From owner-freebsd-hackers Sun Feb 3 0: 8: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C1B3D37B402 for ; Sun, 3 Feb 2002 00:08:06 -0800 (PST) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id g137sH504871; Sat, 2 Feb 2002 23:54:17 -0800 (PST) (envelope-from dg) Date: Sat, 2 Feb 2002 23:54:17 -0800 From: David Greenman To: Matthew Dillon Cc: hackers@freebsd.org Subject: Re: Patch to remove MFREE() macro entirely Message-ID: <20020202235417.B4855@nexus.root.com> References: <200202030400.g13408C59494@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202030400.g13408C59494@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Feb 02, 2002 at 08:00:08PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Oh what a tangled web we weave. This should be really easy for people > to take a quick look at to see if I made any mistakes. I'm basically > untangling the (small) mess that people made of the code while trying to > use the MFREE() macro over the last N years. > > If nobody sees any problems it will go into -current next week some > time and then be MFC'd to stable. Looks good to me. I'm definately very much in favor of killing MFREE(). -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com President, Download Technologies, Inc. - http://www.downloadtech.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 8:17:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.77]) by hub.freebsd.org (Postfix) with ESMTP id BEC1237B404 for ; Sun, 3 Feb 2002 08:17:22 -0800 (PST) Received: from prg.traveller.cz (localhost [127.0.0.1]) by prg.traveller.cz (8.12.1[KQ-CZ](1)/8.12.1/pukvis) with ESMTP id g13GHLg7064706 for ; Sun, 3 Feb 2002 17:17:21 +0100 (CET) Received: from localhost (mime@localhost) by prg.traveller.cz (8.12.1[KQ-CZ](1)/pukvis) with ESMTP id g13GHLil064703 for ; Sun, 3 Feb 2002 17:17:21 +0100 (CET) Date: Sun, 3 Feb 2002 17:17:21 +0100 (CET) From: Michal Mertl To: hackers@freebsd.org Subject: unbelievable benchmark output Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I wrote a simple program which does this: gettimeofday something (takes several seconds) gettimeofday print time elapsed Several runs of the program take about the same time but the time changes wildly when the executable is called differently. ------- ./xx/xxx 5 s xx/xxx 9 s and similar. It holds true on vastly different machines with current and stable. The only thing which I can think of that can be causing this is some memory alignment issue. It makes me a bit scared - if the filename or argv[0] make program load to different address than it can probaly mean that even normal programs can suffer significatnly from this. Alignment, which does gcc would probably be mostly useless than. Does the system care where is loads the program image at all? Compile the code below with gcc -O -march=pentiumpro and save the program to /tmp/x (1x) and /tmp/xxxxxxxxxxx (11x). cd /tmp; ./x shows me 0.490495 (with slight variations amongst runs) and ./xxxxxxxxxxx 1.016591. The real results depend on hw but they occur always with different differences in speed and the length of name of fast/slow programs. BTW: The program doesn't have to contain assembly it seems but with the program below the results are most visible. ---------- 8< -------- #include #include #include #include #define NUMTESTS 10000000 static inline void atomic_add_64(volatile u_int64_t *p, u_int64_t v) { __asm __volatile ( " movl (%0),%%eax ; " " movl 4(%0),%%edx ; " " 1:movl (%1),%%ebx ; " " movl 4(%1),%%ecx ; " " addl %%eax,%%ebx ; " " adcl %%edx,%%ecx ; " " cmpxchg8b (%0) ; " " jnz 1b ; " "#atomic_add_64" : : "S" (p), /* 0 */ "D" (&v) /* 1 */ : "eax", "ebx", "ecx", "edx", "memory" ); } void difftimeval(struct timeval start, struct timeval *end) { if (end->tv_usec < start.tv_usec) { end->tv_usec += (1000000 - start.tv_usec); end->tv_sec--; } else end->tv_usec -= start.tv_usec; end->tv_sec -= start.tv_sec; } int main() { u_int64_t i, j; int k; struct timeval st, en; i = 0; j = 10; gettimeofday(&st, NULL); for (k = 0; k < NUMTESTS; k++) { atomic_add_64(&i, j); } gettimeofday(&en, NULL); difftimeval(st, &en); printf("%lu.%06lu\n", en.tv_sec, en.tv_usec); return (EXIT_SUCCESS); } --------- 8< ---- -- Michal Mertl mime@traveller.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 8:59:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 2F8B437B400 for ; Sun, 3 Feb 2002 08:59:42 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id CD89F10DDF7; Sun, 3 Feb 2002 08:59:41 -0800 (PST) Date: Sun, 3 Feb 2002 08:59:41 -0800 From: Alfred Perlstein To: Michal Mertl Cc: hackers@freebsd.org Subject: stack alignment issues (was: unbelievable benchmark output) Message-ID: <20020203085941.N10817@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mime@traveller.cz on Sun, Feb 03, 2002 at 05:17:21PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Michal Mertl [020203 08:17] wrote: > I wrote a simple program which does this: > > gettimeofday > something (takes several seconds) > gettimeofday > print time elapsed > > Several runs of the program take about the same time but the time > changes wildly when the executable is called differently. > > ------- > ./xx/xxx > 5 s > xx/xxx > 9 s > > and similar. It holds true on vastly different machines with current and > stable. > > The only thing which I can think of that can be causing this is some > memory alignment issue. It sure looks like an alignment issue. If you print the address of 'i' and 'j' in the attached program you can see for the fast case they are aligned to 8 byte boundries, but when it's slow they are at an address that is a multiple of 4 but not 8. Not really sure what to make of this, anyone else know how we ought to fix this? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 9:16:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from cheer.mahoroba.org (flets19-017.kamome.or.jp [218.45.19.17]) by hub.freebsd.org (Postfix) with ESMTP id A07F337B41A for ; Sun, 3 Feb 2002 09:16:18 -0800 (PST) Received: from mille.mahoroba.org (IDENT:DIEE9hEvzul4nFjD4tgkixf7t1hLQhCkr8eM1lpNiVYhHN2Z3qOcIcLcvbA2VZFW@mille.mahoroba.org [IPv6:2001:200:301:0:202:2dff:fe0a:6bee]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.2/8.12.2) with ESMTP/inet6 id g13HGBHk091054 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Feb 2002 02:16:11 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 04 Feb 2002 02:16:11 +0900 Message-ID: From: Hajimu UMEMOTO To: Marco Wertejuk Cc: freebsd-hackers@freebsd.org Subject: Re: rtadvd bugfix? In-Reply-To: <20020202024949.A2176@motoko.hayai.de> References: <20020202024949.A2176@motoko.hayai.de> User-Agent: xcite1.38> Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.5-RELEASE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, >>>>> On Sat, 2 Feb 2002 02:49:49 +0100 >>>>> Marco Wertejuk said: wertejuk> I was really nerved when I noticed that rtadvd is exiting wertejuk> without any notice if the host is not an ipv6 gateway. wertejuk> Since it took me a lot of time to find this problem wertejuk> I wrote a patch for rtadvd to show a message and wertejuk> noticed something strange: wertejuk> rtadvd won't exit even if ipv6 forwarding is not wertejuk> enabled, take a look at this patch. (attachement) wertejuk> Watch out for the changed if-condition. wertejuk> Is that really a bug ? No, I don't think it is a bug. The value of `forwarding' is checked later. From config.c: /* * Basically, hosts MUST NOT send Router Advertisement messages at any * time (RFC 2461, Section 6.2.3). However, it would sometimes be * useful to allow hosts to advertise some parameters such as prefix * information and link MTU. Thus, we allow hosts to invoke rtadvd * only when router lifetime (on every advertising interface) is * explicitly set zero. (see also the above section) */ if (val && forwarding == 0) { syslog(LOG_WARNING, "<%s> non zero router lifetime is specified for %s, " "which must not be allowed for hosts.", __FUNCTION__, intface); exit(1); } And, I believe the message goes to syslog in this case. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 9:29:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from math.smsu.edu (math.smsu.edu [146.7.45.198]) by hub.freebsd.org (Postfix) with ESMTP id 1C7D237B400 for ; Sun, 3 Feb 2002 09:29:16 -0800 (PST) Received: by math.smsu.edu (Postfix, from userid 1000) id 4CFFB8E118; Sun, 3 Feb 2002 11:29:16 -0600 (CST) To: freebsd-hackers@freebsd.org Subject: Re: unbelievable benchmark output Message-Id: <20020203172916.4CFFB8E118@math.smsu.edu> Date: Sun, 3 Feb 2002 11:29:16 -0600 (CST) From: erik@math.smsu.edu (Erik Greenwald) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Several runs of the program take about the same time but the time > changes wildly when the executable is called differently. > > ------- > ./xx/xxx > 5 s > xx/xxx > 9 s > > The only thing which I can think of that can be causing this is some > memory alignment issue. > it could also be the shell taking time to look up the names? > Compile the code below with gcc -O -march=pentiumpro and save the > program to /tmp/x (1x) and /tmp/xxxxxxxxxxx (11x). cd /tmp; ./x shows me > 0.490495 (with slight variations amongst runs) and ./xxxxxxxxxxx 1.016591. > The real results depend on hw but they occur always with different > differences in speed and the length of name of fast/slow programs. > here're my numbers athlon 850, iwill k266 (via686b southbridge), 384m ram, 5400rpm fujitsu 20G FreeBSD fenris 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Feb 1 23:57:28 CST 2002 root@fenris:/usr/src/sys/i386/compile/FENRIS i386 ./x bounces between .6 and .7 ./xxx...xx bounces between .65 and .75 with 100 x's in the name, .67 to .76 /tmp/x .55 .60 /tmp/x(11) .62 /tmp/x(100) .62 .72 > > > -- > Michal Mertl > mime@traveller.cz > -Erik [http://math.smsu.edu/~erik] The opinions expressed by me are not necessarily opinions. In all probability, they are random rambling, and to be ignored. Failure to ignore may result in severe boredom or confusion. Shake well before opening. Keep Refrigerated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 9:56:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id 7CDE237B41A for ; Sun, 3 Feb 2002 09:56:12 -0800 (PST) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.2/8.12.1) with ESMTP id g13Htx7q000753; Sun, 3 Feb 2002 12:55:59 -0500 (EST) Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.2/8.12.1/Submit) id g13Htupr000752; Sun, 3 Feb 2002 12:55:56 -0500 (EST) (envelope-from bmilekic) Date: Sun, 3 Feb 2002 12:55:56 -0500 From: Bosko Milekic To: David Greenman Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Patch to remove MFREE() macro entirely Message-ID: <20020203125556.A487@unixdaemons.com> References: <200202030400.g13408C59494@apollo.backplane.com> <20020202235417.B4855@nexus.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020202235417.B4855@nexus.root.com>; from dg@root.com on Sat, Feb 02, 2002 at 11:54:17PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Feb 02, 2002 at 11:54:17PM -0800, David Greenman wrote: > > Oh what a tangled web we weave. This should be really easy for people > > to take a quick look at to see if I made any mistakes. I'm basically > > untangling the (small) mess that people made of the code while trying to > > use the MFREE() macro over the last N years. > > > > If nobody sees any problems it will go into -current next week some > > time and then be MFC'd to stable. > > Looks good to me. I'm definately very much in favor of killing MFREE(). Absolutely! Especially in light of the fact that in -CURRENT now-a-days, MFREE() will has no benefits and pretty much ALL the mbuf macros are deprecated (they just wrap calls to the appropriate functions). They were really big for macros and actually used to make things slower by busting the cache. > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > President, TeraSolutions, Inc. - http://www.terasolutions.com > President, Download Technologies, Inc. - http://www.downloadtech.com > Pave the road of life with opportunities. -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 10:30:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 79B6B37B417 for ; Sun, 3 Feb 2002 10:30:35 -0800 (PST) Received: from kajsa.energyhq.org (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 7E3803FC4C; Sun, 3 Feb 2002 19:30:36 +0100 (CET) Date: Sun, 3 Feb 2002 19:29:57 +0100 From: Miguel Mendez To: Alfred Perlstein Cc: mime@traveller.cz, hackers@freebsd.org Subject: Re: stack alignment issues (was: unbelievable benchmark output) Message-Id: <20020203192957.4ce563a0.flynn@energyhq.homeip.net> In-Reply-To: <20020203085941.N10817@elvis.mu.org> References: <20020203085941.N10817@elvis.mu.org> Organization: Energy, Inc X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 3 Feb 2002 08:59:41 -0800 Alfred Perlstein wrote: Hi, > It sure looks like an alignment issue. If you print the address > of 'i' and 'j' in the attached program you can see for the fast > case they are aligned to 8 byte boundries, but when it's slow they > are at an address that is a multiple of 4 but not 8. Agreed, my bet is on data alignment. > > Not really sure what to make of this, anyone else know how we ought > to fix this? Well, you could always malloc() some memory and make sure your data is in an address that is multiple of 8. You'll waste some mem but will gain performance. I actually haven't tried it on FreeBSD but it's a trick I used to do on the Amiga some years ago. Cheers, -- Miguel Mendez - flynn@energyhq.homeip.net Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 11:33:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id D1AEC37B417 for ; Sun, 3 Feb 2002 11:33:27 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g13JXIP08178; Sun, 3 Feb 2002 13:33:18 -0600 (CST) (envelope-from dan) Date: Sun, 3 Feb 2002 13:33:18 -0600 From: Dan Nelson To: Alfred Perlstein Cc: Michal Mertl , hackers@FreeBSD.ORG Subject: Re: stack alignment issues (was: unbelievable benchmark output) Message-ID: <20020203193318.GA6310@dan.emsphone.com> References: <20020203085941.N10817@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020203085941.N10817@elvis.mu.org> User-Agent: Mutt/1.3.27i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Feb 03), Alfred Perlstein said: > * Michal Mertl [020203 08:17] wrote: > > Several runs of the program take about the same time but the time > > changes wildly when the executable is called differently. > > > > The only thing which I can think of that can be causing this is > > some memory alignment issue. > > It sure looks like an alignment issue. If you print the address of > 'i' and 'j' in the attached program you can see for the fast case > they are aligned to 8 byte boundries, but when it's slow they are at > an address that is a multiple of 4 but not 8. > > Not really sure what to make of this, anyone else know how we ought > to fix this? This has actually been an issue for ages, most commonly seen with doubles. take a look at the thread at http://www.freebsd.org/cgi/getmsg.cgi?fetch=393691+0+/usr/local/www/db/text/2000/freebsd-current/20000507.freebsd-current or, easier to read the entire thread: http://groups.yahoo.com/group/freebsd-current/messages/39583?threaded=1 -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 12: 0:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bogslab.ucdavis.edu (bogslab.ucdavis.edu [169.237.68.34]) by hub.freebsd.org (Postfix) with ESMTP id B53A537B417 for ; Sun, 3 Feb 2002 12:00:44 -0800 (PST) Received: from thistle.bogs.org (thistle.bogs.org [198.137.203.61]) by bogslab.ucdavis.edu (8.9.3/8.9.3) with ESMTP id MAA49066 for ; Sun, 3 Feb 2002 12:00:38 -0800 (PST) (envelope-from greg@bogslab.ucdavis.edu) Received: from thistle.bogs.org (localhost [127.0.0.1]) by thistle.bogs.org (8.11.3/8.11.3) with ESMTP id g13JxXG36444 for ; Sun, 3 Feb 2002 11:59:35 -0800 (PST) (envelope-from greg@thistle.bogs.org) Message-Id: <200202031959.g13JxXG36444@thistle.bogs.org> To: hackers@FreeBSD.ORG X-To: Dan Nelson X-Sender: owner-freebsd-hackers@FreeBSD.ORG Subject: Re: stack alignment issues (was: unbelievable benchmark output) In-reply-to: Your message of "Sun, 03 Feb 2002 13:33:18 CST." <20020203193318.GA6310@dan.emsphone.com> Reply-To: gkshenaut@ucdavis.edu Date: Sun, 03 Feb 2002 11:59:33 -0800 From: Greg Shenaut Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020203193318.GA6310@dan.emsphone.com>, Dan Nelson cleopede: >In the last episode (Feb 03), Alfred Perlstein said: >> * Michal Mertl [020203 08:17] wrote: >> Not really sure what to make of this, anyone else know how we ought >> to fix this? > >This has actually been an issue for ages, most commonly seen with >doubles. take a look at the thread at Has any "real world" program ever been significantly affected by this "problem"? Greg Shenaut To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 13:11:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from milla.33net.fdns.net (milla.33net.fdns.net [217.197.166.58]) by hub.freebsd.org (Postfix) with ESMTP id 64C5A37B417 for ; Sun, 3 Feb 2002 13:11:17 -0800 (PST) Received: (from nick@localhost) by milla.33net.fdns.net (8.11.6/8.11.6) id g13LBbV42280 for freebsd-hackers@FreeBSD.ORG; Sun, 3 Feb 2002 22:11:37 +0100 (CET) (envelope-from nick) Date: Sun, 3 Feb 2002 22:11:37 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= To: freebsd-hackers@FreeBSD.ORG Subject: File name. Message-ID: <20020203221137.A34994@FreeBSD.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Key-URL: http://naomi.fdns.net/~nick/keys/PGP.txt X-OS: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey. For example i cantrol fchflags syscall via my kernel module. I got: int n_fchflags(register struct proc *p, register struct fchflags_args) { =2E.. } struct fchflags_args { int fd; int flags; }; I can get vnode of changed file. I can get inode number of changed file. But how can i get file name? There is a way to get inode when i have file name and p (struct proc), so maybe there is a way to get file name from inode number and p. And another thing for chflags syscall. I got file name, but how can I get full path name for this file? --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF2niT/PhmMH/Mf1AQF2vgQAg0OzU4aki4NB+fDQk7ozEC5QCIatiBXn ncUdAbf0STcS5zGA8Fsb/1WF5jNtuo45dqkKo1E2jNGjh+cTYUr5MgDryzCBBT3u AFz7RF3Z53pq2rovNtuhyenAtY83epE07bXGGMlQt2H5POnW8+6xc4o/ZeEt+yxz +YxhstKSUmQ= =uYHn -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 15: 6:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id 3C1C437B417 for ; Sun, 3 Feb 2002 15:06:22 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g13N2DZ08920; Sun, 3 Feb 2002 18:02:13 -0500 (EST) (envelope-from mike) Date: Sun, 3 Feb 2002 18:02:13 -0500 From: Mike Barcroft To: Mike Makonnen Cc: Gaspar Chilingarov , freebsd-hackers@freebsd.org Subject: Re: fork rate limit Message-ID: <20020203180213.B6496@espresso.q9media.com> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202030754.g137saC40573@blackbox.pacbell.net>; from mike_makonnen@yahoo.com on Sat, Feb 02, 2002 at 11:54:36PM -0800 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Makonnen writes: > On Sun, 3 Feb 2002 02:35:46 +0400 > Gaspar Chilingarov wrote: > > > I've got such situation on our free shellbox set up in the > > university - some newbies were kidding with old while(1) fork(); > > attack. Finnaly they got hit by memory limits set up for each > > user, but anyway they were taking a lot of processor time. I > > prefer to limit some uid's ability to do many forks in some > > short period - like 'no more than 200 forks in 10 seconds' or > > smthng like this. > > Lock them out of the box for a while. If they do it again ban them > forever. The students will learn pretty quickly not to do such things. He should be able to pick his own administrative policy. > This means less work for you, and no need to continuously maintain diffs > against the kernel sources. IMO it's a *very,very* bad thing to > introduce changes into the kernel that might introduce unintended side > effects when the problem can be solved administratively. Obviously he is intending his changes to be committed; hence, the patches will be applicable to -CURRENT. This is an area where FreeBSD is lacking. I can't understand why you wish to stifle his work. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 19:14:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 805AE37B404; Sun, 3 Feb 2002 19:14:14 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g143EDD36265; Sun, 3 Feb 2002 22:14:13 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 3 Feb 2002 22:14:12 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mike Barcroft Cc: Mike Makonnen , Gaspar Chilingarov , freebsd-hackers@freebsd.org Subject: Re: fork rate limit In-Reply-To: <20020203180213.B6496@espresso.q9media.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 3 Feb 2002, Mike Barcroft wrote: > > This means less work for you, and no need to continuously maintain diffs > > against the kernel sources. IMO it's a *very,very* bad thing to > > introduce changes into the kernel that might introduce unintended side > > effects when the problem can be solved administratively. > > Obviously he is intending his changes to be committed; hence, the > patches will be applicable to -CURRENT. This is an area where FreeBSD > is lacking. I can't understand why you wish to stifle his work. BTW, many sites find the per-uid process limits helpful in preventing fork bombs from crippling the site. The default configuration may not be sufficiently agressive, and while it's not the same as a rate limit, it does have the effect of topping them. If there is a strong desire for rate-limiting, slotting it into the current resource handling code shouldn't be hard at all -- the state can be stored in uidinfo. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 19:37:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d127.as1.nwbl0.wi.voyager.net [169.207.130.193]) by hub.freebsd.org (Postfix) with ESMTP id 0C11237B47A; Sun, 3 Feb 2002 19:37:35 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g13LfEa13399; Sun, 3 Feb 2002 21:41:15 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 3 Feb 2002 21:41:14 +0000 (GMT) From: Mike Silbersack To: Robert Watson Cc: Mike Barcroft , Mike Makonnen , Gaspar Chilingarov , Subject: Re: fork rate limit In-Reply-To: Message-ID: <20020203213819.C13287-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 3 Feb 2002, Robert Watson wrote: > BTW, many sites find the per-uid process limits helpful in preventing fork > bombs from crippling the site. The default configuration may not be > sufficiently agressive, and while it's not the same as a rate limit, it > does have the effect of topping them. If there is a strong desire for > rate-limiting, slotting it into the current resource handling code > shouldn't be hard at all -- the state can be stored in uidinfo. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services Yeah, I threw in the maxprocperuid auto-capping thinking that it would help reduce the nastiness of forkbombs. However, as PR kern/23740 points out, one of the problems we're encountering now is that the proc structures are large enough that all kernel memory can be exhausted. We're going to have to cap maxproc so that proc structures can't use more than 50% of system memory in order to make sure that forkbombs can't seriously hurt a box. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 19:45:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d127.as1.nwbl0.wi.voyager.net [169.207.130.193]) by hub.freebsd.org (Postfix) with ESMTP id 5395A37B405 for ; Sun, 3 Feb 2002 19:45:09 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g13LmPV13436; Sun, 3 Feb 2002 21:48:25 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 3 Feb 2002 21:48:25 +0000 (GMT) From: Mike Silbersack To: Luigi Rizzo Cc: Storms of Perfection , , , Subject: Re: Clock Granularity (kernel option HZ) In-Reply-To: <20020201002017.B48439@iguana.icir.org> Message-ID: <20020203214558.T13287-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 1 Feb 2002, Luigi Rizzo wrote: > HZ also has an impact on select() behaviour when timeouts are > used (and device drivers using timeouts as well). > A lot of software uses select() with a very short timeout which > is usually rounded up to the next tick. If the author of the software > is unaware of what goes on (likely) there might be negative effects > on performance because such programs stay idle longer than they should. > > cheers > luigi True, I had forgotten about that effect. Ironic, since I was quite annoyed by the limitations of 10ms accuracy last semester. Increasing the resolution of select/usleep is a good argument for increasing the HZ default, but I'm not sure how great the impact would be on slower machines. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 20:13:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d127.as1.nwbl0.wi.voyager.net [169.207.130.193]) by hub.freebsd.org (Postfix) with ESMTP id 9465037B416 for ; Sun, 3 Feb 2002 20:13:42 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g13MH0813560; Sun, 3 Feb 2002 22:17:01 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Sun, 3 Feb 2002 22:17:00 +0000 (GMT) From: Mike Silbersack To: Terry Lambert Cc: Alfred Perlstein , Luigi Rizzo , Storms of Perfection , , , Subject: Re: Clock Granularity (kernel option HZ) In-Reply-To: <3C5A8290.216BB28C@mindspring.com> Message-ID: <20020203220958.Q13287-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 1 Feb 2002, Terry Lambert wrote: > I guess you are talking the LRP stuff. > > I was just talking about the processing at NETISR as a > result of a higher HZ causing a higher softintr run > frequency. Interesting; I hadn't considered that scheduling could have an effect on performance, but that does make sense on a heavily loaded system. > Really, the timer code that TCP uses is all bogus for a > large number of connections, and upping the clock wheel > size doesn't gain you nearly as much as interval specific > lists which only have to process until the intended time > to fire is later than "now". The clock stuff as it is > has to traverse the entire chain, because it can't know > that the firing of the timer after the current one is later > than the current one (i.e. intervals of 1 second and one > hour can end up in the same wheel bucket, because it is, in > effect, an unsorted modular timer, and inserting sorted for > more than one or two intervals is an O(N) problem). > > -- Terry I was looking at the timer implementation a few weeks ago and pondering if it could be improved as well. I think it's quite clever if you're dealing with a quantity of timers < 1000 or so, but it looks like it could be more optimal when used with the quantity of timers we have these days. Did you attempt to combine the various tcp timers so that there would be one callout per socket? I think it would be a pretty easy task; just store the various timers inside each socket, and only set a callout for the soonest to wake one. Upon wakeup, quickly check them all. That would reduce the total number of events in the callout wheel for one, and might help with the hash function aliasing long-term events such as keepalives into the current time. (I'm assuming that the retransmission and other short-term timers do a good job of keeping themselves just ahead of the clockhand that they aren't falsely checked.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:11:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f138.pav1.hotmail.com [64.4.31.138]) by hub.freebsd.org (Postfix) with ESMTP id D379737B422 for ; Sun, 3 Feb 2002 23:11:45 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 3 Feb 2002 23:11:45 -0800 Received: from 212.30.183.204 by pv1fd.pav1.hotmail.msn.com with HTTP; Mon, 04 Feb 2002 07:11:45 GMT X-Originating-IP: [212.30.183.204] From: "Magdalinin Kirill" To: freebsd-hackers@freebsd.org Subject: how to count number of user process? Date: Mon, 04 Feb 2002 10:11:45 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 04 Feb 2002 07:11:45.0761 (UTC) FILETIME=[34796D10:01C1AD4B] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, can anyone give an idea of C code on how to quickly count the number of processes for a given user? I want to patch Apache in order to prevent it from forking new process over user's maxproc limit (while running suexec). Should I look at ps(1) source code or there are some other examples? thanks, Kirill Magdalinin bsdforumen@hotmail.com _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:17:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 510AA37B405 for ; Sun, 3 Feb 2002 23:17:51 -0800 (PST) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 1D614A809; Mon, 4 Feb 2002 18:17:49 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 1BD085427; Mon, 4 Feb 2002 18:17:49 +1100 (EST) Date: Mon, 4 Feb 2002 18:17:49 +1100 (EST) From: Andrew To: Magdalinin Kirill Cc: freebsd-hackers@freebsd.org Subject: Re: how to count number of user process? In-Reply-To: Message-ID: <20020204181712.P53524-100000@starbug.ugh.net.au> X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Feb 2002, Magdalinin Kirill wrote: > can anyone give an idea of C code on how to quickly count > the number of processes for a given user? I want to patch You could try kvm_getprocs with an argument of KERN_PROC_UID. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:23:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 781CB37B423; Sun, 3 Feb 2002 23:23:28 -0800 (PST) Received: from blackbox.pacbell.net ([64.172.25.165]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GQZ0022DZ735U@mta5.snfc21.pbi.net>; Sun, 03 Feb 2002 23:23:28 -0800 (PST) Received: (from mikem@localhost) by blackbox.pacbell.net (8.11.6/8.11.6) id g147Nld08497; Sun, 03 Feb 2002 23:23:47 -0800 (PST envelope-from mikem) Date: Sun, 03 Feb 2002 23:23:47 -0800 From: Mike Makonnen Subject: Re: fork rate limit In-reply-to: <20020203180213.B6496@espresso.q9media.com> To: Mike Barcroft Cc: nm@web.am, freebsd-hackers@freebsd.org Message-id: <200202040723.g147Nld08497@blackbox.pacbell.net> MIME-version: 1.0 X-Mailer: Sylpheed version 0.6.5 (GTK+ 1.2.10; i386--freebsd4.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203180213.B6496@espresso.q9media.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 3 Feb 2002 18:02:13 -0500 Mike Barcroft wrote: > He should be able to pick his own administrative policy. And what I pointed out was simply another choice. Whether he implements the solution in software or takes the administrative route is obviously his choice. And if other people are interested in the work and want it commited that's fine too. cheers, mike makonnen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:49:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from milla.33net.fdns.net (milla.33net.fdns.net [217.197.166.58]) by hub.freebsd.org (Postfix) with ESMTP id DFDDA37B404 for ; Sun, 3 Feb 2002 23:49:17 -0800 (PST) Received: (from nick@localhost) by milla.33net.fdns.net (8.11.6/8.11.6) id g147ndw45671 for freebsd-hackers@FreeBSD.ORG; Mon, 4 Feb 2002 08:49:39 +0100 (CET) (envelope-from nick) Date: Mon, 4 Feb 2002 08:49:39 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= To: freebsd-hackers@FreeBSD.ORG Subject: Re: File name. Message-ID: <20020204084939.B34994@FreeBSD.pl> References: <20020203221137.A34994@FreeBSD.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020203221137.A34994@FreeBSD.pl>; from nick@FreeBSD.pl on Sun, Feb 03, 2002 at 10:11:37PM +0100 X-PGP-Key-URL: http://naomi.fdns.net/~nick/keys/PGP.txt X-OS: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --gatW/ieO32f1wygP Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 03, 2002 at 10:11:37PM +0100, Pawe=B3 Jakub Dawidek wrote: +> But how can i get file name? +>=20 [...] +> I got file name, but how can I get full path name for this file? +>=20 Answer that there is no way to get that will be nice too. --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --gatW/ieO32f1wygP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF49Ez/PhmMH/Mf1AQHo2AP/cLh+ua3IwrUg402Bc+T+MzUY4m1TC5zM agR1wuE7QbyB13aUM5jrflTUrBXHizUFgUG0zSUZdGXfbHeIdkVLZuVYwiiyNa2E wOFBUvHlFUE+cSJVNVfbRQhUgplFBqHFQCE+O6CWv4GIuIhBqTFh7SxfSUgFkaQj t8OoKH/bOBs= =J3l/ -----END PGP SIGNATURE----- --gatW/ieO32f1wygP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:53:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A79537B41B for ; Sun, 3 Feb 2002 23:53:53 -0800 (PST) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.3/8.11.3) with ESMTP id g147rnO6362838; Mon, 4 Feb 2002 10:53:49 +0300 (MSK) Date: Mon, 4 Feb 2002 10:53:48 +0300 (MSK) From: Maxim Konovalov To: Magdalinin Kirill Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: how to count number of user process? In-Reply-To: Message-ID: <20020204105308.L66803-100000@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10:11+0300, Feb 4, 2002, Magdalinin Kirill wrote: > Hello, > > can anyone give an idea of C code on how to quickly count > the number of processes for a given user? I want to patch > Apache in order to prevent it from forking new process > over user's maxproc limit (while running suexec). > > Should I look at ps(1) source code or there are some > other examples? take a look at src/usr.bin/killall/killall.c > thanks, > > Kirill Magdalinin > bsdforumen@hotmail.com > > _________________________________________________________________ > Join the world’s largest e-mail service with MSN Hotmail. > http://www.hotmail.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto: maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 3 23:55: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 2E36D37B400 for ; Sun, 3 Feb 2002 23:54:59 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id EE8B910DDF7; Sun, 3 Feb 2002 23:54:58 -0800 (PST) Date: Sun, 3 Feb 2002 23:54:58 -0800 From: Alfred Perlstein To: Pawel Jakub Dawidek Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: File name. Message-ID: <20020203235458.P10817@elvis.mu.org> References: <20020203221137.A34994@FreeBSD.pl> <20020204084939.B34994@FreeBSD.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020204084939.B34994@FreeBSD.pl>; from nick@FreeBSD.pl on Mon, Feb 04, 2002 at 08:49:39AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Pawel Jakub Dawidek [020203 23:49] wrote: > On Sun, Feb 03, 2002 at 10:11:37PM +0100, Pawel Jakub Dawidek wrote: > +> But how can i get file name? > +> > [...] > +> I got file name, but how can I get full path name for this file? > +> > Answer that there is no way to get that will be nice too. There is, and there isn't. :) Since UFS allows for hardlinks a single file may have multiple valid names. For instance: # cd /tmp # echo foo > f1 # ln f1 f2 484 -rw-r--r-- 2 root wheel 4 Feb 4 01:39 f1 484 -rw-r--r-- 2 root wheel 4 Feb 4 01:39 f2 However there's a dirty way to get at it via the vfs lookup cache entries hung off the vnode. Paul Saab showed me a delta that did something nasty like this, but I've got no clue as to where it is now. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 0:58:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from milla.33net.fdns.net (milla.33net.fdns.net [217.197.166.58]) by hub.freebsd.org (Postfix) with ESMTP id 5626C37B404 for ; Mon, 4 Feb 2002 00:58:16 -0800 (PST) Received: (from nick@localhost) by milla.33net.fdns.net (8.11.6/8.11.6) id g148wfX46158 for freebsd-hackers@freebsd.org; Mon, 4 Feb 2002 09:58:41 +0100 (CET) (envelope-from nick) Date: Mon, 4 Feb 2002 09:58:40 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= To: freebsd-hackers@freebsd.org Subject: Re: File name. Message-ID: <20020204095840.B45984@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="JP+T4n/bALQSJXh8" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Key-URL: http://garage.freebsd.pl/keys/PGP.txt X-OS: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --JP+T4n/bALQSJXh8 Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 03, 2002 at 11:54:58PM -0800, Alfred Perlstein wrote: +> However there's a dirty way to get at it via the vfs lookup cache +> entries hung off the vnode. Paul Saab showed me a delta that +> did something nasty like this, but I've got no clue as to where +> it is now. +>=20 Hmm... And what with full path when i got filename, proc, etc. I can get full path or only mountpoint? --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --JP+T4n/bALQSJXh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF5NQD/PhmMH/Mf1AQErigQAgw6AI0svbMQBkwq1u9mf2D1zfI+AH76V 5APY+LbYePvppFBcWgbM0uu61e3+XAzVpGfgb2M1/deXInNVF9rvAKXx9HnNe95X yOgoYWCZhLKV+7amscsMx+gbg252/7Zjao7liJIw8dZ6uYV/ha4m58Jitx4w9Z4w T0xsoynqUcA= =Gw5l -----END PGP SIGNATURE----- --JP+T4n/bALQSJXh8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 1: 4:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from saturn.home.ben.com (12-224-233-146.client.attbi.com [12.224.233.146]) by hub.freebsd.org (Postfix) with ESMTP id 11EF437B41A for ; Mon, 4 Feb 2002 01:04:28 -0800 (PST) Received: from pulsar.home.ben.com (pulsar.home.ben.com [172.17.42.9]) by saturn.home.ben.com (8.11.6/8.11.6) with ESMTP id g1494RX34836 for ; Mon, 4 Feb 2002 01:04:27 -0800 (PST) Received: from pulsar.home.ben.com (bjj@localhost) by pulsar.home.ben.com (8.11.6/8.6.12) with ESMTP id g1494Q848838 for ; Mon, 4 Feb 2002 01:04:26 -0800 (PST) Message-Id: <200202040904.g1494Q848838@pulsar.home.ben.com> To: freebsd-hackers@FreeBSD.ORG Subject: a note about configure, off_t and struct stat Date: Mon, 04 Feb 2002 01:04:26 -0800 From: Ben Jackson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd like to preserve this for posterity, so I'm hoping the list will accept this (I'm not subscribed) so that others may benefit from the archives. I hope no one else ever has to spend the 10 hours on this I did! IF for some reason configure decides that your system does not define `off_t' it will put `#define off_t long' in config.h. Among other things, this will makes struct stat 4 bytes shorter. This means that calls to stat() will now stomp on memory every time it's called. With auto variables you might get lucky and hit things like return addresses! Much fun ensues. You could probably also get crazy results from mmap() and other things taking off_t which you are sure you have the prototype for but are getting 32 bit quantities anyway. For some reason the two things that this bit me on were bonobo-conf and ximian evolution. For whatever reason, db-3.1.17 (if you've built evolution you know what I mean) which I built at the same time detected off_t fine and didn't have this problem. --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 1:15:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 750AF37B445 for ; Mon, 4 Feb 2002 01:15:05 -0800 (PST) Received: from pool0039.cvx40-bradley.dialup.earthlink.net ([216.244.42.39] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16XfCl-0007fk-00; Mon, 04 Feb 2002 01:14:28 -0800 Message-ID: <3C5E50EE.C6FBD879@mindspring.com> Date: Mon, 04 Feb 2002 01:14:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Silbersack Cc: Alfred Perlstein , Luigi Rizzo , Storms of Perfection , thierry@herbelot.com, replicator@ngs.ru, hackers@FreeBSD.org Subject: Re: Clock Granularity (kernel option HZ) References: <20020203220958.Q13287-100000@patrocles.silby.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Silbersack wrote: > I was looking at the timer implementation a few weeks ago and pondering if > it could be improved as well. I think it's quite clever if you're dealing > with a quantity of timers < 1000 or so, but it looks like it could be more > optimal when used with the quantity of timers we have these days. You can up the number of buckets; the theory is that most network timeouts have "untimeout" called on them before they have a chance to fire. This means that any time you hit a slot in the wheel, you have to traverse the entire list of timeouts in the chain for that slot, since the insertion of new timeouts is not ordered. It's not really easy to do ordered insertion, since you would need to have a data structure that lets you access it as a btree, to even get O(log2(N)+.5) time on the insertion (e.g. if it were made bsearchable). The timeouts are based on the number of slots vs. the HZ of the soft timer, vs. the number of outstanding requests ...this is what determines if there is the possibility of more than one entry per bucket, or if a bucket list spans more than 2MSL for all buckets (high HZ vs. number of slots). Even so, with a large number of connection requests in a given soft timer quanta, they all end up in the same bucket, which is worst case performance under an attack. So yeah: it works for a small number of connections (e.g. desktop use), but falls over under a large number of connections relative to log2(N) for N buckets (server use), so it's pretty suboptimal. And the longer the list, the less likely you are to get to all the entries within a quantum, so at some point, you will starvation deadlock doing timer list traversal, and nothing else. > Did you attempt to combine the various tcp timers so that there would be > one callout per socket? I think it would be a pretty easy task; just > store the various timers inside each socket, and only set a callout for > the soonest to wake one. Upon wakeup, quickly check them all. That would > reduce the total number of events in the callout wheel for one, and might > help with the hash function aliasing long-term events such as keepalives > into the current time. (I'm assuming that the retransmission and other > short-term timers do a good job of keeping themselves just ahead of the > clockhand that they aren't falsely checked.) This actually doesn't work, unless you round all events to the same interval. Basically, this would mean that you would be rescheduling the same set of timers for a small set of durations. IMO, it's better to avoid the callout wheel entirely, for this case. You don't really want to examine all 2MSL timers for 1,000,000 connections, every 2MSL. My preferred approach to to create one list per fixed duration timer, and then you end up with a small number of these lists, leaving other timeout events to fall on the callout wheel. Then when the softclock fires, you go down each of this small number of lists, until the time to expire exceeds the current tick, at which point you bail. This works with fixed duration lists, where it doesn't work with the callout wheel, because you know that each element in the list is a fixed duration, and therefore, if you link onto the end of the list when scheduling a new one, you are guaranteed that the list will be ordered in terms of increasing tick-at-which-to-fire. In the callout wheel case, each bucket is not necessarily ordered in increasing tick, and since the number of ticks is not fixed -- there is no fixed duration guarantee -- you have to traverse the entire list. Since you already know that one of your main assumptions is that the timeouts will be untimed-out before they fire, then for a list of N elements, you only have to traverse M + 1 elements, where there are M elements to fire for this given interval. The effect of this is to reduce a list of N elements to traverse in a given bucket to a single element traversal, in most cases ( M ~= 0, M << N ). This effectively scales much better. It scales almost infinitely, whereas the other approach scales for the total number of elements K ( M[0] ... M[n], n~= 5 for a small number of fixed intervals can translate into a large "K") to K/number_of_buckets_in_wheel ... basically, an exponential times log2(number_of_buckets_in_wheel). Personally, I've looked at the "Opportunistic Timers" paper, and I'm not convinced about their arguments during overload conditions; specifically, I think that all it really does is free up CPU time for the non-overload case that no one cares about, and degrades to hard timers in the overload case, where the "opportunity" never presents to do timer processing, since you're already screwed by livelock at that point. I think some small number of fixed interval lists is probably the correct way to go for large scaling. You could probably safely eat a variance of +/- < 1MSL, if you wanted to do so, by only doing the processing of the soft interrupt list for the 2MSL timer every 1MSL, or more frequently, if you needed a higher resolution; in any case, it migh make sense to make _that_ list traversal a scheduled event on the timer wheel; however, I think that you probably want to seperate it, and do the traversal of the fixed intervals up front, for other timer load reasons (e.g. TCP timers aren't the only ones that tend to go up hugely when you have 1,000,000 TCP connections lying around). I would do the fixed interval traversal first, before the wheel slot list, as you *know* that all but the last compare will result in a timer firing, so it's more like "real work" than the callout wheel. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 1:28:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 7CB5837B41C for ; Mon, 4 Feb 2002 01:28:18 -0800 (PST) Received: from pool0039.cvx40-bradley.dialup.earthlink.net ([216.244.42.39] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16XfPc-00059x-00; Mon, 04 Feb 2002 01:27:44 -0800 Message-ID: <3C5E540B.9FDACF64@mindspring.com> Date: Mon, 04 Feb 2002 01:27:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?Pawe=B3?= Jakub Dawidek Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: File name. References: <20020203221137.A34994@FreeBSD.pl> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pawe=B3 Jakub Dawidek wrote: > I can get vnode of changed file. > I can get inode number of changed file. > But how can i get file name? > = > There is a way to get inode when i have file name and p (struct proc), = so > maybe there is a way to get file name from inode number and p. > = > And another thing for chflags syscall. > I got file name, but how can I get full path name for this file? char *saved_name; func() { char *foo; ... fd =3D open( foo, O_RDWR, 0664); saved_name =3D strdup( foo); ... printf( "name that goes with fd %d is '%s'\n", fd, saved_name); ... } i.e.: You opened the thing, you ought to know its name. = -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 2: 9:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from milla.33net.fdns.net (milla.33net.fdns.net [217.197.166.58]) by hub.freebsd.org (Postfix) with ESMTP id 4398237B400 for ; Mon, 4 Feb 2002 02:09:40 -0800 (PST) Received: (from nick@localhost) by milla.33net.fdns.net (8.11.6/8.11.6) id g14AAFt46841 for freebsd-hackers@freebsd.org; Mon, 4 Feb 2002 11:10:15 +0100 (CET) (envelope-from nick) Date: Mon, 4 Feb 2002 11:10:15 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= To: freebsd-hackers@freebsd.org Subject: Re: File name. Message-ID: <20020204111015.D45984@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hxkXGo8AKqTJ+9QI" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Key-URL: http://garage.freebsd.pl/keys/PGP.txt X-OS: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --hxkXGo8AKqTJ+9QI Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 04, 2002 at 01:27:39AM -0800, Terry Lambert wrote: +> char *saved_name; +>=20 +> func() +> { +> char *foo; +>=20 +> ... +>=20 +> fd =3D open( foo, O_RDWR, 0664); +> saved_name =3D strdup( foo); +>=20 +> ... +>=20 +> printf( "name that goes with fd %d is '%s'\n", +> fd, saved_name); +> ... +> } +>=20 +> i.e.: You opened the thing, you ought to know its name.=20 +>=20 Nope. We are in kernel area. I want to control for example open() syscall: static int my_open(register struct proc *p, register struct open_args *ea) { [...] } Name of file to open is in ea->path, but this name can be: ./somefile and i need a full path to it. --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --hxkXGo8AKqTJ+9QI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF5eBz/PhmMH/Mf1AQFSEQP+Ir/rGLnVKuDUow27z4A6gGNBksGFFzFb 6wSB4rO8jDYjihIYlHBFsSXGE8Wn05zpfdmb3k4v8oIz+ERFul31S+4whCHEfGJF ZJacRyGS08IQ6WyBqfL99Wfxs39SbfNS5ckWvgvVCVqdiSNpj7SzoYxAUSfL57o5 7fNCgmiQtao= =COd3 -----END PGP SIGNATURE----- --hxkXGo8AKqTJ+9QI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 2:40: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 54B4737B425 for ; Mon, 4 Feb 2002 02:38:13 -0800 (PST) Received: (from root@localhost) by bugz.infotecs.ru (8.11.6/8.11.4) id g14Aai194298 for freebsd-hackers@freebsd.org; Mon, 4 Feb 2002 13:36:44 +0300 (MSK) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200202041036.g14Aai194298@bugz.infotecs.ru> Subject: Re: file name To: freebsd-hackers@freebsd.org Date: Mon, 4 Feb 2002 13:36:44 +0300 (MSK) X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I want to control for example open() syscall: > static int my_open(register struct proc *p, register struct open_args *ea) > { > [...] > } > Name of file to open is in ea->path, but this name can be: ./somefile > and i need a full path to it. I faced that problem once. I used an ugly hack: simulation of __getcwd() syscall. You need to allocate user memory via mmap() with MAP_ANON flag, pass it to __getcwd(), then copy string to kernel using copyin() or like that, and munmap() the memory. This is neither proper nor efficient way to do that, but it's easy and it works. Note that in case of ./ or several ../ in the file name you may need to do some extra processing to get "correct" full path. Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 2:40:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from cisco.com (europe.cisco.com [144.254.52.73]) by hub.freebsd.org (Postfix) with ESMTP id 3501037B425 for ; Mon, 4 Feb 2002 02:40:56 -0800 (PST) Received: from cobweb.example.org (dhcp-nic-val-26-117.cisco.com [64.103.26.117]) by cisco.com (8.8.8+Sun/8.8.8) with SMTP id LAA23465 for ; Mon, 4 Feb 2002 11:40:53 +0100 (MET) Received: (qmail 66659 invoked by uid 1000); 4 Feb 2002 10:41:38 -0000 Date: Mon, 4 Feb 2002 11:41:38 +0100 From: Marco Molteni To: freebsd-hackers@freebsd.org Subject: status of bluetooth support for FreeBSD? Message-ID: <20020204104138.GA66539@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I remember an email thread on -hackers last October on bluetooth support for FreeBSD: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=589265+595599+/usr/local/www/db/text/2001/freebsd-hackers/20011007.freebsd-hackers There were two different projects, one in design phase (by John Kozubik ) and another (by Maksim Yevmenkin ) with already some beta code working. any news on this? thanks Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 2:53: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from milla.33net.fdns.net (milla.33net.fdns.net [217.197.166.58]) by hub.freebsd.org (Postfix) with ESMTP id AED8B37B41E for ; Mon, 4 Feb 2002 02:52:57 -0800 (PST) Received: (from nick@localhost) by milla.33net.fdns.net (8.11.6/8.11.6) id g14ArI547199 for freebsd-hackers@freebsd.org; Mon, 4 Feb 2002 11:53:18 +0100 (CET) (envelope-from nick) Date: Mon, 4 Feb 2002 11:53:18 +0100 From: =?ISO-8859-2?Q?Pawe=B3_Jakub_Dawidek?= To: freebsd-hackers@freebsd.org Subject: Re: file name Message-ID: <20020204115318.E45984@garage.freebsd.pl> References: <200202041036.g14Aai194298@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Q8BnQc91gJZX4vDc" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202041036.g14Aai194298@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on Mon, Feb 04, 2002 at 01:36:44PM +0300 X-PGP-Key-URL: http://garage.freebsd.pl/keys/PGP.txt X-OS: FreeBSD 4.5-RC i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Q8BnQc91gJZX4vDc Content-Type: text/plain; charset=ISO-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 04, 2002 at 01:36:44PM +0300, Eugene L. Vorokov wrote: +> I faced that problem once. I used an ugly hack: simulation of __getcwd() +> syscall. You need to allocate user memory via mmap() with MAP_ANON flag, +> pass it to __getcwd(), then copy string to kernel using copyin() or like +> that, and munmap() the memory. This is neither proper nor efficient way +> to do that, but it's easy and it works. Note that in case of ./ or +> several ../ in the file name you may need to do some extra processing +> to get "correct" full path. +> =20 Working! thX a lot! :) --=20 Pawe=B3 Jakub Dawidek Network Administrator. Am I Evil? Yes, I Am. --Q8BnQc91gJZX4vDc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia iQCVAwUBPF5oHj/PhmMH/Mf1AQHWxgP/YYw5C12D832V98eSVFMPjKMe5QFg0gBX 2s2t6r2VucN4EWtPD3Y81lXs7/3c8xeaWmBemBPUoYijEOLphtqXauz2cTZk+Kni lR1UUv4qcGFsMtWrDfn2VaxMTiSR3+eUgrBtdEyqeN5/1I4E1qc6DmFzKxzdDaPu +btvx+3r3ZA= =tpSF -----END PGP SIGNATURE----- --Q8BnQc91gJZX4vDc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 3:13:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.77]) by hub.freebsd.org (Postfix) with ESMTP id 517E237B420 for ; Mon, 4 Feb 2002 03:13:32 -0800 (PST) Received: from prg.traveller.cz (localhost [127.0.0.1]) by prg.traveller.cz (8.12.1[KQ-CZ](1)/8.12.1/pukvis) with ESMTP id g14BDIG2037219; Mon, 4 Feb 2002 12:13:18 +0100 (CET) Received: from localhost (mime@localhost) by prg.traveller.cz (8.12.1[KQ-CZ](1)/pukvis) with ESMTP id g14BDH8V037214; Mon, 4 Feb 2002 12:13:17 +0100 (CET) Date: Mon, 4 Feb 2002 12:13:17 +0100 (CET) From: Michal Mertl To: hackers@freebsd.org Cc: greg@bogslab.ucdavis.edu, Subject: Re: stack alignment issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greg Shenaut wrote: > In message <20020203193318.GA6310@dan.emsphone.com>, Dan Nelson cleopede: > >In the last episode (Feb 03), Alfred Perlstein said: > >> * Michal Mertl [020203 08:17] wrote: > >> Not really sure what to make of this, anyone else know how we ought > >> to fix this? > > > >This has actually been an issue for ages, most commonly seen with > >doubles. take a look at the thread at > > Has any "real world" program ever been significantly affected by > this "problem"? I don't know any such program but I suppose they exist. The problem is probably generaly unnoticed by the people running the program. FWIW OpenBSD 2.6 has the same problem but Linux (kernel 2.0 and 2.4) is unaffected. Did you look at the patch by Bruce at http://groups.yahoo.com/group/freebsd-current/message/39605 ? Bruce, is it still fresh in your memory? Can you comment on the patch - can it be commited in some form? -- Michal Mertl mime@traveller.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 3:41:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 59AC937B423 for ; Mon, 4 Feb 2002 03:41:13 -0800 (PST) Received: from pool0049.cvx22-bradley.dialup.earthlink.net ([209.179.198.49] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16XhUN-00057j-00; Mon, 04 Feb 2002 03:40:47 -0800 Message-ID: <3C5E733A.25EE304C@mindspring.com> Date: Mon, 04 Feb 2002 03:40:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?Pawe=B3?= Jakub Dawidek Cc: freebsd-hackers@freebsd.org Subject: Re: File name. References: <20020204111015.D45984@garage.freebsd.pl> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pawe=B3 Jakub Dawidek wrote: > Nope. We are in kernel area. > I want to control for example open() syscall: > static int my_open(register struct proc *p, register struct open_args *= ea) > { > [...] > } > Name of file to open is in ea->path, but this name can be: ./somefile > and i need a full path to it. Look at the "open" and "exec" source code. The "." is interpreted in the context of the current directory for the current process for the lookup. The answer is to know what "." means, in context. If you don't have a current process from which to get a pointer to the current directory vnode, then you will need to make one up yourself. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 5:33:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from digitaldaemon.com (digitaldaemon.com [63.105.9.34]) by hub.freebsd.org (Postfix) with SMTP id D306A37B422 for ; Mon, 4 Feb 2002 05:33:33 -0800 (PST) Received: (qmail 36372 invoked from network); 4 Feb 2002 13:33:53 -0000 Received: from 213-84-202-101.adsl.xs4all.nl (HELO jak.nl) (213.84.202.101) by jak.nl with SMTP; 4 Feb 2002 13:33:53 -0000 Message-ID: <3C5E8EA2.8070204@jak.nl> Date: Mon, 04 Feb 2002 14:37:38 +0100 From: Arjan Knepper Organization: JAK++ Software Development B.V. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: hackers FreeBSD Subject: SMP problem on DELL PowerEdge 2550 with Cyclades Cyclom YeP boards (STABLE 4.5) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG When a dual processor kernel is used the system panics (crash and reboot) on io on the cyclades serial ports. Single processor kernel runs without problems. Any ideas? Thanks, Arjan Knepper To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 9:23:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from OWA-UK-1.digisle.com (OWA-UK-1.digisle.com [206.220.226.174]) by hub.freebsd.org (Postfix) with ESMTP id 3DD6437B421; Mon, 4 Feb 2002 09:23:16 -0800 (PST) Received: from digisle.net ([206.220.227.145]) by OWA-UK-1.digisle.com with Microsoft SMTPSVC(5.0.2195.3779); Mon, 4 Feb 2002 17:23:14 +0000 Message-ID: <3C5EC381.C8F658B@digisle.net> Date: Mon, 04 Feb 2002 09:23:14 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: status of bluetooth support for FreeBSD? References: <20020204104138.GA66539@cobweb.example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Feb 2002 17:23:15.0380 (UTC) FILETIME=[A130FF40:01C1ADA0] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hackers, sorry for wide distribution. there are some news. i will submit full status report when its due (this weed i think) thanks, max Marco Molteni wrote: > > Hi all, > > I remember an email thread on -hackers last October on bluetooth > support for FreeBSD: > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=589265+595599+/usr/local/www/db/text/2001/freebsd-hackers/20011007.freebsd-hackers > > There were two different projects, one in design phase (by John Kozubik > ) and another (by Maksim Yevmenkin ) > with already some beta code working. > > any news on this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 9:46:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 67B8F37B41F for ; Mon, 4 Feb 2002 09:46:20 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA27900; Tue, 5 Feb 2002 04:46:03 +1100 Date: Tue, 5 Feb 2002 04:48:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Michal Mertl Cc: , Subject: Re: stack alignment issues In-Reply-To: Message-ID: <20020205043744.G23848-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Feb 2002, Michal Mertl wrote: > Did you look at the patch by Bruce at > http://groups.yahoo.com/group/freebsd-current/message/39605 ? > > Bruce, is it still fresh in your memory? Can you comment on the patch - > can it be commited in some form? I haven't done anything to clean up the patch. I hope the problem will go away in future versions of gcc (align the stack at runtime in the few routines that actually need it). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 10: 3:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d172.as12.nwbl0.wi.voyager.net [169.207.136.174]) by hub.freebsd.org (Postfix) with ESMTP id 2370437B433 for ; Mon, 4 Feb 2002 10:03:52 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g14C7BH02267; Mon, 4 Feb 2002 12:07:13 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Mon, 4 Feb 2002 12:07:11 +0000 (GMT) From: Mike Silbersack To: Bruce Evans Cc: Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020205043744.G23848-100000@gamplex.bde.org> Message-ID: <20020204120547.B2144-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Bruce Evans wrote: > On Mon, 4 Feb 2002, Michal Mertl wrote: > > > Did you look at the patch by Bruce at > > http://groups.yahoo.com/group/freebsd-current/message/39605 ? > > > > Bruce, is it still fresh in your memory? Can you comment on the patch - > > can it be commited in some form? > > I haven't done anything to clean up the patch. I hope the problem > will go away in future versions of gcc (align the stack at runtime in > the few routines that actually need it). > > Bruce Well, if Linux aligns the initial stack, the chance that gcc will have auto-alignment added sounds to be about zero. You might as well go ahead with your patch when you get a chance. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 10:11:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 2019E37B423 for ; Mon, 4 Feb 2002 10:11:19 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id E273F10DDF7; Mon, 4 Feb 2002 10:11:18 -0800 (PST) Date: Mon, 4 Feb 2002 10:11:18 -0800 From: Alfred Perlstein To: Mike Silbersack Cc: Bruce Evans , Michal Mertl , hackers@freebsd.org, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues Message-ID: <20020204101118.A12744@elvis.mu.org> References: <20020205043744.G23848-100000@gamplex.bde.org> <20020204120547.B2144-100000@patrocles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020204120547.B2144-100000@patrocles.silby.com>; from silby@silby.com on Mon, Feb 04, 2002 at 12:07:11PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Mike Silbersack [020204 10:04] wrote: > > On Tue, 5 Feb 2002, Bruce Evans wrote: > > > On Mon, 4 Feb 2002, Michal Mertl wrote: > > > > > Did you look at the patch by Bruce at > > > http://groups.yahoo.com/group/freebsd-current/message/39605 ? > > > > > > Bruce, is it still fresh in your memory? Can you comment on the patch - > > > can it be commited in some form? > > > > I haven't done anything to clean up the patch. I hope the problem > > will go away in future versions of gcc (align the stack at runtime in > > the few routines that actually need it). > > > > Bruce > > Well, if Linux aligns the initial stack, the chance that gcc will have > auto-alignment added sounds to be about zero. You might as well go ahead > with your patch when you get a chance. I agree, either way we should try to optimized the current situation, especially if it seems to give a 2x perf boost! -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 10:47: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2262337B425; Mon, 4 Feb 2002 10:46:52 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g14IkoD45722; Mon, 4 Feb 2002 13:46:50 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 4 Feb 2002 13:46:50 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Bi-Monthly Development Status Report Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a solicitation for submissions for the December 2001 - January 2002 FreeBSD Bi-Monthly Development Status Report. All submissions are due by February 8, 2002. Submissions should be made by filling out the template found at: http://www.FreeBSD.org/news/status/report-sample.xml Submissions must then be e-mailed to the following address: robert+freebsd.monthly@cyrus.watson.org For automatic processing. Reports must be submitted in the XML format described, or they will be silently dropped. Submissions made to other e-mail addresses will be ignored. Status reports should be submitted once per project, although project developers may choose to submit additional reports on specific sub-projects of substantial size. Status reports are typically one or two short paragraphs, but the text may be up to 20 lines in length. Submissions are welcome on a variety of topics relating to FreeBSD, including development, documentation, advocacy, and development processes. Prior status reports may be viewed at: http://www.FreeBSD.org/news/status/ Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 11:41:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id BF62537B428 for ; Mon, 4 Feb 2002 11:41:38 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g14Jfxi62359; Mon, 4 Feb 2002 11:41:59 -0800 (PST) Date: Mon, 4 Feb 2002 11:41:58 -0800 (PST) From: Doug White To: Marko Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: natd UDP errors with PPP demand dial In-Reply-To: <51142759637.20020202102537@mindspring.com> Message-ID: <20020204114052.Q61624-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 2 Feb 2002, Marko wrote: > My question is concerning the popular "netd[pid] failed to write > packet back [Permission denied]" message. This is caused by ipfw blocking packets after natd has translated them. Check your firewall rules. It might be an odd race of the rules not getting installed before natd fires up. Are you using ppp.linkup (or equivalent) to configure ipfw in this case? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 13:21:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 19F5237B419 for ; Mon, 4 Feb 2002 13:21:26 -0800 (PST) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g14LLPo48309 for ; Mon, 4 Feb 2002 13:21:25 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 04 Feb 2002 13:21:25 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: A question about timecounters Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to understand the timecounter code, and in particular the reason for the "microuptime went backwards" messages which I see on just about every machine I have, whether running -stable or -current. This problem is usually attributed to too much interrupt latency. My question is, how much latency is "too much"? Which interrupt has to be locked out for how long in order to see these messages? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 13:34:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from host213-123-128-100.in-addr.btopenworld.com (host213-123-128-100.in-addr.btopenworld.com [213.123.128.100]) by hub.freebsd.org (Postfix) with ESMTP id CCCBB37B426 for ; Mon, 4 Feb 2002 13:34:50 -0800 (PST) Received: by host213-123-128-100.in-addr.btopenworld.com (Postfix, from userid 1001) id 2CCCA72; Mon, 4 Feb 2002 21:34:50 +0000 (GMT) Date: Mon, 4 Feb 2002 21:34:50 +0000 From: Dominic Marks To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters Message-ID: <20020204213450.E923@gallium.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jdp@polstra.com on Mon, Feb 04, 2002 at 01:21:25PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 04, 2002 at 01:21:25PM -0800, John Polstra wrote: > I'm trying to understand the timecounter code, and in particular the > reason for the "microuptime went backwards" messages which I see on > just about every machine I have, whether running -stable or -current. I see them everywhere with -CURRENT, but not at all with -STABLE. This is with two seperate machines. Perhaps that may add clues. > This problem is usually attributed to too much interrupt latency. My > question is, how much latency is "too much"? Which interrupt has to > be locked out for how long in order to see these messages? > > John > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 13:42:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from OWA-UK-1.digisle.com (OWA-UK-1.digisle.com [206.220.226.174]) by hub.freebsd.org (Postfix) with ESMTP id 2B07837B426; Mon, 4 Feb 2002 13:42:25 -0800 (PST) Received: from digisle.net ([206.220.227.145]) by OWA-UK-1.digisle.com with Microsoft SMTPSVC(5.0.2195.3779); Mon, 4 Feb 2002 21:42:23 +0000 Message-ID: <3C5F003D.CA329159@digisle.net> Date: Mon, 04 Feb 2002 13:42:21 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Bluetooth stack for FreeBSD (full status) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Feb 2002 21:42:24.0005 (UTC) FILETIME=[D4E4E350:01C1ADC4] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hackers, Here is full status report on project i was working on. I apologize for the wide distribution, but i think that might be interesting. Bluetooth stack for FreeBSD (Netgraph implementation) ===================================================== The project is making progress. I decided to submit report because now i have some confidence that i can make it actually work. The goal is to design and implement Host Controller Interface (HCI) and Link Layer Control and Adaptation Protocol (L2CAP) layers using Netgraph framework. All information obtained from Bluetooth Specification Book v1.1. More distant goal is to write support for Service Discovery Protocol (SDP) and RFCOMM protocol (serial port emulation over Bluetooth link). RFCOMM is more fun (IMO) and the current plan is to write RFCOMM Netgraph module and then tie it with "ng_tty" to complete the graph. BTW, while i was working on this Nokia has released another open source Bluetooth stack for Linux - Affix (http://affix.sourceforge.net). And i do not want to see FreeBSD behind :) Project roadmap ================ Step 1: General design Status: Complete. Everything is pretty much defined and i have more or less clear picture of how it will work. However, there are several minor issues. I still trying to figure them out. Step 2: Implementation (HCI and L2CAP layer) Status: Complete. HCI and L2CAP Netgraph nodes have been implemented. Most of the implementation issues have been resolved. However, there are some parts of the code that may require minor changes. Step 3: Testing Status: In progress. I finally figured out how to etherboot -current under VMWare (would be nice if someone can put it into handbook), and now i have perfect "sand box". Testing is likely to take some time. I do not have real Bluetooth hardware at this point, so i wrote some tools that allow me to test the code. Some of them will be used as foundation for future utilities. But i only can do spot testing. I need hardware. At this point the code seems to work, but i still need to test all failure modes and make sure code does the right thing. The Bluetooth specification does not provide great details on everything (IMO), so i'm trying to do reasonable thing. After this step is complete i will make an engineering release and make it available to the community. The purpose is to collect feedback from people who familiar with Netgraph and/or Bluetooth and make all required changes. Step 4: Utilities/Library API/Documentation Status: In progress. Some work already has been done as part of "Step 3: Testing". I need some time and external input to figure out what is actually required. Ideal case would be to reuse what is already implemented. Step 5: Unit testing with real hardware Status: Not complete. I keep looking for Bluetooth hardware every day. I'm glad to see that it is actually exists. The good news is that some cards have UART 1650 on board, so (i hope) they are just fancy serial ports. If that is true, then "ng_sio" module would be perfect. The "ng_sio" will act just like "ng_ether" module, but for serial ports. NOTE: "ng_sio" module does not exist yet :) Step 6: Final acceptance testing and stable release Status: Not complete. This is not for me to decide :) I hope to get feedback from people. Issues ====== 1. Bluetooth hardware. I do not have real Bluetooth hardware and i need it badly :) If people can donate hardware/specs it would be great. I promise to write all required drivers and make them available. I also promise to return hardware/specs on first request. For now my plan is to spend some amount of $$$ and get a card or even two. 2. Project name. I would like to see the name that reflects the following: - it is a Bluetooth stack - implementation is for FreeBSD - implementation based on Netgraph framework Thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 13:57:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 5016B37B41E for ; Mon, 4 Feb 2002 13:57:52 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g14Lvao48420; Mon, 4 Feb 2002 13:57:36 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g14LvaX02099; Mon, 4 Feb 2002 13:57:36 -0800 (PST) (envelope-from jdp) Date: Mon, 4 Feb 2002 13:57:36 -0800 (PST) Message-Id: <200202042157.g14LvaX02099@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: dominic_marks@btinternet.com Subject: Re: A question about timecounters In-Reply-To: <20020204213450.E923@gallium.localdomain> References: <20020204213450.E923@gallium.localdomain> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020204213450.E923@gallium.localdomain>, Dominic Marks wrote: > On Mon, Feb 04, 2002 at 01:21:25PM -0800, John Polstra wrote: > > I'm trying to understand the timecounter code, and in particular the > > reason for the "microuptime went backwards" messages which I see on > > just about every machine I have, whether running -stable or -current. > > I see them everywhere with -CURRENT, but not at all with -STABLE. This is > with two seperate machines. Perhaps that may add clues. I'm looking for something less empirical than that. When somebody says this problem is caused by too much interrupt latency, I assume they have a mental model of what is going wrong when this excessive latency occurs. Given that, it should be possible to make a statement like, "If X is never locked out for longer than Y, this problem cannot happen." I'm looking for definitions of X and Y. X might be hardclock() or softclock() or non-interrupt kernel processing. Y would be some measure of time, probably a function of HZ and/or the timecounter frequency. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 14:35:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 1FF8B37B419 for ; Mon, 4 Feb 2002 14:35:22 -0800 (PST) Received: (qmail 6699 invoked by uid 100); 4 Feb 2002 22:35:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15455.3239.990461.982594@guru.mired.org> Date: Mon, 4 Feb 2002 16:35:19 -0600 To: hackers@freebsd.org Subject: VCD file system? X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-STABLE-i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm not sure where this should go, but -hackers seems to be about right. I notice that I can put a Video CD in a Windows machine - even back to W98 - and it manages to show me folders and files on it. This makes me think that the thing has a file system on it. The question is then - what's the file system format, and is it available for FreeBSD or is someone working on it? Thanx, http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 14:37:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id D586737B41B for ; Mon, 4 Feb 2002 14:37:45 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id A60209B08; Mon, 4 Feb 2002 17:37:08 -0500 (EST) Date: Mon, 4 Feb 2002 17:37:08 -0500 From: Will Andrews To: Maksim Yevmenkin Cc: freebsd-hackers@freebsd.org Subject: Re: Bluetooth stack for FreeBSD (full status) Message-ID: <20020204223708.GR82640@squall.waterspout.com> References: <3C5F003D.CA329159@digisle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C5F003D.CA329159@digisle.net> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 04, 2002 at 01:42:21PM -0800, Maksim Yevmenkin wrote: > Hackers, Please properly format your email so it doesn't look like the below so I can read it. > Here is full status report on project i was working on. I apologize for > the > wide distribution, but i think that might be interesting. > > Bluetooth stack for FreeBSD (Netgraph implementation) > ===================================================== > > The project is making progress. I decided to submit report because now i > have > some confidence that i can make it actually work. The goal is to design > and > implement Host Controller Interface (HCI) and Link Layer Control and > Adaptation > Protocol (L2CAP) layers using Netgraph framework. All information > obtained from > Bluetooth Specification Book v1.1. [...] This sounds like something that should be submitted to robert+freebsd-monthly@cyrus.watson.org for inclusion with the next FreeBSD Development Monthly Status Report. You'll want to abridge it for that purpose though. :) Regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15: 3:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 8B93A37B416 for ; Mon, 4 Feb 2002 15:03:18 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g14N37604748; Tue, 5 Feb 2002 00:03:07 +0100 (CET) (envelope-from wkb) Date: Tue, 5 Feb 2002 00:03:07 +0100 From: Wilko Bulte To: Mike Meyer Cc: hackers@FreeBSD.ORG Subject: Re: VCD file system? Message-ID: <20020205000307.C4704@freebie.xs4all.nl> References: <15455.3239.990461.982594@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15455.3239.990461.982594@guru.mired.org>; from mwm-dated-1013294120.4f4266@mired.org on Mon, Feb 04, 2002 at 04:35:19PM -0600 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 04, 2002 at 04:35:19PM -0600, Mike Meyer wrote: ISO9660, so plain old CDROM fs. At least the VCDs I bought in HongKong last year are like that. Wilko > I'm not sure where this should go, but -hackers seems to be about right. > > I notice that I can put a Video CD in a Windows machine - even back to > W98 - and it manages to show me folders and files on it. This makes me > think that the thing has a file system on it. > > The question is then - what's the file system format, and is it > available for FreeBSD or is someone working on it? > > Thanx, > -- > Mike Meyer http://www.mired.org/home/mwm/ > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---end of quoted text--- -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:13:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from zilla.emergent.com.au (www.emergent.com.au [203.27.68.30]) by hub.freebsd.org (Postfix) with ESMTP id A9D9F37B405 for ; Mon, 4 Feb 2002 15:13:34 -0800 (PST) Received: from spgtscts01 ([203.41.151.8]) by zilla.emergent.com.au (8.11.3/8.9.3) with SMTP id g14NDUJ27329; Tue, 5 Feb 2002 10:13:30 +1100 (EST) (envelope-from cmoran@emergent.com.au) Message-ID: <00be01c1add1$89b51280$59cfa8c0@southpacific.corp.microsoft.com> From: "Moran, Chris" To: , "Mike Meyer" References: <15455.3239.990461.982594@guru.mired.org> Subject: Re: VCD file system? Date: Tue, 5 Feb 2002 10:13:15 +1100 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am pretty sure it is ISO ----- Original Message ----- From: "Mike Meyer" To: Sent: Tuesday, February 05, 2002 9:35 AM Subject: VCD file system? > I'm not sure where this should go, but -hackers seems to be about right. > > I notice that I can put a Video CD in a Windows machine - even back to > W98 - and it manages to show me folders and files on it. This makes me > think that the thing has a file system on it. > > The question is then - what's the file system format, and is it > available for FreeBSD or is someone working on it? > > Thanx, > -- > Mike Meyer http://www.mired.org/home/mwm/ > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:18:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.slc.edu (Weir-01a.SLC.Edu [198.83.6.252]) by hub.freebsd.org (Postfix) with ESMTP id 51D7037B41C for ; Mon, 4 Feb 2002 15:17:38 -0800 (PST) Received: (from aschneid@localhost) by mail.slc.edu (8.11.6/8.11.6) id g14IHOt01696; Mon, 4 Feb 2002 18:17:24 GMT (envelope-from aschneid@mail.slc.edu) Date: Mon, 4 Feb 2002 18:17:24 +0000 From: Anthony Schneider To: Mike Makonnen Cc: Gaspar Chilingarov , freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit Message-ID: <20020204181724.B1633@mail.slc.edu> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203160433.A10920@mail.slc.edu> <20020203223946.B13336@mail.slc.edu> <20020204175616.A1056@mail.slc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SkvwRMAIpAhPCcCJ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020204175616.A1056@mail.slc.edu>; from aschneid@mail.slc.edu on Mon, Feb 04, 2002 at 05:56:16PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --SkvwRMAIpAhPCcCJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've actually wanted something like this for a while and have considered coding it myself. Perhaps this could go into a login.conf variable (which I would have to create myself), but originally my plan was basically kill off parent processes with the uid of the user who is fork()'ing too often (200 per 10 seconds sounds good) simply hard-coded. Now, should this be available as a login.conf variable, and should the variable ever be used on a system other than my own, it could very easily be defaulted to something like :maxforks=3D0: for a 10 second timespan, and set to :maxforks=3D200: for the scenario we are talking about, perhaps assigned exclusively to student (or untrusted) accounts. So, by default, the limit will be ignored, and aside from the potential for poor implementation of th= is, the only side effect would be a default login.conf with an extra line, and perhaps a few extra lines in the login.conf manpage. Some people would like to limit this, and should they want to, they should be able to. People run public access systems (myself included) where fork bombs can put a huge load on the system before a sysadmin can finally pick out the perpetrator and zap him. This is a non-fatal, but VERY annoying scenario to deal with, and if it can be prevented, I say go for it. I believe that a few tweaks to fork1(), struct uidinfo and some others would do the trick. Gaspar, if you choose to go ahead with this and would like assistance (testing, coding), I'd be glad to help. Also, if anyone has any further input, I know that I'd be glad to hear about it. -Anthony. p.s. sincerest apologies for anyone who may have received several copies of this email. I've been having a few mail difficulties. On Sat, Feb 02, 2002 at 11:54:36PM -0800, Mike Makonnen wrote: > On Sun, 3 Feb 2002 02:35:46 +0400 > Gaspar Chilingarov wrote: >=20 > > I've got such situation on our free shellbox set up in the > > university - some newbies were kidding with old while(1) fork(); > > attack. Finnaly they got hit by memory limits set up for each > > user, but anyway they were taking a lot of processor time. I > > prefer to limit some uid's ability to do many forks in some > > short period - like 'no more than 200 forks in 10 seconds' or > > smthng like this. >=20 > Lock them out of the box for a while. If they do it again ban them > forever. The students will learn pretty quickly not to do such things. > This means less work for you, and no need to continuously maintain diffs > against the kernel sources. IMO it's a *very,very* bad thing to > introduce changes into the kernel that might introduce unintended side > effects when the problem can be solved administratively. >=20 >=20 > cheers, > mike makonnen >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --SkvwRMAIpAhPCcCJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxe0DMACgkQ+rDjkNht5F2mBgCgmBKcKLwbARjh2pNkmUN08GIG vmgAnAjZIU8wU/AM/3+WRXelgu516Oi6 =Ch/R -----END PGP SIGNATURE----- --SkvwRMAIpAhPCcCJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:36:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 29DFD37B425 for ; Mon, 4 Feb 2002 15:36:24 -0800 (PST) Received: from pool0476.cvx22-bradley.dialup.earthlink.net ([209.179.199.221] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Xsen-0007hd-00; Mon, 04 Feb 2002 15:36:17 -0800 Message-ID: <3C5F1AEB.2946887D@mindspring.com> Date: Mon, 04 Feb 2002 15:36:11 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Mike Silbersack , Bruce Evans , Michal Mertl , hackers@freebsd.org, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues References: <20020205043744.G23848-100000@gamplex.bde.org> <20020204120547.B2144-100000@patrocles.silby.com> <20020204101118.A12744@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > Well, if Linux aligns the initial stack, the chance that gcc will have > > auto-alignment added sounds to be about zero. You might as well go ahead > > with your patch when you get a chance. > > I agree, either way we should try to optimized the current situation, > especially if it seems to give a 2x perf boost! How about "aligning the initial stack"? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:37: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id EEB4037B4CF for ; Mon, 4 Feb 2002 15:36:11 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g14NZpQ54565; Mon, 4 Feb 2002 17:35:51 -0600 (CST) (envelope-from dan) Date: Mon, 4 Feb 2002 17:35:51 -0600 From: Dan Nelson To: Anthony Schneider Cc: Mike Makonnen , Gaspar Chilingarov , freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit Message-ID: <20020204233550.GE88948@dan.emsphone.com> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203160433.A10920@mail.slc.edu> <20020203223946.B13336@mail.slc.edu> <20020204175616.A1056@mail.slc.edu> <20020204181724.B1633@mail.slc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020204181724.B1633@mail.slc.edu> User-Agent: Mutt/1.3.27i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Feb 04), Anthony Schneider said: > I've actually wanted something like this for a while and have considered > coding it myself. Perhaps this could go into a login.conf variable > (which I would have to create myself), but originally my plan was basically > kill off parent processes with the uid of the user who is fork()'ing too > often (200 per 10 seconds sounds good) simply hard-coded. Killing off parent procs could really upset a regular user who is running ./configure, which could easily spawn a couple undred processes in 10 seconds. Maybe simply delay the fork() until the rate drops? -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:44:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 40B0637B41D; Mon, 4 Feb 2002 15:44:49 -0800 (PST) Received: from pool0476.cvx22-bradley.dialup.earthlink.net ([209.179.199.221] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Xsmv-0003n8-00; Mon, 04 Feb 2002 15:44:42 -0800 Message-ID: <3C5F1CE4.1566F495@mindspring.com> Date: Mon, 04 Feb 2002 15:44:36 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maksim Yevmenkin Cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Bluetooth stack for FreeBSD (full status) References: <3C5F003D.CA329159@digisle.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maksim Yevmenkin wrote: > More distant goal is to write support for Service Discovery Protocol > (SDP) and RFCOMM protocol (serial port emulation over Bluetooth link). FWIW: The SDP is based on SLP; the Salutation Consortium (also with major support from IBM) has several implementations of this, and there are a couple of public implementations as well, including a mesh-enabled DA. If you search for "Service Location Protocol" on the web, you should find most of these. I haven't really taken an active interest in BlueTooth, since there are no laptops or printers that come with it already present; I rather think it will end up as still-born because of 802.11e Gigabit wireless, which can use as little or less power. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 15:58:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dmlb.org (pc1-camc6-0-cust106.cam.cable.ntl.com [80.4.4.106]) by hub.freebsd.org (Postfix) with ESMTP id 1BC0937B400; Mon, 4 Feb 2002 15:58:07 -0800 (PST) Received: from slave.my.domain ([192.168.200.39] helo=slave) by dmlb.org with smtp (Exim 3.33 #1) id 16Xszo-000Muj-00; Mon, 04 Feb 2002 23:58:00 +0000 Message-ID: <00a201c1add7$dc2e99e0$27c8a8c0@my.domain> From: "Duncan Barclay" To: "Terry Lambert" , "Maksim Yevmenkin" Cc: , References: <3C5F003D.CA329159@digisle.net> <3C5F1CE4.1566F495@mindspring.com> Subject: Re: Bluetooth stack for FreeBSD (full status) Date: Mon, 4 Feb 2002 23:58:36 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Terry Lambert" > I haven't really taken an active interest in BlueTooth, > since there are no laptops or printers that come with > it already present; I rather think it will end up as > still-born because of 802.11e Gigabit wireless, which > can use as little or less power. There are now a few devices with Bluetooth in them. Sony has had a Viao with it in for a while. 802.11e is not gigabit wireless. .11e is quality of service enhancements to the .11 MAC. You may be confusing it with .11a - 54Mbps at 5.2GHz or the new .11g giving 54Mbps at 2.45GHz. Some people (Proxim) have .11a cards that can operate at 108Mbps. This will have a reduced range though as they probably halve the forward error correction somehow - maybe by increased puncturing. .11 without .11e is worse than Bluetooth for certain data types. For example it cannot carry isochronous data. Bluetooth was never meant to compete with .11 and was designed for a different purpose - mobile phones. Wanderering around the UK's high streets a lot of phone shops and a couple of the bigger consumer electronics chains are now selling Bluetooth enabled stuff. Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 16: 1:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.slc.edu (Weir-01a.SLC.Edu [198.83.6.252]) by hub.freebsd.org (Postfix) with ESMTP id 41E2837B41D for ; Mon, 4 Feb 2002 16:01:20 -0800 (PST) Received: (from aschneid@localhost) by mail.slc.edu (8.11.6/8.11.6) id g14J0uU02216; Mon, 4 Feb 2002 19:00:56 GMT (envelope-from aschneid@mail.slc.edu) Date: Mon, 4 Feb 2002 19:00:56 +0000 From: Anthony Schneider To: Dan Nelson Cc: Mike Makonnen , Gaspar Chilingarov , freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit Message-ID: <20020204190056.A2156@mail.slc.edu> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203160433.A10920@mail.slc.edu> <20020203223946.B13336@mail.slc.edu> <20020204175616.A1056@mail.slc.edu> <20020204181724.B1633@mail.slc.edu> <20020204233550.GE88948@dan.emsphone.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020204233550.GE88948@dan.emsphone.com>; from dnelson@allantgroup.com on Mon, Feb 04, 2002 at 05:35:51PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable good point. it seems that on open (yet restricted) systems, users wouldn't be ./configure'ing much software, particularly if quotas are small and network access is next to none, which would leave me inclined to go with the kill(). But, of course, that would just be for my own uses. Perhaps there's a way to do both? Either have two login.conf variables, one for delay and one for timespan, or even combine them into one with a 'd' or 't' suffix? I guess the kill() isn't particularly necessary. -Anthony. On Mon, Feb 04, 2002 at 05:35:51PM -0600, Dan Nelson wrote: > In the last episode (Feb 04), Anthony Schneider said: > > I've actually wanted something like this for a while and have considered > > coding it myself. Perhaps this could go into a login.conf variable > > (which I would have to create myself), but originally my plan was basic= ally > > kill off parent processes with the uid of the user who is fork()'ing too > > often (200 per 10 seconds sounds good) simply hard-coded. >=20 > Killing off parent procs could really upset a regular user who is > running ./configure, which could easily spawn a couple undred processes > in 10 seconds. Maybe simply delay the fork() until the rate drops? >=20 > --=20 > Dan Nelson > dnelson@allantgroup.com --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxe2mcACgkQ+rDjkNht5F1rGQCfULi4KHq27m9/URqrilgFVgwQ rrEAmwY9D8EycF6mhSlRQtfgJVQGWNkS =iHcm -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 16: 8: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from OWA-UK-1.digisle.com (OWA-UK-1.digisle.com [206.220.226.174]) by hub.freebsd.org (Postfix) with ESMTP id 2CDE337B422; Mon, 4 Feb 2002 16:07:56 -0800 (PST) Received: from digisle.net ([206.220.227.145]) by OWA-UK-1.digisle.com with Microsoft SMTPSVC(5.0.2195.3779); Tue, 5 Feb 2002 00:07:54 +0000 Message-ID: <3C5F2259.D230E492@digisle.net> Date: Mon, 04 Feb 2002 16:07:53 -0800 From: Maksim Yevmenkin Organization: Digital Island X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Duncan Barclay Cc: Terry Lambert , freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Bluetooth stack for FreeBSD (full status) References: <3C5F003D.CA329159@digisle.net> <3C5F1CE4.1566F495@mindspring.com> <00a201c1add7$dc2e99e0$27c8a8c0@my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Feb 2002 00:07:55.0458 (UTC) FILETIME=[293EE220:01C1ADD9] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Duncan Barclay wrote: > > From: "Terry Lambert" > > I haven't really taken an active interest in BlueTooth, > > since there are no laptops or printers that come with > > it already present; I rather think it will end up as > > still-born because of 802.11e Gigabit wireless, which > > can use as little or less power. > > There are now a few devices with Bluetooth in them. Sony has had a Viao > with it in for a while. yes, Sony VAIO PCG-SR31K http://www.zdnet.co.uk/reviews/rstories/0,3040,e7110920,00.html as far as printing goes, you can get Bluetooth adapter for your printer. thanks, max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 17:17:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 654) id 9BCB037B419; Mon, 4 Feb 2002 17:17:36 -0800 (PST) Date: Mon, 4 Feb 2002 17:17:36 -0800 From: Mike Smith To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters Message-ID: <20020204171736.A13719@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In article <20020204213450.E923@gallium.localdomain>, > Dominic Marks wrote: > > On Mon, Feb 04, 2002 at 01:21:25PM -0800, John Polstra wrote: > > > I'm trying to understand the timecounter code, and in particular the > > > reason for the "microuptime went backwards" messages which I see on > > > just about every machine I have, whether running -stable or -current. > > > > I see them everywhere with -CURRENT, but not at all with -STABLE. This is > > with two seperate machines. Perhaps that may add clues. > > I'm looking for something less empirical than that. When somebody > says this problem is caused by too much interrupt latency, I assume > they have a mental model of what is going wrong when this excessive > latency occurs. It's not necessarily caused by interrupt latency. Here's the assumption that's being made. There is a ring of timecounter structures, of some size. In testing, I've used sizes of a thousand or more, but still seen this problem. There is a pointer to the "current" timecounter structure. When the "current" time is updated, the following procedure is followed: - Find the "next" timecounter in the ring. - Update its contents with the new current time. - Move the "current" pointer. When one wishes to read the current time, one proceeds as follows: - Get the "current" pointer and save it locally. - Read the timecounter structure via the local "current" pointer. Since the operations on the "current" pointer are atomic, there is no need to lock the structure. There are a couple of possible problems with this mechanism. One is that the ring "catches up" with your saved copy of the "current" pointer, ie. inbetween fetching the pointer and reading the timecounter contents, the "next" pointer passes over you again in such a fashion that you get garbage out of the structure. Another is that there is a race between multiple updaters of the timecounter; if two parties are both updating the "next" timecounter along with another party trying to get the "current" time, this could cause corruption. All that interrupt latency will do is make the updates late; I can't actually see how it could cause corruption. Corruption has to be caused by mishandling of the timecounter ring in some fashion. Note that you can probably eliminate the ring loop theory by allocating a very large number of entries in the ring by setting NTIMECOUNTER (kern/kern_tc.c) higher. The structures are small; try 100,000 or so. If you can reproduce under these circumstances, try adding some checks to make sure the "current" timecounter pointer is behaving monotonically; just save the last timecounter pointer in microtime() et. al. Another test worth performing is to look at the tco_delta function for the timecounter and make sure that it returns a sane value, and one that doesn't behave out of synch with the interrupt handler that updates the timecounter proper. If you save the delta value in the timecounter and zero it when it's updated, you can catch this. You can rule this out by using getmicroptime() rather than microuptime(); it may return the same value twice, which isn't desirable, but that would be better than nothing. Hope this helps a bit. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 17:42:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id B4D2B37B425; Mon, 4 Feb 2002 17:42:01 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g151g0o49308; Mon, 4 Feb 2002 17:42:00 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g151fxW02520; Mon, 4 Feb 2002 17:41:59 -0800 (PST) (envelope-from jdp) Date: Mon, 4 Feb 2002 17:41:59 -0800 (PST) Message-Id: <200202050141.g151fxW02520@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: msmith@hub.freebsd.org Subject: Re: A question about timecounters In-Reply-To: <20020204171736.A13719@hub.freebsd.org> References: <20020204171736.A13719@hub.freebsd.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020204171736.A13719@hub.freebsd.org>, Mike Smith wrote: > > It's not necessarily caused by interrupt latency. Here's the assumption > that's being made. [...] Thanks for the superb explanation! I appreciate it. > There is a ring of timecounter structures, of some size. In testing, > I've used sizes of a thousand or more, but still seen this problem. > > There is a pointer to the "current" timecounter structure. That's the global variable named "timecounter", right? I did notice one potential problem: that variable is not declared volatile. So in this part ... > When one wishes to read the current time, one proceeds as follows: > > - Get the "current" pointer and save it locally. > - Read the timecounter structure via the local "current" pointer. ... the compiler is perfectly free to reread the global multiple times in the function rather than using the saved local copy. If the "current" pointer has moved in that time, we'll an inconsistent view of the timecounter. In looking at the generated code I haven't found any actual instances of that. But I'll try making it volatile just to make sure. Even if it doesn't cause any problems currently, I think we should change it to volatile since it could start to cause problems some day. I also noticed this in tco_forward(): tco = timecounter; tc = sync_other_counter(); [...] if (tco->tc_poll_pps) But sync_other_counter() loads its own copy of "timecounter", and there's no guarantee it hasn't changed from the value that tco_forward() saved in its local variable. I'm not sure yet if that's a potential problem. It could corrected by passing "tco" as an argument to sync_other_counter. I'll try that too. > There are a couple of possible problems with this mechanism. > > One is that the ring "catches up" with your saved copy of the > "current" pointer, ie. inbetween fetching the pointer and reading the > timecounter contents, the "next" pointer passes over you again in such > a fashion that you get garbage out of the structure. As you mentioned, with a large enough ring this should be impossible. If I read the code correctly, the "current" pointer is only moved once per second. So in the current ring of 4 counters (number 0 is special), it would take 4 seconds to wrap around the ring. That's a pretty long time. > Another is that there is a race between multiple updaters of the > timecounter; if two parties are both updating the "next" timecounter > along with another party trying to get the "current" time, this could > cause corruption. > > All that interrupt latency will do is make the updates late; I can't > actually see how it could cause corruption. Corruption has to be > caused by mishandling of the timecounter ring in some fashion. I agree. > Note that you can probably eliminate the ring loop theory by > allocating a very large number of entries in the ring by setting > NTIMECOUNTER (kern/kern_tc.c) higher. The structures are small; try > 100,000 or so. OK, but even the thousand you tried should give a cushion of more than 16 minutes. > If you can reproduce under these circumstances, try adding some checks > to make sure the "current" timecounter pointer is behaving > monotonically; just save the last timecounter pointer in microtime() > et. al. > > Another test worth performing is to look at the tco_delta function for > the timecounter and make sure that it returns a sane value, and one > that doesn't behave out of synch with the interrupt handler that updates > the timecounter proper. If you save the delta value in the timecounter > and zero it when it's updated, you can catch this. > > You can rule this out by using getmicroptime() rather than > microuptime(); it may return the same value twice, which isn't > desirable, but that would be better than nothing. > > Hope this helps a bit. Yep, thanks again. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 17:45:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 5C3BF37B404 for ; Mon, 4 Feb 2002 17:45:45 -0800 (PST) Received: from chowder.gsoft.com.au (root@localhost [127.0.0.1]) by cain.gsoft.com.au (8.11.6/8.11.6) with ESMTP id g151jTZ48520; Tue, 5 Feb 2002 12:15:29 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00be01c1add1$89b51280$59cfa8c0@southpacific.corp.microsoft.com> Date: Tue, 05 Feb 2002 12:15:28 +1030 (CST) From: "Daniel O'Connor" To: "Moran, Chris" Subject: Re: VCD file system? Cc: Mike Meyer , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 04-Feb-2002 Moran, Chris wrote: > I am pretty sure it is ISO VCD's have a 'shell' ISO9660 FS on them to put stuff like a VCD player and movie info on, but the actual movie data is not stored on that FS. I believe it is recorded with a different mode that has less error checking (more space) on another track. I think mplayer can play them 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-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 18: 6:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from imr1.aus.deuba.com (bagheera.aus.deuba.com [203.0.62.7]) by hub.freebsd.org (Postfix) with ESMTP id 72B0B37B429 for ; Mon, 4 Feb 2002 18:06:27 -0800 (PST) Received: from bmr1-e1.aus.deuba.com by imr1.aus.deuba.com id g1526OP26019; Tue, 5 Feb 2002 13:06:25 +1100 (EST) Received: from mailhost.aus.deuba.com [10.179.4.6] by bmr1-e1.aus.deuba.com id g1526On05373; Tue, 5 Feb 2002 13:06:24 +1100 (EST) Received: from merton.aus.deuba.com (merton.aus.deuba.com [10.179.88.22]) by mailhost.aus.deuba.com (8.9.1/8.9.1) with SMTP id NAA21660 for ; Tue, 5 Feb 2002 13:06:23 +1100 (EST) Received: (qmail 75169 invoked by uid 107); 5 Feb 2002 02:06:23 -0000 Message-ID: <20020205020623.75168.qmail@merton.aus.deuba.com> From: callum.gibson@db.com Subject: pthread_sigmask problem To: hackers@freebsd.org Date: Tue, 5 Feb 2002 13:06:23 +1100 (EST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I have an application which attempts to block all signals using pthread_sigmask(). I'm aware that this only works on the current thread, however this call occurs before any other threads are created and so should be inherited. I call it as follows: sigset_t signalSet; (void)sigfillset(&signalSet); (void)pthread_sigmask(SIG_BLOCK, &signalSet, NULL); However, it seems that signals such as SIGPIPE, SIGINT, etc will still kill the process. I also tried replacing the pthread_sigmask call with sigprocmask to see if it made any difference, which it didn't. The only other relevant info I can think of, is that I start up another thread specifically for catching SIGTERM, thusly: (void)sigemptyset(&signalSet); (void)sigaddset(&signalSet, SIGTERM); if (sigwait(&signalSet, &signo) < 0 || signo != SIGTERM) /* some error handling */; /* shutdown cleanly */ etc. This part still works as expected. Additionally, I have the same code working under Solaris threads (not pthreads on Solaris) fine, the only relevant change being the call thr_sigsetmask instead of pthread_sigmask. The same behaviour is exhibited on 4.3-RELEASE and 4.4-RELEASE. Any ideas on what is wrong? regards, Callum (c)2002 Callum Gibson callum.gibson@db.com Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620 ### The opinions in this message are mine and not Deutsche's ### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 18:24:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 5F88737B425 for ; Mon, 4 Feb 2002 18:24:49 -0800 (PST) Received: (qmail 8441 invoked by uid 100); 5 Feb 2002 02:24:47 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15455.17007.464520.955265@guru.mired.org> Date: Mon, 4 Feb 2002 20:24:47 -0600 To: Wilko Bulte Cc: Mike Meyer , hackers@FreeBSD.ORG Subject: Re: VCD file system? In-Reply-To: <20020205000307.C4704@freebie.xs4all.nl> References: <15455.3239.990461.982594@guru.mired.org> <20020205000307.C4704@freebie.xs4all.nl> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-STABLE-i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Context recovered from top posting.] Wilko Bulte types: > On Mon, Feb 04, 2002 at 04:35:19PM -0600, Mike Meyer wrote: > > I notice that I can put a Video CD in a Windows machine - even back to > > W98 - and it manages to show me folders and files on it. This makes me > > think that the thing has a file system on it. > > The question is then - what's the file system format, and is it > > available for FreeBSD or is someone working on it? > ISO9660, so plain old CDROM fs. > > At least the VCDs I bought in HongKong last year are like that. Here's what happens when I try and mount one on a SCSI cdrom drive: bash-2.05a$ mount /cdrom cd9660: /dev/cd0c: Invalid argument This one worked on Windows. At least, I managed to get it to play the video. Thanx, http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 19:18:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 9B4F037B430; Mon, 4 Feb 2002 19:18:12 -0800 (PST) Received: from pool0393.cvx40-bradley.dialup.earthlink.net ([216.244.43.138] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16Xw79-0007gM-00; Mon, 04 Feb 2002 19:17:47 -0800 Message-ID: <3C5F4ECE.9FC6FC3B@mindspring.com> Date: Mon, 04 Feb 2002 19:17:34 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Duncan Barclay Cc: Maksim Yevmenkin , freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Bluetooth stack for FreeBSD (full status) References: <3C5F003D.CA329159@digisle.net> <3C5F1CE4.1566F495@mindspring.com> <00a201c1add7$dc2e99e0$27c8a8c0@my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Duncan Barclay wrote: > There are now a few devices with Bluetooth in them. Sony has had a Viao > with it in for a while. Which model? My PCG-XG29 and the 505 a friend of mine recently bout don't have it. You'd think that with IBM being so "gung ho" about BlueTooth, that every ThinkPad, IBM "Palm Pilot", and Lexmark printer would have it. IBM is notoriously schitzophrenic, though, and it's pretty clear it's the technical people puching it, and manufacturing is far behind. > 802.11e is not gigabit wireless. .11e is quality of service enhancements > to the .11 MAC. You may be confusing it with .11a - 54Mbps at 5.2GHz or > the new .11g giving 54Mbps at 2.45GHz. Some people (Proxim) have .11a cards > that can operate at 108Mbps. This will have a reduced range though as they > probably halve the forward error correction somehow - maybe by > increased puncturing. Actually, I was thinking of 802.16, but I turned the "6" into an "e". There was a recent article on it, where the FCC had approved it, but the cell phone companies were all up in arms over their revenue model being shot in the head. It uses broadband over a large number of carrier frequencies, and *really* is gigabit wireless. The article also noted that radio astronomers were upset about the amount of "white noise" it would produce, which would make radio astronomy harder. > .11 without .11e is worse than Bluetooth for certain data types. For example > it cannot carry isochronous data. Bluetooth was never meant to compete > with .11 and was designed for a different purpose - mobile phones. > Wanderering around the UK's high streets a lot of phone shops and a > couple of the bigger consumer electronics chains are now selling > Bluetooth enabled stuff. I've also heard it sold as "the ultimate solution for PDAs", and "the replacement for IR links, which currently have to be line-of-sight", and "the way to get rid of cables". I think we'll eventually find out that "it's both a desert topping, and a floor wax!". 8-). But right now, it's a solution in search of a problem. All this is really going off topic, though... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 19:41:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1BCDE37B496 for ; Mon, 4 Feb 2002 19:40:24 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g153eNGr025270; Mon, 4 Feb 2002 22:40:23 -0500 (EST) Date: Mon, 4 Feb 2002 22:40:23 -0500 (EST) From: Daniel Eischen To: callum.gibson@db.com Cc: hackers@FreeBSD.ORG Subject: Re: pthread_sigmask problem In-Reply-To: <20020205020623.75168.qmail@merton.aus.deuba.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002 callum.gibson@db.com wrote: > Hi all, > I have an application which attempts to block all signals using > pthread_sigmask(). I'm aware that this only works on the current thread, > however this call occurs before any other threads are created and so > should be inherited. I call it as follows: > > sigset_t signalSet; > > (void)sigfillset(&signalSet); > (void)pthread_sigmask(SIG_BLOCK, &signalSet, NULL); > > However, it seems that signals such as SIGPIPE, SIGINT, etc will still > kill the process. I also tried replacing the pthread_sigmask call with > sigprocmask to see if it made any difference, which it didn't. Yes, at least with FreeBSD pthreads you have to either install a signal handler to catch these signals or to set the handler to SIG_IGN. When you set a threads signal mask, even if it is for all threads, you don't affect how signals are delivered to the process. The default action for SIGPIPE and SIGINT is to kill the process, so setting masks for threads doesn't affect this. > The only other relevant info I can think of, is that I start up another > thread specifically for catching SIGTERM, thusly: > > (void)sigemptyset(&signalSet); > (void)sigaddset(&signalSet, SIGTERM); > if (sigwait(&signalSet, &signo) < 0 || signo != SIGTERM) > /* some error handling */; > > /* shutdown cleanly */ > etc. > > This part still works as expected. POSIX explicitly states that if you use sigwait() and there are no handlers installed, that the effect is as if a handler is installed for the signal. So using sigwait() will automagically install a handler for the signal and then remove it once the sigwait() is completed (that is, unless the application already installed a handler for the signal, in which case sigwait doesn't install a handler). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 20: 2:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from imr1.aus.deuba.com (bagheera.aus.deuba.com [203.0.62.7]) by hub.freebsd.org (Postfix) with ESMTP id 02A0A37B41E for ; Mon, 4 Feb 2002 20:02:12 -0800 (PST) Received: from bmr1-e1.aus.deuba.com by imr1.aus.deuba.com id g1542AP04348; Tue, 5 Feb 2002 15:02:10 +1100 (EST) Received: from mailhost.aus.deuba.com [10.179.4.6] by bmr1-e1.aus.deuba.com id g15429n11413; Tue, 5 Feb 2002 15:02:09 +1100 (EST) Received: from merton.aus.deuba.com (merton.aus.deuba.com [10.179.88.22]) by mailhost.aus.deuba.com (8.9.1/8.9.1) with SMTP id PAA28628 for ; Tue, 5 Feb 2002 15:02:09 +1100 (EST) Received: (qmail 75764 invoked by uid 107); 5 Feb 2002 04:02:08 -0000 Message-ID: <20020205040208.75763.qmail@merton.aus.deuba.com> From: callum.gibson@db.com Subject: Re: pthread_sigmask problem To: eischen@pcnet1.pcnet.com Date: Tue, 5 Feb 2002 15:02:08 +1100 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "eischen@pcnet1.pcnet.com" at Feb 04, 2002 10:40:23 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks, Dan. (I saw your name come up in the archives next to a lot of threads/signals posts while I was looking for an answer to this so I wondered if you'd answer. :-) eischen@pcnet1.pcnet.com writes: }> However, it seems that signals such as SIGPIPE, SIGINT, etc will still }> kill the process. I also tried replacing the pthread_sigmask call with }> sigprocmask to see if it made any difference, which it didn't. }Yes, at least with FreeBSD pthreads you have to either install a signal }handler to catch these signals or to set the handler to SIG_IGN. When }you set a threads signal mask, even if it is for all threads, you don't }affect how signals are delivered to the process. The default action }for SIGPIPE and SIGINT is to kill the process, so setting masks for }threads doesn't affect this. I figured it was just using the default action for these signals. So, am I mistaken in thinking that SIG_BLOCK was supposed to ignore those signals or is this a pthreads bug on FreeBSD? Or just an "undefined" behaviour and a pthreads gotcha? It's worth noting that even with pthreads on Solaris I get the behaviour I was expecting (ie the signals are ignored) using either pthread_sigmask or sigprocmask. Also, is it documented anywhere which signals will behave like this? It seems like it would be all of them, as if the process still has an inherent signal mask independent of the threads running, thus requiring signal handlers to be installed for them. Hmm, it's a lot more verbose calling sigaction for every signal rather than a single pthread_sigmask call. I guess that's why we have for loops. C (c)2002 Callum Gibson callum.gibson@db.com Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620 ### The opinions in this message are mine and not Deutsche's ### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 20:30: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 0CA7337B41D for ; Mon, 4 Feb 2002 20:29:56 -0800 (PST) Received: from pool0393.cvx40-bradley.dialup.earthlink.net ([216.244.43.138] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16XxEk-0000IN-00; Mon, 04 Feb 2002 20:29:42 -0800 Message-ID: <3C5F5FB0.8003B28C@mindspring.com> Date: Mon, 04 Feb 2002 20:29:36 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: Wilko Bulte , Mike Meyer , hackers@FreeBSD.ORG Subject: Re: VCD file system? References: <15455.3239.990461.982594@guru.mired.org> <20020205000307.C4704@freebie.xs4all.nl> <15455.17007.464520.955265@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: > Here's what happens when I try and mount one on a SCSI cdrom drive: > > bash-2.05a$ mount /cdrom > cd9660: /dev/cd0c: Invalid argument > > This one worked on Windows. At least, I managed to get it to play the > video. Do you read German? Here is a Linux version: http://home.t-online.de/home/ritzert/videocd.html The VideoCD format was never really publically documented back when it was popular, and there were some programs that reverse engineered it that Phillips went after (MPegTV?); I remember that the last set of Commodore hardware had a license for it, and it was held as a closely guarded secret at that time. It's actually pretty trivial; you need to be able to read the full sector, instead of just the smaller "formatted" data portion of it; this is already supported in an CDROM hardware that can read raw audio off a CDROM, which is pretty much any CDROM drive since the first one that could do it in the SGI Indy, and the first one you could legally buy in the U.S. seperate from a system (the Toshiba 3401B; I have one, of course). Probably, you are talking about a very old Video CD (CD-i), which is Green Book standard. Panasonix and Matsushita CD drives can't read these, so it might just be a difference in hardware. If you are talking about a newer one, then it's a White Book standard, or, the newer Video CD 2.0. To get a copy of this, you have to be a licensee from Phillips of one of: o CD Information Agreement o Software Dev Package o CD Disc/Player o VideoCD Disc/Player See: -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 20:30:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from imr1.aus.deuba.com (bagheera.aus.deuba.com [203.0.62.7]) by hub.freebsd.org (Postfix) with ESMTP id D116337B421 for ; Mon, 4 Feb 2002 20:30:55 -0800 (PST) Received: from bmr1-e1.aus.deuba.com by imr1.aus.deuba.com id g154UrP06769; Tue, 5 Feb 2002 15:30:53 +1100 (EST) Received: from mailhost.aus.deuba.com [10.179.4.6] by bmr1-e1.aus.deuba.com id g154Urn12965; Tue, 5 Feb 2002 15:30:53 +1100 (EST) Received: from merton.aus.deuba.com (merton.aus.deuba.com [10.179.88.22]) by mailhost.aus.deuba.com (8.9.1/8.9.1) with SMTP id PAA07732 for ; Tue, 5 Feb 2002 15:30:52 +1100 (EST) Received: (qmail 75888 invoked by uid 107); 5 Feb 2002 04:30:52 -0000 Message-ID: <20020205043052.75887.qmail@merton.aus.deuba.com> From: callum.gibson@db.com Subject: Re: pthread_sigmask problem To: hackers@freebsd.org Date: Tue, 5 Feb 2002 15:30:52 +1100 (EST) Cc: eischen@pcnet1.pcnet.com In-Reply-To: from "callum" at Feb 05, 2002 03:02:08 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG callum writes: }handlers to be installed for them. Hmm, it's a lot more verbose calling }sigaction for every signal rather than a single pthread_sigmask call. }I guess that's why we have for loops. Doh! You can specify a set of signals with sigaction. Sorry about that. C (c)2002 Callum Gibson callum.gibson@db.com Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620 ### The opinions in this message are mine and not Deutsche's ### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 20:42:18 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id 60AC837B416 for ; Mon, 4 Feb 2002 20:42:13 -0800 (PST) Received: (qmail 15810 invoked from network); 5 Feb 2002 04:42:11 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.155.36]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Feb 2002 04:42:11 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200202042157.g14LvaX02099@vashon.polstra.com> Date: Mon, 04 Feb 2002 23:42:09 -0500 (EST) From: John Baldwin To: John Polstra Subject: Re: A question about timecounters Cc: dominic_marks@btinternet.com, hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 04-Feb-02 John Polstra wrote: > In article <20020204213450.E923@gallium.localdomain>, > Dominic Marks wrote: >> On Mon, Feb 04, 2002 at 01:21:25PM -0800, John Polstra wrote: >> > I'm trying to understand the timecounter code, and in particular the >> > reason for the "microuptime went backwards" messages which I see on >> > just about every machine I have, whether running -stable or -current. >> >> I see them everywhere with -CURRENT, but not at all with -STABLE. This is >> with two seperate machines. Perhaps that may add clues. > > I'm looking for something less empirical than that. When somebody > says this problem is caused by too much interrupt latency, I assume > they have a mental model of what is going wrong when this excessive > latency occurs. Given that, it should be possible to make a statement > like, "If X is never locked out for longer than Y, this problem > cannot happen." I'm looking for definitions of X and Y. X might be > hardclock() or softclock() or non-interrupt kernel processing. Y > would be some measure of time, probably a function of HZ and/or the > timecounter frequency. X is hardclock I think, since hardclock() calls tc_windup(). I'm not sure what Y is except that it is indeed a known value. phk should know as he is Mr. Timecounter. > John > -- > John Polstra > John D. Polstra & Co., Inc. Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 20:43:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 3A73A37B41C for ; Mon, 4 Feb 2002 20:42:29 -0800 (PST) Received: (qmail 9658 invoked from network); 5 Feb 2002 04:42:28 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.155.36]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Feb 2002 04:42:28 -0000 Message-ID: X-Mailer: XFMail 1.4.0 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: Mon, 04 Feb 2002 23:42:26 -0500 (EST) From: John Baldwin To: Robert Watson Subject: Re: FreeBSD 5.x Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, Alp Atici Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 20-Jan-02 Robert Watson wrote: > > On Sat, 19 Jan 2002, Alp Atici wrote: > >> Is gcc 3.x going to be the default compiler starting from FBSD 5.x >> series? Is the development on current branch compiled using gcc 3.0 (or >> up)? >> >> Is 5.x series going to be based on a preemptible kernel? > > Can't answer the gcc question, but yes, John Baldwin currently has support > for preemption in his SMPng development tree. The kernel is already somewhat preemptive. The kernel in 5.0 will certainly be preemptible, as making a kernel SMP safe makes it laregly preemptible (i.e, safe for preemption) as well. Making the kernel "fully" preemptive (i.e., we can switch tasks on any setrunqueue() if the conditions favor that) is actually a fairly esay thing to do, I'm just not sure how well it works right now. :) I just recently fixed some bugs in the alpha pmap code that should help out with getting our kernel closer to that goal. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 21:26:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9145F37B425 for ; Mon, 4 Feb 2002 21:26:40 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g155QdmO005018; Tue, 5 Feb 2002 00:26:39 -0500 (EST) Date: Tue, 5 Feb 2002 00:26:39 -0500 (EST) From: Daniel Eischen To: callum.gibson@db.com Cc: hackers@FreeBSD.ORG Subject: Re: pthread_sigmask problem In-Reply-To: <20020205040208.75763.qmail@merton.aus.deuba.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002 callum.gibson@db.com wrote: > Thanks, Dan. (I saw your name come up in the archives next to a lot of > threads/signals posts while I was looking for an answer to this so I > wondered if you'd answer. :-) > > eischen@pcnet1.pcnet.com writes: > }> However, it seems that signals such as SIGPIPE, SIGINT, etc will still > }> kill the process. I also tried replacing the pthread_sigmask call with > }> sigprocmask to see if it made any difference, which it didn't. > }Yes, at least with FreeBSD pthreads you have to either install a signal > }handler to catch these signals or to set the handler to SIG_IGN. When > }you set a threads signal mask, even if it is for all threads, you don't > }affect how signals are delivered to the process. The default action > }for SIGPIPE and SIGINT is to kill the process, so setting masks for > }threads doesn't affect this. > > I figured it was just using the default action for these signals. So, am > I mistaken in thinking that SIG_BLOCK was supposed to ignore those signals > or is this a pthreads bug on FreeBSD? Or just an "undefined" behaviour > and a pthreads gotcha? It's worth noting that even with pthreads on Solaris > I get the behaviour I was expecting (ie the signals are ignored) using > either pthread_sigmask or sigprocmask. It's not clear to me that using pthread_sigmask should change the default behaviour that signals have on the process. Thread signal masks seem to be independent of installed signal handlers and default actions that signals have on the process. > Also, is it documented anywhere which signals will behave like this? It > seems like it would be all of them, as if the process still has an inherent > signal mask independent of the threads running, thus requiring signal > handlers to be installed for them. Hmm, it's a lot more verbose calling > sigaction for every signal rather than a single pthread_sigmask call. > I guess that's why we have for loops. See sigaction(2). From your other email: > Doh! You can specify a set of signals with sigaction. Sorry about that. Nope, you can only install a handler for one signal at a time. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 21:48:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from imr1.aus.deuba.com (bagheera.aus.deuba.com [203.0.62.7]) by hub.freebsd.org (Postfix) with ESMTP id 864F837B41F for ; Mon, 4 Feb 2002 21:48:25 -0800 (PST) Received: from bmr1-e1.aus.deuba.com by imr1.aus.deuba.com id g155mLP12513; Tue, 5 Feb 2002 16:48:23 +1100 (EST) Received: from mailhost.aus.deuba.com [10.179.4.6] by bmr1-e1.aus.deuba.com id g155mLn17179; Tue, 5 Feb 2002 16:48:21 +1100 (EST) Received: from merton.aus.deuba.com (merton.aus.deuba.com [10.179.88.22]) by mailhost.aus.deuba.com (8.9.1/8.9.1) with SMTP id QAA17663 for ; Tue, 5 Feb 2002 16:48:20 +1100 (EST) Received: (qmail 76301 invoked by uid 107); 5 Feb 2002 05:48:20 -0000 Message-ID: <20020205054820.76300.qmail@merton.aus.deuba.com> From: callum.gibson@db.com Subject: Re: pthread_sigmask problem To: eischen@pcnet1.pcnet.com Date: Tue, 5 Feb 2002 16:48:20 +1100 (EST) Cc: hackers@freebsd.org In-Reply-To: from "eischen@pcnet1.pcnet.com" at Feb 05, 2002 12:26:39 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Let me know if I should take this off list now since it's probably reached its limit of interest for most people. eischen@pcnet1.pcnet.com writes: }> I figured it was just using the default action for these signals. So, am }> I mistaken in thinking that SIG_BLOCK was supposed to ignore those signals }> or is this a pthreads bug on FreeBSD? Or just an "undefined" behaviour }> and a pthreads gotcha? It's worth noting that even with pthreads on Solaris }> I get the behaviour I was expecting (ie the signals are ignored) using }> either pthread_sigmask or sigprocmask. }It's not clear to me that using pthread_sigmask should change }the default behaviour that signals have on the process. Thread }signal masks seem to be independent of installed signal handlers }and default actions that signals have on the process. Well, it depends on what it means to block a signal. From reading the manpage it seems to indicate that delivery of these signals is deferred indefinitely until a thread sigwaits for them or if a thread doesn't have them blocked. Since I was doing this as the very first thing in the process (ie there are no other threads), it would imply that all other threads created from then on would also block those signals. This is certainly how it behaves on Solaris. Haven't checked Linux but will report back if you're interested. In practice, FreeBSD's thread library probably has internal threads operating in the background which are there from the outset and don't inherit this mask and it's _those_ threads which are taking delivery of the fatal signals. }> Also, is it documented anywhere which signals will behave like this? It }> seems like it would be all of them, as if the process still has an inherent }> signal mask independent of the threads running, thus requiring signal }> handlers to be installed for them. Hmm, it's a lot more verbose calling }> sigaction for every signal rather than a single pthread_sigmask call. }> I guess that's why we have for loops. }See sigaction(2). Yeah, doesn't really explain if the process is anything more than the sum of its threads. Under Solaris that's all it is. A non-threaded process is actually a process with a single thread. This is the state of the process when I do the sigprocmask/thr_setsigmask/pthread_sigmask call. It's only after you make your first call to the thread library proper (by creating a new thread) that the background threads appear (this is on Solaris). I suspect this is not how it works on FreeBSD - the method of compilation even gives a clue to this (a special compiler directive). Even without making any new threads a FreeBSD threaded program will probably have these internal threads (I'm speculating here as I don't have the equivalent of pstack to be able to check that). I guess it also has something to do with being a userland implementation? I guess the question boils down to: Should an application be able to operate oblivious to the existence of internal threads? Does a process exist apart from the threads that make it up? Anyway, sigaction does the trick - it just seems superfluous on Solaris, at least. }>From your other email: }> Doh! You can specify a set of signals with sigaction. Sorry about that. }Nope, you can only install a handler for one signal at a time. Spotted that just after I sent it but I figured replying to myself twice in a row was Really Bad (tm). I was right the first time. C (c)2002 Callum Gibson callum.gibson@db.com Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620 ### The opinions in this message are mine and not Deutsche's ### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Feb 4 21:59:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 6B2E737B41D for ; Mon, 4 Feb 2002 21:59:25 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA09574; Tue, 5 Feb 2002 16:59:03 +1100 Date: Tue, 5 Feb 2002 17:01:29 +1100 (EST) From: Bruce Evans X-X-Sender: To: Mike Silbersack Cc: Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020204120547.B2144-100000@patrocles.silby.com> Message-ID: <20020205163210.G25358-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 4 Feb 2002, Mike Silbersack wrote: > On Tue, 5 Feb 2002, Bruce Evans wrote: > > I haven't done anything to clean up the patch. I hope the problem > > will go away in future versions of gcc (align the stack at runtime in > > the few routines that actually need it). > > Well, if Linux aligns the initial stack, the chance that gcc will have > auto-alignment added sounds to be about zero. You might as well go ahead > with your patch when you get a chance. There is a nonzero probability that the pessimization of aligning in almost every routine will be fixed someday. Actually, the pessimization is worse -- the alignment is done before every call. Example: %%% foo.c: foo() { f1(1); f2(2); f3(3.0); } %%% gcc -O -S [-mpreferred-stack boundary] currently generates the following code for this: %%% .file "z.c" .version "01.01" gcc2_compiled.: .section .rodata .p2align 3 .LC0: .long 0x0,0x40080000 .text .p2align 2,0x90 .globl foo .type foo,@function foo: pushl %ebp movl %esp,%ebp subl $8,%esp # <- extra instruction for alignment (for foo) addl $-12,%esp # <- extra instruction for alignment (for f1) pushl $1 call f1 addl $-12,%esp # <- extra instruction for alignment (for f2) pushl $2 call f2 addl $32,%esp # <- extra instruction for alignment (for f3) addl $-8,%esp # <- extra instruction for alignment (another) pushl .LC0+4 pushl .LC0 call f3 leave ret .Lfe1: .size foo,.Lfe1-foo .ident "GCC: (c) 2.95.3 20010315 (release)" %%% It should generate something like: .file "z.c" .version "01.01" gcc2_compiled.: .section .rodata .p2align 3 .LC0: .long 0x0,0x40080000 .text .p2align 2,0x90 .globl foo .type foo,@function foo: pushl %ebp movl %esp,%ebp andl $~0x7,%esp # <- extra instruction for alignment (for foo) # Only needed since foo() uses FPU. # 8-byte alignment enough for doubles? # Adjust in prologue so that there are # hopefully no alloca()-like issues, except # we need a frame pointer to restore %esp. pushl $1 call f1 pushl $2 call f2 pushl .LC0+4 pushl .LC0 call f3 leave ret .Lfe1: .size foo,.Lfe1-foo .ident "GCC: (c) 2.95.3 20010315 (release)" %%% My patch is not suitable for committing verbatim. It has 2 or 3 XXX's. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 1:56: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by hub.freebsd.org (Postfix) with ESMTP id 461BD37B419 for ; Tue, 5 Feb 2002 01:56:01 -0800 (PST) Received: (from yar@localhost) by comp.chem.msu.su (8.11.1/8.11.1) id g159tvL11207 for hackers@freebsd.org; Tue, 5 Feb 2002 12:55:57 +0300 (MSK) (envelope-from yar) Date: Tue, 5 Feb 2002 12:55:57 +0300 From: Yar Tikhiy To: hackers@freebsd.org Subject: Get disk device size? Message-ID: <20020205125557.A10266@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, Could anyone point out at an ioctl or any other way to get a disk device size granted the device has no BSD label or PC slice table on it? Ways for both the userland and kernel are welcome. Thanks in advance! -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 2:57:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id CAB4B37B405 for ; Tue, 5 Feb 2002 02:57:42 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.6/8.11.6) id g15Ajbv77495; Tue, 5 Feb 2002 10:45:37 GMT (envelope-from nik) Date: Tue, 5 Feb 2002 10:45:37 +0000 From: Nik Clayton To: Bruce Evans Cc: Mike Silbersack , Michal Mertl , hackers@freebsd.org, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues Message-ID: <20020205104537.S5732@clan.nothing-going-on.org> References: <20020204120547.B2144-100000@patrocles.silby.com> <20020205163210.G25358-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mln0rGgUGuXEqmuI" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020205163210.G25358-100000@gamplex.bde.org>; from bde@zeta.org.au on Tue, Feb 05, 2002 at 05:01:29PM +1100 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --mln0rGgUGuXEqmuI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Bruce, On Tue, Feb 05, 2002 at 05:01:29PM +1100, Bruce Evans wrote: > My patch is not suitable for committing verbatim. It has 2 or 3 XXX's. Do you make these patches available anywhere, so that other people can look over them and maybe help you on the XXX'd sections? N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --mln0rGgUGuXEqmuI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxft9EACgkQk6gHZCw343WzBACeMNRQsombeYj1vLlqyx5H1N5Q 9poAn1tX+aRMag4ztcXBYHLkPcDviw3a =tfr1 -----END PGP SIGNATURE----- --mln0rGgUGuXEqmuI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 3:48:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D046A37B425; Tue, 5 Feb 2002 03:48:10 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15Bj2M86053; Tue, 5 Feb 2002 12:45:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@FreeBSD.ORG, msmith@hub.freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Mon, 04 Feb 2002 17:41:59 PST." <200202050141.g151fxW02520@vashon.polstra.com> Date: Tue, 05 Feb 2002 12:45:02 +0100 Message-ID: <86051.1012909502@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202050141.g151fxW02520@vashon.polstra.com>, John Polstra writes: >Mike Smith wrote: >> >> It's not necessarily caused by interrupt latency. Here's the assumption >> that's being made. >[...] > >Thanks for the superb explanation! I appreciate it. My apologies for never getting the timecounter paper finished and published, I should really do that... >That's the global variable named "timecounter", right? I did notice >one potential problem: that variable is not declared volatile. So >in this part ... This may be a problem, I have yet to see GCC make different code for that but I should probably have committed the "volatile" anyway. >I also noticed this in tco_forward(): > > tco = timecounter; > tc = sync_other_counter(); > [...] > if (tco->tc_poll_pps) > >But sync_other_counter() loads its own copy of "timecounter", >and there's no guarantee it hasn't changed from the value that >tco_forward() saved in its local variable. I'm not sure yet if >that's a potential problem. It could corrected by passing "tco" as >an argument to sync_other_counter. I'll try that too. This code is actually correct, the tc_poll_pps needs to be done on the "old" timecounter, because that would be the reference for any captured hardware timestamps, if I did it on the new timecounter I might get negative deltas which would complicate things. Also the new timecounter may have a changed frequency/offset (tickadj/ntpd and all that). >> There are a couple of possible problems with this mechanism. >> >> One is that the ring "catches up" with your saved copy of the >> "current" pointer, ie. inbetween fetching the pointer and reading the >> timecounter contents, the "next" pointer passes over you again in such >> a fashion that you get garbage out of the structure. This is unlikely. >> Another is that there is a race between multiple updaters of the >> timecounter; if two parties are both updating the "next" timecounter >> along with another party trying to get the "current" time, this could >> cause corruption. I have worries in this respect with SMPng, but have yet to see a corrupted timecounter ring. There is one more failure mode which you have overlooked: The individual timecounters maintain a binary counter of a certain width, if interrupt latency gets too bad, this may overflow. This is a non-issue for the TSC, which is 64bit wide in hardware. It should also be a non-issue for the PIIX which is at least 24 bits in hardware. But the i8254 is a piece of shit in this context, and due to circumstances (apm being enabled0 most machines end up using the i8254 by default. My (and I belive Bruce's) diagnosis so far is that most problems come from the i8254 timecounter. I made a commit recently which made the core-code more robust to bad interrupt jitter/latency, basically it would return timestamps with too many microseconds or nanoseconds because it only tried to roll over to seconds ones. Now it while()'s over that loop. Hope this helps... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 5:13:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 5B6DF37B405; Tue, 5 Feb 2002 05:13:17 -0800 (PST) Received: from mailrelay1.informatik.tu-muenchen.de (mailrelay.informatik.tu-muenchen.de [131.159.2.33]) by mailout.informatik.tu-muenchen.de (Postfix) with ESMTP id 7914161AF; Tue, 5 Feb 2002 14:13:12 +0100 (MET) Received: from atrbg11.informatik.tu-muenchen.de (atrbg11.informatik.tu-muenchen.de [131.159.24.91]) by mailrelay1.informatik.tu-muenchen.de (Postfix) with ESMTP id 8B7137942; Tue, 5 Feb 2002 14:13:12 +0100 (MET) Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 44653137FF; Tue, 5 Feb 2002 14:13:12 +0100 (CET) Date: Tue, 5 Feb 2002 14:13:12 +0100 From: Daniel Lang To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: autotuning kernel vars Message-ID: <20020205131312.GA58643@atrbg11.informatik.tu-muenchen.de> Reply-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y+ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, (sorry for posting this to two lists, Reply-To: is set.) I've just built a new kernel for a just upgraded box to 4.5-STABLE. I've included NMBCLUSTERS=0 and NBUF=0 to try the auto-sizing feature as documented in LINT The box is P4-1400 with 1.5GB RAM, (not)running: FreeBSD 4.5-STABLE #2: Tue Feb 5 12:18:11 CET 2002 root@atleo5.leo.org:/usr/obj/usr/src/sys/ATLEO5 The kernel does not even boot, because of: [..] real memory = 1610596352 (1572848K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x003a1000 - 0x5fff3fff, 1606758400 bytes (392275 pages) kmem_suballoc: bad status return of 1. panic: kmem_suballoc [..] Now, what I remember it may have to do with some of the tunings failing. I also have maxusers=512 (but this caused no problems until now). Any advice, even "don't set NMBCLUSTERS to 0", preferred with "because in your setup XXXX happens", but greatly appreciated in any way. TIA, Daniel -- IRCnet: Mr-Spock - "Do you love yourself ?" - "Yes!" (Isar 12) - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 7:53:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d179.as0.nwbl0.wi.voyager.net [169.207.130.181]) by hub.freebsd.org (Postfix) with ESMTP id 840B937B41A; Tue, 5 Feb 2002 07:53:02 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g159t8C01650; Tue, 5 Feb 2002 09:55:19 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 5 Feb 2002 09:55:08 +0000 (GMT) From: Mike Silbersack To: Daniel Lang , Cc: freebsd-hackers@freebsd.org Subject: Re: autotuning kernel vars In-Reply-To: <20020205131312.GA58643@atrbg11.informatik.tu-muenchen.de> Message-ID: <20020205094939.A1617-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Daniel Lang wrote: > Hi, > > (sorry for posting this to two lists, Reply-To: is set.) > > I've just built a new kernel for a just upgraded box to > 4.5-STABLE. I've included > > NMBCLUSTERS=0 and > NBUF=0 > > to try the auto-sizing feature as documented in LINT > > Any advice, even "don't set NMBCLUSTERS to 0", preferred with > "because in your setup XXXX happens", but greatly appreciated > in any way. > > TIA, > Daniel LINT says, and I quote: # # The `maxusers' parameter controls the static sizing of a number of # internal system tables by a formula defined in subr_param.c. Setting # maxusers to 0 will cause the system to auto-size based on physical # memory. # Hence, you should set maxusers to 0, not nmbclusters, not nbuf. In fact, for autosizing to work, you should not specify nmbclusters or nbuf whatsoever. The autotuning simply sets maxusers to megs of memory / 2. While this is a huge improvement from having maxusers default to 32 for everyone running GENERIC, it's not some magic feature that will turbocharge your machine. If you have been comfortable with manually setting up your configuration, you do not need to worry about autosizing. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 8: 0: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d179.as0.nwbl0.wi.voyager.net [169.207.130.181]) by hub.freebsd.org (Postfix) with ESMTP id C1BD737B420; Tue, 5 Feb 2002 07:59:50 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g15A3EV01685; Tue, 5 Feb 2002 10:03:14 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 5 Feb 2002 10:03:14 +0000 (GMT) From: Mike Silbersack To: Daniel Lang , Cc: freebsd-hackers@freebsd.org Subject: Re: autotuning kernel vars In-Reply-To: <20020205094939.A1617-100000@patrocles.silby.com> Message-ID: <20020205100134.B1617-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Mike Silbersack wrote: > LINT says, and I quote: > > # > # The `maxusers' parameter controls the static sizing of a number of > # internal system tables by a formula defined in subr_param.c. Setting > # maxusers to 0 will cause the system to auto-size based on physical > # memory. > # Hmph, apologies. I was not aware of the comment in LINT that suggested setting nmbclusters / nbuf to 0. This comment predates the autoscaling code, and is wrong. I'll go remove it. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 8: 9:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by hub.freebsd.org (Postfix) with ESMTP id A084637B432; Tue, 5 Feb 2002 08:09:48 -0800 (PST) Received: from mailrelay1.informatik.tu-muenchen.de (mailrelay.informatik.tu-muenchen.de [131.159.2.33]) by mailout.informatik.tu-muenchen.de (Postfix) with ESMTP id CDE256105; Tue, 5 Feb 2002 17:09:47 +0100 (MET) Received: from atrbg11.informatik.tu-muenchen.de (atrbg11.informatik.tu-muenchen.de [131.159.24.91]) by mailrelay1.informatik.tu-muenchen.de (Postfix) with ESMTP id DC86B7942; Tue, 5 Feb 2002 17:09:47 +0100 (MET) Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 82861137FF; Tue, 5 Feb 2002 17:09:47 +0100 (CET) Date: Tue, 5 Feb 2002 17:09:47 +0100 From: Daniel Lang To: Mike Silbersack Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: autotuning kernel vars Message-ID: <20020205160947.GE58643@atrbg11.informatik.tu-muenchen.de> References: <20020205094939.A1617-100000@patrocles.silby.com> <20020205100134.B1617-100000@patrocles.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020205100134.B1617-100000@patrocles.silby.com> User-Agent: Mutt/1.3.27i X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r++>+++ y+ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Mike, Mike Silbersack wrote on Tue, Feb 05, 2002 at 10:03:14AM +0000: [..] > Hmph, apologies. I was not aware of the comment in LINT that suggested > setting nmbclusters / nbuf to 0. This comment predates the autoscaling > code, and is wrong. I'll go remove it. Ah, well, thanks. That clarifies it. So for I don't specify any values for NMBCLUSTERS and NBUF, leaving maxusers at 512, and just watch how the machine performs. I just thought about increasing NMBCLUSTERS because somewhere (I don't remember) it was mentioned, that some new code (larger default buffers somewhere in the ip stack?) could make one run out of them. But I guess with maxusers=512 I'm already on the safe side. Thanks, Daniel -- IRCnet: Mr-Spock - kommst du siehst du, gehst du hast du, weisst du, krass! - Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 8:30:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0C2D837B404; Tue, 5 Feb 2002 08:30:35 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g15GUXi09713; Tue, 5 Feb 2002 09:30:34 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g15GUTL30336; Tue, 5 Feb 2002 09:30:33 -0700 (MST) (envelope-from imp@village.org) Date: Tue, 05 Feb 2002 09:30:06 -0700 (MST) Message-Id: <20020205.093006.104650505.imp@village.org> To: yar@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: Get disk device size? From: "M. Warner Losh" In-Reply-To: <20020205125557.A10266@comp.chem.msu.su> References: <20020205125557.A10266@comp.chem.msu.su> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <20020205125557.A10266@comp.chem.msu.su> Yar Tikhiy writes: : Could anyone point out at an ioctl or any other way to get a disk : device size granted the device has no BSD label or PC slice table : on it? Ways for both the userland and kernel are welcome. For userland, look at how fdisk and/or disklabel get it. For kernel, look at kern/subr_disk*.c Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 8:36: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F2F437B405; Tue, 5 Feb 2002 08:36:01 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g15GZxi09756; Tue, 5 Feb 2002 09:36:00 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g15GZwL30376; Tue, 5 Feb 2002 09:35:58 -0700 (MST) (envelope-from imp@village.org) Date: Tue, 05 Feb 2002 09:35:35 -0700 (MST) Message-Id: <20020205.093535.103565337.imp@village.org> To: phk@critter.freebsd.dk Cc: jdp@polstra.com, hackers@FreeBSD.ORG, msmith@hub.freebsd.org Subject: Re: A question about timecounters From: "M. Warner Losh" In-Reply-To: <86051.1012909502@critter.freebsd.dk> References: <200202050141.g151fxW02520@vashon.polstra.com> <86051.1012909502@critter.freebsd.dk> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <86051.1012909502@critter.freebsd.dk> Poul-Henning Kamp writes: : But the i8254 is a piece of shit in this context, and due to : circumstances (apm being enabled0 most machines end up using the : i8254 by default. : : My (and I belive Bruce's) diagnosis so far is that most problems : come from the i8254 timecounter. We measured pps interrupts with the i8254 timecounter in a fast interrupt handler via the parallel port (yes, we hacked it to give us a fast interrupt). We found lots of outliers on the order of a few milliseconds in the data that we had to discard because they were obviously bogus. We don't know if this is because of interrupt latency or because of bugs in the 8254 timecounter code/hardware. At the time, it wasn't important enough to do a detailed numerology on to see if more data couldn't be mined from it or not. And the data that we saw the outliers in was somewhat processed from the original data... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 8:42:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7BC6837B41C; Tue, 5 Feb 2002 08:42:40 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15GdRM89798; Tue, 5 Feb 2002 17:39:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "M. Warner Losh" Cc: jdp@polstra.com, hackers@FreeBSD.ORG, msmith@hub.freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 09:35:35 MST." <20020205.093535.103565337.imp@village.org> Date: Tue, 05 Feb 2002 17:39:27 +0100 Message-ID: <89796.1012927167@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020205.093535.103565337.imp@village.org>, "M. Warner Losh" writes: >In message: <86051.1012909502@critter.freebsd.dk> > Poul-Henning Kamp writes: >: But the i8254 is a piece of shit in this context, and due to >: circumstances (apm being enabled0 most machines end up using the >: i8254 by default. >: >: My (and I belive Bruce's) diagnosis so far is that most problems >: come from the i8254 timecounter. > >We measured pps interrupts with the i8254 timecounter in a fast >interrupt handler via the parallel port (yes, we hacked it to give us >a fast interrupt). We found lots of outliers on the order of a few >milliseconds in the data that we had to discard because they were >obviously bogus. We don't know if this is because of interrupt >latency or because of bugs in the 8254 timecounter code/hardware. At >the time, it wasn't important enough to do a detailed numerology on to >see if more data couldn't be mined from it or not. And the data that >we saw the outliers in was somewhat processed from the original >data... I have not tried to measure the i8254 against my hardware solution, but by now I belive that certain bogus chipsets may have bummed the 'latch' command or more than that maybe. Anyway, some, but not all of the i8254 issues could be eased up a bit if we lost the pcaudio crap and used the RTC's 128 Hz signal for Hz and let the i8254 run at a 65536 count all the time. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9: 6:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id D61EA37B422; Tue, 5 Feb 2002 09:06:52 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15H6qo53253; Tue, 5 Feb 2002 09:06:52 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15H6pp03714; Tue, 5 Feb 2002 09:06:51 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 09:06:51 -0800 (PST) Message-Id: <200202051706.g15H6pp03714@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: jhb@freebsd.org Subject: Re: A question about timecounters In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , John Baldwin wrote: > > > like, "If X is never locked out for longer than Y, this problem > > cannot happen." I'm looking for definitions of X and Y. X might be > > hardclock() or softclock() or non-interrupt kernel processing. Y > > would be some measure of time, probably a function of HZ and/or the > > timecounter frequency. > > X is hardclock I think, since hardclock() calls tc_windup(). That makes sense, but on the other hand hardclock seems unlikely to be delayed by much. The only thing that can block hardclock is another hardclock, an splclock, or an splhigh. And, maybe, splstatclock. I'm talking about -stable here, which is where I'm doing my experiments. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:10:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 67E6A37B419; Tue, 5 Feb 2002 09:10:40 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15H7YM90117; Tue, 5 Feb 2002 18:07:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 09:06:51 PST." <200202051706.g15H6pp03714@vashon.polstra.com> Date: Tue, 05 Feb 2002 18:07:34 +0100 Message-ID: <90115.1012928854@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051706.g15H6pp03714@vashon.polstra.com>, John Polstra writes: >In article , >John Baldwin wrote: >> >> > like, "If X is never locked out for longer than Y, this problem >> > cannot happen." I'm looking for definitions of X and Y. X might be >> > hardclock() or softclock() or non-interrupt kernel processing. Y >> > would be some measure of time, probably a function of HZ and/or the >> > timecounter frequency. >> >> X is hardclock I think, since hardclock() calls tc_windup(). > >That makes sense, but on the other hand hardclock seems unlikely to be >delayed by much. The only thing that can block hardclock is another >hardclock, an splclock, or an splhigh. And, maybe, splstatclock. I'm >talking about -stable here, which is where I'm doing my experiments. Try swapping so you use the RTC for hardclock & statclock. Let the i8254 run with 65536 divisor and do only timecounter service. That would be a very interresting experiment. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:21:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 53EA937B428 for ; Tue, 5 Feb 2002 09:21:50 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15HLVo53326; Tue, 5 Feb 2002 09:21:32 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15HLVW03792; Tue, 5 Feb 2002 09:21:31 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 09:21:31 -0800 (PST) Message-Id: <200202051721.g15HLVW03792@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <86051.1012909502@critter.freebsd.dk> References: <86051.1012909502@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <86051.1012909502@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202050141.g151fxW02520@vashon.polstra.com>, John Polstra writes: > >That's the global variable named "timecounter", right? I did notice > >one potential problem: that variable is not declared volatile. So > >in this part ... > > This may be a problem, I have yet to see GCC make different code for > that but I should probably have committed the "volatile" anyway. It should be committed, but it is not causing the problem in this case. I changed it and then compared MD5s of the object files. The only changes that resulted were unimportant. > >I also noticed this in tco_forward(): > > > > tco = timecounter; > > tc = sync_other_counter(); > > [...] > > if (tco->tc_poll_pps) > > > >But sync_other_counter() loads its own copy of "timecounter", > >and there's no guarantee it hasn't changed from the value that > >tco_forward() saved in its local variable. I'm not sure yet if > >that's a potential problem. It could corrected by passing "tco" as > >an argument to sync_other_counter. I'll try that too. > > This code is actually correct, the tc_poll_pps needs to be done on > the "old" timecounter, because that would be the reference for any > captured hardware timestamps, if I did it on the new timecounter I > might get negative deltas which would complicate things. Also the > new timecounter may have a changed frequency/offset (tickadj/ntpd > and all that). I don't think I follow your reasoning here. If the call to sync_other_counter were inlined, we'd have something like this: tco = timecounter; tco_in_sync_other_counter = timecounter; [...] if (tco->tc_poll_pps) Obviously tco and tco_in_sync_other_counter will have the same value almost all of the time, so the code can't be relying on them being different. Anyway, I realize now that this also isn't the problem, because tco_forward is only ever called at splclock. It can't be interrupted or re-entered, at least not on the uniprocessor -stable systems I'm looking at. > There is one more failure mode which you have overlooked: The individual > timecounters maintain a binary counter of a certain width, if interrupt > latency gets too bad, this may overflow. > > This is a non-issue for the TSC, which is 64bit wide in hardware. Many of the systems where I see this problem are using the TSC as the timecounter. They don't have APM in the kernel, and they aren't running ntpd. I.e., it's not only the i8254 that's the problem. The fastest of these systems is a 1.13 GHz PIII, and it would take the 32 bits of the TSC which are actually used 3.8 seconds to wrap around. > Hope this helps... Yep, thanks. I have some ideas of other things to try. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:23:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 97ADD37B484 for ; Tue, 5 Feb 2002 09:23:20 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15HNHo53339; Tue, 5 Feb 2002 09:23:17 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15HNH603801; Tue, 5 Feb 2002 09:23:17 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 09:23:17 -0800 (PST) Message-Id: <200202051723.g15HNH603801@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <90115.1012928854@critter.freebsd.dk> References: <90115.1012928854@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <90115.1012928854@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051706.g15H6pp03714@vashon.polstra.com>, John Polstra writes: > >In article , > >John Baldwin wrote: > >> > >> > like, "If X is never locked out for longer than Y, this problem > >> > cannot happen." I'm looking for definitions of X and Y. X might be > >> > hardclock() or softclock() or non-interrupt kernel processing. Y > >> > would be some measure of time, probably a function of HZ and/or the > >> > timecounter frequency. > >> > >> X is hardclock I think, since hardclock() calls tc_windup(). > > > >That makes sense, but on the other hand hardclock seems unlikely to be > >delayed by much. The only thing that can block hardclock is another > >hardclock, an splclock, or an splhigh. And, maybe, splstatclock. I'm > >talking about -stable here, which is where I'm doing my experiments. > > Try swapping so you use the RTC for hardclock & statclock. > > Let the i8254 run with 65536 divisor and do only timecounter service. > > That would be a very interresting experiment. Agreed. But in the cases I'm worrying about right now, the timecounter is the TSC. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:34:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C14B937B429 for ; Tue, 5 Feb 2002 09:34:17 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15HVCM90500; Tue, 5 Feb 2002 18:31:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 09:23:17 PST." <200202051723.g15HNH603801@vashon.polstra.com> Date: Tue, 05 Feb 2002 18:31:12 +0100 Message-ID: <90498.1012930272@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: >Agreed. But in the cases I'm worrying about right now, the >timecounter is the TSC. Now, *that* is very interesting, how reproducible is it ? Can you try to MFC rev 1.111 and see if that changes anything ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:39:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d179.as0.nwbl0.wi.voyager.net [169.207.130.181]) by hub.freebsd.org (Postfix) with ESMTP id DC19537B427; Tue, 5 Feb 2002 09:39:17 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g15BgnL02033; Tue, 5 Feb 2002 11:42:49 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 5 Feb 2002 11:42:49 +0000 (GMT) From: Mike Silbersack To: Daniel Lang Cc: freebsd-stable@freebsd.org, Subject: Re: autotuning kernel vars In-Reply-To: <20020205160947.GE58643@atrbg11.informatik.tu-muenchen.de> Message-ID: <20020205113839.F1617-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Daniel Lang wrote: > Hi Mike, > > Mike Silbersack wrote on Tue, Feb 05, 2002 at 10:03:14AM +0000: > [..] > > Hmph, apologies. I was not aware of the comment in LINT that suggested > > setting nmbclusters / nbuf to 0. This comment predates the autoscaling > > code, and is wrong. I'll go remove it. > Ah, well, thanks. That clarifies it. > > So for I don't specify any values for NMBCLUSTERS and NBUF, > leaving maxusers at 512, and just watch how the machine > performs. > > I just thought about increasing NMBCLUSTERS because somewhere > (I don't remember) it was mentioned, that some new code > (larger default buffers somewhere in the ip stack?) could > make one run out of them. But I guess with maxusers=512 I'm > already on the safe side. > > Thanks, > Daniel To monitor mbuf and mbuf cluster usage (nmbclusters sets the number of mbuf clusters), simply run netstat -m. This will show you the current and peak usage of mbufs / clusters, as well the max value that was determined from maxusers. From that, you'll be able to tell if your usage is anywhere near the max, and will be able to determine whether or not to increase the value. With maxusers=512 you should have around 9000 mbuf clusters; this should be more than enough unless you're running a really busy web/ftp/mail server. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:49:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 2051B37B41B; Tue, 5 Feb 2002 09:49:39 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA26964; Wed, 6 Feb 2002 04:49:35 +1100 Date: Wed, 6 Feb 2002 04:52:02 +1100 (EST) From: Bruce Evans X-X-Sender: To: Nik Clayton Cc: Mike Silbersack , Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020205104537.S5732@clan.nothing-going-on.org> Message-ID: <20020206044925.J27421-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Nik Clayton wrote: > On Tue, Feb 05, 2002 at 05:01:29PM +1100, Bruce Evans wrote: > > My patch is not suitable for committing verbatim. It has 2 or 3 XXX's. > > Do you make these patches available anywhere, so that other people can > look over them and maybe help you on the XXX'd sections? Erm, I'm replying to mail that gave a URL for my old mail with the patch. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 9:54: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id E461C37B429 for ; Tue, 5 Feb 2002 09:53:29 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15HrQo53485; Tue, 5 Feb 2002 09:53:26 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15HrQh04002; Tue, 5 Feb 2002 09:53:26 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 09:53:26 -0800 (PST) Message-Id: <200202051753.g15HrQh04002@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <90498.1012930272@critter.freebsd.dk> References: <90498.1012930272@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <90498.1012930272@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: > > >Agreed. But in the cases I'm worrying about right now, the > >timecounter is the TSC. > > Now, *that* is very interesting, how reproducible is it ? I can reproduce it pretty easily. This is from a PIII/550: web1# uptime 5:23PM up 37 mins, 2 users, load averages: 0.08, 0.05, 0.01 web1# dmesg | grep microuptime microuptime() went backwards (1992.7347381 -> 1991.587620) microuptime() went backwards (1992.7347381 -> 1991.620385) microuptime() went backwards (1992.7347381 -> 1991.621582) microuptime() went backwards (2016.7063298 -> 2015.272466) microuptime() went backwards (2286.7346482 -> 2285.587587) microuptime() went backwards (2286.7346482 -> 2285.593646) microuptime() went backwards (2286.7346482 -> 2285.595103) microuptime() went backwards (2286.7346482 -> 2285.617023) Now, two things are unusual about this system. First, I have it pumping packets from inside the kernel (with a special netgraph node) at a rate which is keeping the system about 95% busy processing interrupts. (That's about 330K packets/second.) That definitely makes it happen more often. But I also see it occasionally when the system is sitting idle. Second, I have HZ set to 10000. I think that also contributes to the problem. It shouldn't, though. Not even a PII/400 breathes hard at HZ=10000. On another system which is mostly idle, I see it about 4 times a day. That system also has HZ set to 10000. It's a PIII/1.13 GHz: microuptime() went backwards (200671.582473 -> 200671.582472) microuptime() went backwards (222622.358518 -> 222622.358517) microuptime() went backwards (228934.897839 -> 228934.897838) microuptime() went backwards (246166.386301 -> 246166.386300) microuptime() went backwards (263484.488575 -> 263484.488574) Notice the difference on this system that's fairly idle. On the other system, it was the seconds going backward. Here it's the microseconds. These may be two entirely different problems. > Can you try to MFC rev 1.111 and see if that changes anything ? Sure. I'll let you know. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:26:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id E1DBD37B428 for ; Tue, 5 Feb 2002 10:26:16 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15IQEo53597; Tue, 5 Feb 2002 10:26:14 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15IQDt04095; Tue, 5 Feb 2002 10:26:13 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 10:26:13 -0800 (PST) Message-Id: <200202051826.g15IQDt04095@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <90498.1012930272@critter.freebsd.dk> References: <90498.1012930272@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <90498.1012930272@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: > > Can you try to MFC rev 1.111 and see if that changes anything ? That produced some interesting results. I am still testing under very heavy network interrupt load. With the change from 1.111, I still get the microuptime messages about as often. But look how much larger the reported backwards jumps are: microuptime() went backwards (896.225603 -> 888.463636) microuptime() went backwards (896.225603 -> 888.494440) microuptime() went backwards (896.225603 -> 888.500875) microuptime() went backwards (1184.392277 -> 1176.603001) microuptime() went backwards (1184.392277 -> 1176.603749) John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:31: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 1CD8337B416 for ; Tue, 5 Feb 2002 10:30:53 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15IUqo53631 for ; Tue, 5 Feb 2002 10:30:52 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15IUq004143; Tue, 5 Feb 2002 10:30:52 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 10:30:52 -0800 (PST) Message-Id: <200202051830.g15IUq004143@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Subject: Re: A question about timecounters In-Reply-To: <200202051826.g15IQDt04095@vashon.polstra.com> References: <90498.1012930272@critter.freebsd.dk> <200202051826.g15IQDt04095@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <200202051826.g15IQDt04095@vashon.polstra.com>, John Polstra wrote: > In article <90498.1012930272@critter.freebsd.dk>, > Poul-Henning Kamp wrote: > > In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: > > > > Can you try to MFC rev 1.111 and see if that changes anything ? > > That produced some interesting results. I am still testing under > very heavy network interrupt load. With the change from 1.111, I > still get the microuptime messages about as often. But look how > much larger the reported backwards jumps are: > > microuptime() went backwards (896.225603 -> 888.463636) > microuptime() went backwards (896.225603 -> 888.494440) > microuptime() went backwards (896.225603 -> 888.500875) > microuptime() went backwards (1184.392277 -> 1176.603001) > microuptime() went backwards (1184.392277 -> 1176.603749) Another interesting thing is that the jumps are always 7.7x seconds back -- usually 7.79 seconds. This is even true with more data points from two different machines. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:46:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C800037B41C for ; Tue, 5 Feb 2002 10:46:10 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15Ih4M91327; Tue, 5 Feb 2002 19:43:04 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 10:26:13 PST." <200202051826.g15IQDt04095@vashon.polstra.com> Date: Tue, 05 Feb 2002 19:43:04 +0100 Message-ID: <91325.1012934584@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051826.g15IQDt04095@vashon.polstra.com>, John Polstra writes: >In article <90498.1012930272@critter.freebsd.dk>, >Poul-Henning Kamp wrote: >> In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: >> >> Can you try to MFC rev 1.111 and see if that changes anything ? > >That produced some interesting results. I am still testing under >very heavy network interrupt load. With the change from 1.111, I >still get the microuptime messages about as often. But look how >much larger the reported backwards jumps are: > > microuptime() went backwards (896.225603 -> 888.463636) > microuptime() went backwards (896.225603 -> 888.494440) > microuptime() went backwards (896.225603 -> 888.500875) > microuptime() went backwards (1184.392277 -> 1176.603001) > microuptime() went backwards (1184.392277 -> 1176.603749) (Ok, I'll MFC 1.111) Sanity-check: this is NOT a multi-CPU system, right ? We now have three options left: hardclock interrupt starvation scheduling related anomaly wrt to the use of microuptime(). arithmetic overflow because the call to microuptime() gets interrupted for too long. Looking for the first, add this to hardclock: static u_int64_t lasttsc; u_int64_t delta, now; now = rdtsc(); delta = now - lasttsc; lasttsc = now; if (delta > (tsc_freq * 3) / (2 * hz)) { printf("delta = %llu \n", delta); } In theory, you get no printfs. If you do, hopefully they have small delta values. Looking for the third: Add splhigh() protection around the stuff in microuptime(); -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:47:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id AB7D837B423 for ; Tue, 5 Feb 2002 10:47:43 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15IicM91479; Tue, 5 Feb 2002 19:44:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 10:30:52 PST." <200202051830.g15IUq004143@vashon.polstra.com> Date: Tue, 05 Feb 2002 19:44:38 +0100 Message-ID: <91477.1012934678@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051830.g15IUq004143@vashon.polstra.com>, John Polstra writes: >In article <200202051826.g15IQDt04095@vashon.polstra.com>, >John Polstra wrote: >> In article <90498.1012930272@critter.freebsd.dk>, >> Poul-Henning Kamp wrote: >> > In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes: >> > >> > Can you try to MFC rev 1.111 and see if that changes anything ? >> >> That produced some interesting results. I am still testing under >> very heavy network interrupt load. With the change from 1.111, I >> still get the microuptime messages about as often. But look how >> much larger the reported backwards jumps are: >> >> microuptime() went backwards (896.225603 -> 888.463636) >> microuptime() went backwards (896.225603 -> 888.494440) >> microuptime() went backwards (896.225603 -> 888.500875) >> microuptime() went backwards (1184.392277 -> 1176.603001) >> microuptime() went backwards (1184.392277 -> 1176.603749) > >Another interesting thing is that the jumps are always 7.7x seconds >back -- usually 7.79 seconds. This is even true with more data points >from two different machines. Yes, I noticed, but didn't dare draw conclusions based on two data points. This points to an arithmetic overflow (ie: point 3 in my previous email) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:49: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mel-rto6.wanadoo.fr (smtp-out-6.wanadoo.fr [193.252.19.25]) by hub.freebsd.org (Postfix) with ESMTP id 9C33437B41F for ; Tue, 5 Feb 2002 10:48:53 -0800 (PST) Received: from mel-rta10.wanadoo.fr (193.252.19.193) by mel-rto6.wanadoo.fr; 5 Feb 2002 19:48:52 +0100 Received: from mail-web7 (193.252.19.214) by mel-rta10.wanadoo.fr; 5 Feb 2002 19:48:34 +0100 Received: from '' by www.wanadoo.fr with HTTP; Tue, 05 Feb 2002 19:48:34 +0100 (MET) Message-ID: <3c6029023c8c1abe@mel-rta10.wanadoo.fr> (added by mel-rta10.wanadoo.fr) Date: Tue, 05 Feb 2002 19:48:34 +0100 (MET) From: "Jonathan BENSAMOUN" To: Subject: switching context and execute MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here is my problem ... I have got a process which syscall myown function. This function forks the process in a child which has to execve. My method : - I hook in fork to insert the execve - before calling the execve I have to switch context. I use mi_switch and cpu_switch. But ! My parent process has to control the error returned by the child SO= ! I have to write in the child instructions stack : 1/ A call to execve 2/ The come back in the parent process context If anyone has an example for a such manipulation ... Thanks John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:51:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 2EC9137B425 for ; Tue, 5 Feb 2002 10:51:40 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15Ipbo53800; Tue, 5 Feb 2002 10:51:37 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15IpbU04184; Tue, 5 Feb 2002 10:51:37 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 10:51:37 -0800 (PST) Message-Id: <200202051851.g15IpbU04184@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <91477.1012934678@critter.freebsd.dk> References: <91477.1012934678@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <91477.1012934678@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051830.g15IUq004143@vashon.polstra.com>, John Polstra writes: > >In article <200202051826.g15IQDt04095@vashon.polstra.com>, > >John Polstra wrote: > > > >Another interesting thing is that the jumps are always 7.7x seconds > >back -- usually 7.79 seconds. This is even true with more data points > >from two different machines. > > Yes, I noticed, but didn't dare draw conclusions based on two data points. It's pretty consistent -- always 7.7somthing. > This points to an arithmetic overflow (ie: point 3 in my previous email) Yes, I think you're onto something now. It's a 550 MHz. machine, so the TSC increments every 1.82 nsec. And 1.82 nsec * 2^32 is 7.81 seconds. :-) I'll try the things you suggested in your other mail. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:52:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id A8B4637B41B for ; Tue, 5 Feb 2002 10:52:22 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA03723; Tue, 5 Feb 2002 11:51:58 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g15Ipw568733; Tue, 5 Feb 2002 11:51:58 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15456.10702.319710.952387@caddis.yogotech.com> Date: Tue, 5 Feb 2002 11:51:58 -0700 To: Poul-Henning Kamp Cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: <91325.1012934584@critter.freebsd.dk> References: <200202051826.g15IQDt04095@vashon.polstra.com> <91325.1012934584@critter.freebsd.dk> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >> Can you try to MFC rev 1.111 and see if that changes anything ? > > > >That produced some interesting results. I am still testing under > >very heavy network interrupt load. With the change from 1.111, I > >still get the microuptime messages about as often. But look how > >much larger the reported backwards jumps are: > > > > microuptime() went backwards (896.225603 -> 888.463636) > > microuptime() went backwards (896.225603 -> 888.494440) > > microuptime() went backwards (896.225603 -> 888.500875) > > microuptime() went backwards (1184.392277 -> 1176.603001) > > microuptime() went backwards (1184.392277 -> 1176.603749) > > (Ok, I'll MFC 1.111) Huh? It appears that 1.111 makes things worse, not better (larger jumps). Can you explain why you think this is a good things, since it seems to be a bad thing to me. > Sanity-check: this is NOT a multi-CPU system, right ? As stated before, both are > 1Ghz single-CPU systems running -stable, although I'm sure John is capable of a answering this on his own. :) > We now have three options left: > hardclock interrupt starvation This is Bruce's hypothesis, right? > scheduling related anomaly wrt to the use of microuptime(). > arithmetic overflow because the call to microuptime() gets > interrupted for too long. 'Interrupted for too long'. Do you mean 'not interrupted enough', aka a long interrupt blockage? (I'm trying to understand here.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:53: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id DDD9237B431 for ; Tue, 5 Feb 2002 10:52:38 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15Iqao53818; Tue, 5 Feb 2002 10:52:36 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15IqZI04193; Tue, 5 Feb 2002 10:52:35 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 10:52:35 -0800 (PST) Message-Id: <200202051852.g15IqZI04193@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <91325.1012934584@critter.freebsd.dk> References: <91325.1012934584@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <91325.1012934584@critter.freebsd.dk>, Poul-Henning Kamp wrote: > > Sanity-check: this is NOT a multi-CPU system, right ? Right. These are all single-CPU systems with non-SMP -stable kernels. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 10:58: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7553337B405 for ; Tue, 5 Feb 2002 10:58:02 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15IsuM91635; Tue, 5 Feb 2002 19:54:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 09:21:31 PST." <200202051721.g15HLVW03792@vashon.polstra.com> Date: Tue, 05 Feb 2002 19:54:56 +0100 Message-ID: <91633.1012935296@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051721.g15HLVW03792@vashon.polstra.com>, John Polstra writes: >In article <86051.1012909502@critter.freebsd.dk>, >> This may be a problem, I have yet to see GCC make different code for >> that but I should probably have committed the "volatile" anyway. > >It should be committed, but it is not causing the problem in this >case. I changed it and then compared MD5s of the object files. The >only changes that resulted were unimportant. Will do. >> >I also noticed this in tco_forward(): >> > >> > tco = timecounter; >> > tc = sync_other_counter(); >> > [...] >> > if (tco->tc_poll_pps) >> >> This code is actually correct, the tc_poll_pps needs to be done on >> the "old" timecounter, because that would be the reference for any >> captured hardware timestamps, if I did it on the new timecounter I >> might get negative deltas which would complicate things. Also the >> new timecounter may have a changed frequency/offset (tickadj/ntpd >> and all that). > >I don't think I follow your reasoning here. If the call to >sync_other_counter were inlined, we'd have something like this: > > tco = timecounter; > tco_in_sync_other_counter = timecounter; > [...] > if (tco->tc_poll_pps) > >Obviously tco and tco_in_sync_other_counter will have the same value >almost all of the time, so the code can't be relying on them being >different. It doesn't rely on them being different, they are used for two different purposes. sync_other_counter() sets up the next counter in the ring to be used for timekeeping, tco/tc_poll_pps is used to calculate any hardware captured timestamps which occured _before_ now. sync_other_counter() returns the next timecounter after fiddling it but we cannot use that for tc_poll_pps() purposes, we need the old (or if you will: still present one) for that. Trust me, this is not your problem because this is used only with the xrpu.c timecounter code anyway and you don't have the hardware for that :-) >Many of the systems where I see this problem are using the TSC as >the timecounter. They don't have APM in the kernel, and they aren't >running ntpd. I.e., it's not only the i8254 that's the problem. The >fastest of these systems is a 1.13 GHz PIII, and it would take the 32 >bits of the TSC which are actually used 3.8 seconds to wrap around. It would be a problem if the kernel is punched hard enough that code doesn't complete in the time it takes for the used timecounter to wrap, ie: if you can have something like: call microuptime() tc = timecounter; (interrupt and do other stuff for several seconds) ... overflow in arithmetic But you would have to pummel your kernel pretty bad for that. On the other hand, between a 10000 Hz and the network load you describe, that may be exactly what is happening... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11: 0:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 207AB37B423 for ; Tue, 5 Feb 2002 11:00:42 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15IvTM91786; Tue, 5 Feb 2002 19:57:31 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@yogotech.com (Nate Williams) Cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 11:51:58 MST." <15456.10702.319710.952387@caddis.yogotech.com> Date: Tue, 05 Feb 2002 19:57:29 +0100 Message-ID: <91784.1012935449@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <15456.10702.319710.952387@caddis.yogotech.com>, Nate Williams writes: >> >> Can you try to MFC rev 1.111 and see if that changes anything ? >> > >> >That produced some interesting results. I am still testing under >> >very heavy network interrupt load. With the change from 1.111, I >> >still get the microuptime messages about as often. But look how >> >much larger the reported backwards jumps are: >> > >> > microuptime() went backwards (896.225603 -> 888.463636) >> > microuptime() went backwards (896.225603 -> 888.494440) >> > microuptime() went backwards (896.225603 -> 888.500875) >> > microuptime() went backwards (1184.392277 -> 1176.603001) >> > microuptime() went backwards (1184.392277 -> 1176.603749) >> >> (Ok, I'll MFC 1.111) > >Huh? It appears that 1.111 makes things worse, not better (larger >jumps). No, 1.111 makes the jumps report more correctly I think. They will maybe save your meal in less bad cases than yours, but in yours they just make sure that we don't get invalid number of microseconds in a timeval, and consequently we get more honest output. >> We now have three options left: >> hardclock interrupt starvation > >This is Bruce's hypothesis, right? Also mine for that matter. >> scheduling related anomaly wrt to the use of microuptime(). >> arithmetic overflow because the call to microuptime() gets >> interrupted for too long. > >'Interrupted for too long'. Do you mean 'not interrupted enough', aka >a long interrupt blockage? (I'm trying to understand here.) See my previous email, I just explained it there. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11: 1:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 06DA137B42A for ; Tue, 5 Feb 2002 11:01:45 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15IwZM91803; Tue, 5 Feb 2002 19:58:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 10:51:37 PST." <200202051851.g15IpbU04184@vashon.polstra.com> Date: Tue, 05 Feb 2002 19:58:35 +0100 Message-ID: <91801.1012935515@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051851.g15IpbU04184@vashon.polstra.com>, John Polstra writes: >In article <91477.1012934678@critter.freebsd.dk>, >Poul-Henning Kamp wrote: >> In message <200202051830.g15IUq004143@vashon.polstra.com>, John Polstra writes: >> >In article <200202051826.g15IQDt04095@vashon.polstra.com>, >> >John Polstra wrote: >> > >> >Another interesting thing is that the jumps are always 7.7x seconds >> >back -- usually 7.79 seconds. This is even true with more data points >> >from two different machines. >> >> Yes, I noticed, but didn't dare draw conclusions based on two data points. > >It's pretty consistent -- always 7.7somthing. > >> This points to an arithmetic overflow (ie: point 3 in my previous email) > >Yes, I think you're onto something now. It's a 550 MHz. machine, so >the TSC increments every 1.82 nsec. And 1.82 nsec * 2^32 is 7.81 >seconds. :-) In that case I'm almost willing to put an AnchorSteam on microuptime() being interrupted for more than good is in which case the splhigh() should cure it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11: 4:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 1BF1637B404 for ; Tue, 5 Feb 2002 11:04:49 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA04300; Tue, 5 Feb 2002 12:04:46 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g15J4jk68853; Tue, 5 Feb 2002 12:04:45 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15456.11469.659090.290513@caddis.yogotech.com> Date: Tue, 5 Feb 2002 12:04:45 -0700 To: Poul-Henning Kamp Cc: nate@yogotech.com (Nate Williams), John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: <91784.1012935449@critter.freebsd.dk> References: <15456.10702.319710.952387@caddis.yogotech.com> <91784.1012935449@critter.freebsd.dk> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >> >> Can you try to MFC rev 1.111 and see if that changes anything ? > >> > > >> >That produced some interesting results. I am still testing under > >> >very heavy network interrupt load. With the change from 1.111, I > >> >still get the microuptime messages about as often. But look how > >> >much larger the reported backwards jumps are: > >> > > >> > microuptime() went backwards (896.225603 -> 888.463636) > >> > microuptime() went backwards (896.225603 -> 888.494440) > >> > microuptime() went backwards (896.225603 -> 888.500875) > >> > microuptime() went backwards (1184.392277 -> 1176.603001) > >> > microuptime() went backwards (1184.392277 -> 1176.603749) > >> > >> (Ok, I'll MFC 1.111) > > > >Huh? It appears that 1.111 makes things worse, not better (larger > >jumps). > > No, 1.111 makes the jumps report more correctly I think. Now, if that ain't a glowing reason to MFC it, I don't know one (I think). :) :) > They will maybe save your meal in less bad cases than yours, but in > yours they just make sure that we don't get invalid number of > microseconds in a timeval, and consequently we get more honest output. How can you verify that this is the case? > >> We now have three options left: > >> hardclock interrupt starvation > > > >This is Bruce's hypothesis, right? > > Also mine for that matter. > > >> scheduling related anomaly wrt to the use of microuptime(). > >> arithmetic overflow because the call to microuptime() gets > >> interrupted for too long. > > > >'Interrupted for too long'. Do you mean 'not interrupted enough', aka > >a long interrupt blockage? (I'm trying to understand here.) > > See my previous email, I just explained it there. I still didn't understand, hence the reason for the question. (The explanation was in the email I originall responded to). I understand the 'overflow' issue, but it would seem to my naive thinking that it would occur only when interrupts are blocked for a period of time, which is the same as hardclock interrupt starvation in my mind. How are issues (1) and (3) above different? Nate ps. I'm just trying to understand, and am *NOT* trying to start a flame-war. :) :) :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11: 6:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 2BD2B37B420 for ; Tue, 5 Feb 2002 11:06:11 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15J68o53968; Tue, 5 Feb 2002 11:06:08 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15J68E04216; Tue, 5 Feb 2002 11:06:08 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 11:06:08 -0800 (PST) Message-Id: <200202051906.g15J68E04216@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <91801.1012935515@critter.freebsd.dk> References: <91801.1012935515@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <91801.1012935515@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051851.g15IpbU04184@vashon.polstra.com>, John Polstra writes: > >Yes, I think you're onto something now. It's a 550 MHz. machine, so > >the TSC increments every 1.82 nsec. And 1.82 nsec * 2^32 is 7.81 > >seconds. :-) > > In that case I'm almost willing to put an AnchorSteam on microuptime() > being interrupted for more than good is in which case the splhigh() should > cure it. I'm testing that now. But for how long would microuptime have to be interrupted to make this happen? Surely not 7.81 seconds! On this same machine I have a curses application running which is updating the screen once a second. It never misses a beat, and userland is very responsive. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:12:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B413537B436 for ; Tue, 5 Feb 2002 11:12:19 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15J9BM92035; Tue, 5 Feb 2002 20:09:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: nate@yogotech.com (Nate Williams) Cc: John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 12:04:45 MST." <15456.11469.659090.290513@caddis.yogotech.com> Date: Tue, 05 Feb 2002 20:09:11 +0100 Message-ID: <92033.1012936151@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <15456.11469.659090.290513@caddis.yogotech.com>, Nate Williams writes: >How are issues (1) and (3) above different? > >ps. I'm just trying to understand, and am *NOT* trying to start a >flame-war. :) :) :) If the starvation happens to hardclock() or rather tc_windup() the effect will be cummulative and show up in permanent jumps in the output of date for instance. In stable hardclock() is spl-protected so this would be _really_ bad news. If the starvation happens in any of {micro|nano}[up]time() (but not the "get&" variants!) the it will result in a single spurious reading. The premise for avoiding locking in the access functions to timecounters where precisely that we could trust them to not be pre-empted for long enough for the hardware to roll over, if this is not the case we loose because the overflow in the hardware counter means that the timecounter we calculate from is not valid for the delta we get from the hardware. I'm not sure this answers your question, if not it is not bad will, just me not understanding the question :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:14:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9A6C337B427 for ; Tue, 5 Feb 2002 11:14:06 -0800 (PST) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g15JE5E15090 for ; Tue, 5 Feb 2002 14:14:05 -0500 (EST) Date: Tue, 5 Feb 2002 14:12:52 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: Ptrace and SIGTRAP problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a mystery to me. I have gone through some kernel code without luck. The following small program demonstrates that a parent process can write into the data space of its child by ptrace(). If the parent waits for the child to exit, there is no problem. However, if the parent does not do so, the child will get a SIGTRAP signal and core dumps. Can anyone give me a clue how this is the case? Thanks! /* * Filename: trace.c - child process. Use cc -o trace trace.c to compile */ int data[8] = { 0, 0 }; main() { int i; printf("\n"); for (i = 0; i < 8; i++) printf("trace: addr = 0x%x: data[%d] = %d\n", &data[i], i, data[i]); printf("ptrace data addr 0x%x\n", &data[0]); exit(0); } Please run trace first to get the start address of data[8]. This address will be given to the parent process. /* * Filename: debug.c - parent process */ #include #include #include #include #include main(int argc, char * argv[]) { caddr_t addr; int i, pid, ret, data, status; if (argc != 2) { printf("Usage: debug address\n"); exit(0); } sscanf(argv[1], "%x", &addr); if ((pid = fork()) == 0) { ptrace(PT_TRACE_ME, 0, 0, 0); execl("./trace", "trace", 0); /* l - list */ printf("Fail to execl() child process!\n"); exit(1); } printf("Child %d array address is 0x%x\n", pid, addr); ret = waitpid(pid, &status, 0); printf("ret = %d, status = %d\n", ret, status); for (i = 0; i < 8; i++) { /* * Write value of i into address addr in proc pid. */ if (ptrace(PT_WRITE_D, pid, addr, i) == -1) { printf("ptrace error = %d\n", errno); exit(0); } addr += sizeof(int); } if (ptrace(PT_CONTINUE, pid, (caddr_t)1, 0) == -1) { printf("ptrace error = %d\n", errno); exit(0); } #if 1 /* * Without this waitpid(), the child (trace) will core dump. */ ret = waitpid(pid, &status, 0); printf("ret = %d, status = %d\n", ret, status); #endif } /* end of main() */ -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:19: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D962537B42C for ; Tue, 5 Feb 2002 11:18:57 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15JFpM92150; Tue, 5 Feb 2002 20:15:51 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 11:06:08 PST." <200202051906.g15J68E04216@vashon.polstra.com> Date: Tue, 05 Feb 2002 20:15:51 +0100 Message-ID: <92148.1012936551@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051906.g15J68E04216@vashon.polstra.com>, John Polstra writes: >In article <91801.1012935515@critter.freebsd.dk>, >Poul-Henning Kamp wrote: >> In message <200202051851.g15IpbU04184@vashon.polstra.com>, John Polstra writes: >> >Yes, I think you're onto something now. It's a 550 MHz. machine, so >> >the TSC increments every 1.82 nsec. And 1.82 nsec * 2^32 is 7.81 >> >seconds. :-) >> >> In that case I'm almost willing to put an AnchorSteam on microuptime() >> being interrupted for more than good is in which case the splhigh() should >> cure it. > >I'm testing that now. But for how long would microuptime have to >be interrupted to make this happen? Surely not 7.81 seconds! On >this same machine I have a curses application running which is >updating the screen once a second. It never misses a beat, and >userland is very responsive. Well, that is what I don't understand yet either :-) The fact that the delta is not exactly 2^32 * cpu clock is probably blindingly obviously indicative of "why", but I havn't solved the puzzle yet... Since you are running with a 10000 HZ, NTIMECOUNTER should probably be considerably increased. (Actually it might be a good idea to simply set NTIMECOUNTER == hz ... hmmm...) We could be seing a situation where a process is preempted in microuptime() and the timecounter ring being recycled *and* the hardware counter overflowing before it completes, that might give this problem. You didn't say if you ran with standard NTIMECOUNTER right now, but 5 would be awfully short time at HZ=10000: 500 usec... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:19:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3A8A837B417 for ; Tue, 5 Feb 2002 11:19:33 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id MAA04838; Tue, 5 Feb 2002 12:19:02 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g15JJ1W68973; Tue, 5 Feb 2002 12:19:01 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15456.12323.943290.212726@caddis.yogotech.com> Date: Tue, 5 Feb 2002 12:18:59 -0700 To: Poul-Henning Kamp Cc: nate@yogotech.com (Nate Williams), John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters In-Reply-To: <92033.1012936151@critter.freebsd.dk> References: <15456.11469.659090.290513@caddis.yogotech.com> <92033.1012936151@critter.freebsd.dk> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > >How are issues (1) and (3) above different? > > > >ps. I'm just trying to understand, and am *NOT* trying to start a > >flame-war. :) :) :) > > If the starvation happens to hardclock() or rather tc_windup() the effect > will be cummulative and show up in permanent jumps in the output of date > for instance. In stable hardclock() is spl-protected so this would be > _really_ bad news. > > If the starvation happens in any of {micro|nano}[up]time() (but not the > "get&" variants!) the it will result in a single spurious reading. Ok, the bulb is starting to grow from dim to bright. :) > The premise for avoiding locking in the access functions to timecounters > where precisely that we could trust them to not be pre-empted for long > enough for the hardware to roll over, if this is not the case we loose > because the overflow in the hardware counter means that the timecounter > we calculate from is not valid for the delta we get from the hardware. > > I'm not sure this answers your question, if not it is not bad will, just > me not understanding the question :-) *grin* I think I understand the problem. Let me try to rephrase to make sure. 1) If we have an interrupt lockout (*NOT* due to time-counting code), then we'd have a problem since the hardclock would never get run. 2) If however, the locking done to protect the timecounter code happens to make getting/setting the timecounter take too long, we'd get similar results, but for *completely* different reasons. Let me be more precise. (1) cli(); /* Take a really long time doing something */ sti(); (2) /* Do something */ gettime(); /* Takes a really long time to complete */ The first is harder to track down/fix, simply because you don't know *who* the offender is. The latter is essentially the same problem to fix, but *may* be easier to fix since the offending code *IS* the timecounter code. Am I even close to understanding? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:40:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d179.as0.nwbl0.wi.voyager.net [169.207.130.181]) by hub.freebsd.org (Postfix) with ESMTP id 6EB8B37B404 for ; Tue, 5 Feb 2002 11:40:03 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g15DhMn02520; Tue, 5 Feb 2002 13:43:24 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 5 Feb 2002 13:43:22 +0000 (GMT) From: Mike Silbersack To: Bruce Evans Cc: Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020205163210.G25358-100000@gamplex.bde.org> Message-ID: <20020205134035.M1617-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Bruce Evans wrote: > On Mon, 4 Feb 2002, Mike Silbersack wrote: > > > On Tue, 5 Feb 2002, Bruce Evans wrote: > > > I haven't done anything to clean up the patch. I hope the problem > > > will go away in future versions of gcc (align the stack at runtime in > > > the few routines that actually need it). > > > > Well, if Linux aligns the initial stack, the chance that gcc will have > > auto-alignment added sounds to be about zero. You might as well go ahead > > with your patch when you get a chance. > > There is a nonzero probability that the pessimization of aligning in almost > every routine will be fixed someday. Actually, the pessimization is worse > -- the alignment is done before every call. Even so, I'd wager that you can align the initial stack a few months ahead of when gcc's alignment is improved. > foo: > pushl %ebp > movl %esp,%ebp > subl $8,%esp # <- extra instruction for alignment (for foo) > addl $-12,%esp # <- extra instruction for alignment (for f1) What disgusting code. I find it amazing that they didn't even stick in some peephole optimizer to at least limit it to one operation. > My patch is not suitable for committing verbatim. It has 2 or 3 XXX's. > > Bruce True, but I'm sure you're capable of fixing it up if you so desire. :) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:43: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from amdext.amd.com (amdext.amd.com [139.95.251.1]) by hub.freebsd.org (Postfix) with ESMTP id 990F937B419; Tue, 5 Feb 2002 11:42:56 -0800 (PST) Received: from ssvlgs01.amd.com (ssvlgs01.amd.com [139.95.250.16]) by amdext.amd.com (8.9.3/8.9.3/AMD) with SMTP id LAA24464; Tue, 5 Feb 2002 11:42:55 -0800 (PST) From: marc.miller@amd.com Received: from 139.95.250.1 by ssvlgs01.amd.com with ESMTP (Tumbleweed MMS SMTP Relay (MMS v4.7)); Tue, 05 Feb 2002 11:42:54 -0800 X-Server-Uuid: 02753650-11b0-11d5-bbc5-00508bf987eb Received: from caexmta3.amd.com (caexmta3.amd.com [139.95.53.7]) by amdint.amd.com (8.9.3/8.9.3/AMD) with ESMTP id LAA07315; Tue, 5 Feb 2002 11:42:54 -0800 (PST) Received: by caexmta3.amd.com with Internet Mail Service (5.5.2653.19) id ; Tue, 5 Feb 2002 11:42:53 -0800 Message-ID: <858788618A93D111B45900805F85267A047D6508@caexmta3.amd.com> To: hackers@freebsd.org, freebsd-audit@freebsd.org Cc: netbsd-users@netbsd.org, port-i386@netbsd.org Subject: Athlon XP SSE flag not set? (AMD's response) Date: Tue, 5 Feb 2002 11:42:51 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 107EEA342557478-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry for the cross-post, but this may be relevant to multiple operating systems. Some users have noticed that on certain motherboards the SSE flag is not being detected when using an Athlon XP, even though all Athlon XP processors we have produced to date support SSE. AMD responds with the following: - Our website has supported motherboards. - These motherboards have BIOSes that enable SSE on AthlonXP. - The end user should upgrade their BIOS if they have these motherboards. - If BIOS upgrade doesn't work for a listed MB, contact AMD (ask.amd.com) and the MB vendor. - If the MB is not on our list of recommended MB and does not properly enable SSE on Athlon XP, call the MB vendor to find out why not. Marc J. Miller Open Source Relations Engineer marc.miller@amd.com 1-800-538-8450 x43325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:44:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 3A1EF37B41C for ; Tue, 5 Feb 2002 11:44:19 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15JiFo54196; Tue, 5 Feb 2002 11:44:15 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15JiFw04286; Tue, 5 Feb 2002 11:44:15 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 11:44:15 -0800 (PST) Message-Id: <200202051944.g15JiFw04286@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <92148.1012936551@critter.freebsd.dk> References: <92148.1012936551@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, adding the splhigh() around the body of microuptime seems to have solved the problem. After 45 minutes of running the same test as before, I haven't gotten a single message. If I get one later, I'll let you know. > >I'm testing that now. But for how long would microuptime have to > >be interrupted to make this happen? Surely not 7.81 seconds! On > >this same machine I have a curses application running which is > >updating the screen once a second. It never misses a beat, and > >userland is very responsive. > > Well, that is what I don't understand yet either :-) > > The fact that the delta is not exactly 2^32 * cpu clock is probably > blindingly obviously indicative of "why", but I havn't solved the > puzzle yet... I've been staring at the code, but I haven't gotten it yet either. > Since you are running with a 10000 HZ, NTIMECOUNTER should probably > be considerably increased. (Actually it might be a good idea to > simply set NTIMECOUNTER == hz ... hmmm...) I don't follow that. As I read the code, the "current" timecounter is only advanced every second -- not every 1/HZ seconds. Why should more of them be needed when HZ is large? > You didn't say if you ran with standard NTIMECOUNTER right now, > but 5 would be awfully short time at HZ=10000: 500 usec... Well, microseconds aren't what they used to be ... :-) But isn't it true that the current timecounter only advances every second? I think I have 5 seconds, not 5/HZ seconds. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:55:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7B80337B41F for ; Tue, 5 Feb 2002 11:55:19 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15JqBM92663; Tue, 5 Feb 2002 20:52:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 11:44:15 PST." <200202051944.g15JiFw04286@vashon.polstra.com> Date: Tue, 05 Feb 2002 20:52:11 +0100 Message-ID: <92661.1012938731@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202051944.g15JiFw04286@vashon.polstra.com>, John Polstra writes: >OK, adding the splhigh() around the body of microuptime seems to have >solved the problem. After 45 minutes of running the same test as >before, I haven't gotten a single message. If I get one later, I'll >let you know. Ok, so we know where the bogotism happens, now to identify it... >I don't follow that. As I read the code, the "current" timecounter >is only advanced every second -- not every 1/HZ seconds. Why should >more of them be needed when HZ is large? No, only if you have set tco_method to one, if tco_method is zero (default) we update the timecounter every HZ. >> You didn't say if you ran with standard NTIMECOUNTER right now, >> but 5 would be awfully short time at HZ=10000: 500 usec... > >Well, microseconds aren't what they used to be ... :-) But isn't it >true that the current timecounter only advances every second? I think >I have 5 seconds, not 5/HZ seconds. Depends on your tco_method... Could you try this combination: NTIMECOUNTER = HZ (or even 5 * HZ) tco_method = 0 no splhigh protection for microuptime() ? The reason why tco_method=1 isn't nice is that we loose the ability to use 1/hz precision cached timestamps in the get*() funtions. Btw, regarding the volatile thing: If I do extern volatile struct timecounter *timecounter; microtime() { struct timecounter *tc; tc = timecounter; The compiler complains about loosing the volatile thing. How do I tell it that it is the contents of the "timecounter" pointer which is volatile, but now what it points at ? I don't want the "tc" pointer to be volatile because it obviously isn't. Do I really need to cast it ? tc = (struct timecounter *)timecounter; That looks silly to me... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 11:58:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id EECD137B41F for ; Tue, 5 Feb 2002 11:58:51 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15Jwno54252; Tue, 5 Feb 2002 11:58:49 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15JwmV04331; Tue, 5 Feb 2002 11:58:48 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 11:58:48 -0800 (PST) Message-Id: <200202051958.g15JwmV04331@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <92661.1012938731@critter.freebsd.dk> References: <92661.1012938731@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <92661.1012938731@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051944.g15JiFw04286@vashon.polstra.com>, John Polstra writes: > >I don't follow that. As I read the code, the "current" timecounter > >is only advanced every second -- not every 1/HZ seconds. Why should > >more of them be needed when HZ is large? > > No, only if you have set tco_method to one, if tco_method is zero (default) > we update the timecounter every HZ. Oh, you're right. Sorry, I misread the code. My tco_method is 0, so it will do the update every HZ. > Could you try this combination: > > NTIMECOUNTER = HZ (or even 5 * HZ) > tco_method = 0 > no splhigh protection for microuptime() ? Yep, I'll try that. > If I do > extern volatile struct timecounter *timecounter; > > microtime() > { > struct timecounter *tc; > > tc = timecounter; > > The compiler complains about loosing the volatile thing. > > How do I tell it that it is the contents of the "timecounter" pointer which > is volatile, but now what it points at ? You want: extern struct timecounter *volatile timecounter; and also change the definition of the variable in the .c file. You won't get any warnings from that. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12: 9:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id F193937B426 for ; Tue, 5 Feb 2002 12:09:12 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id HAA01486; Wed, 6 Feb 2002 07:09:04 +1100 Date: Wed, 6 Feb 2002 07:11:31 +1100 (EST) From: Bruce Evans X-X-Sender: To: Mike Silbersack Cc: Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020205134035.M1617-100000@patrocles.silby.com> Message-ID: <20020206071049.S502-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Mike Silbersack wrote: > On Tue, 5 Feb 2002, Bruce Evans wrote: > > foo: > > pushl %ebp > > movl %esp,%ebp > > subl $8,%esp # <- extra instruction for alignment (for foo) > > addl $-12,%esp # <- extra instruction for alignment (for f1) > > What disgusting code. I find it amazing that they didn't even stick in > some peephole optimizer to at least limit it to one operation. It's clearly the result of work in progress :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:19:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 86EB337B42C for ; Tue, 5 Feb 2002 12:19:23 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 60CF410DDF8; Tue, 5 Feb 2002 12:19:23 -0800 (PST) Date: Tue, 5 Feb 2002 12:19:23 -0800 From: Alfred Perlstein To: Bruce Evans Cc: Mike Silbersack , Michal Mertl , hackers@freebsd.org, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues Message-ID: <20020205121923.O59017@elvis.mu.org> References: <20020205134035.M1617-100000@patrocles.silby.com> <20020206071049.S502-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020206071049.S502-100000@gamplex.bde.org>; from bde@zeta.org.au on Wed, Feb 06, 2002 at 07:11:31AM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bruce Evans [020205 12:09] wrote: > On Tue, 5 Feb 2002, Mike Silbersack wrote: > > > On Tue, 5 Feb 2002, Bruce Evans wrote: > > > foo: > > > pushl %ebp > > > movl %esp,%ebp > > > subl $8,%esp # <- extra instruction for alignment (for foo) > > > addl $-12,%esp # <- extra instruction for alignment (for f1) > > > > What disgusting code. I find it amazing that they didn't even stick in > > some peephole optimizer to at least limit it to one operation. > > It's clearly the result of work in progress :-). I see really cruddy stuff like this every time i do a gcc -S, don't they watch for and try to fix this sort of thing? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:28:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 321F937B416 for ; Tue, 5 Feb 2002 12:28:53 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15KSoo54400; Tue, 5 Feb 2002 12:28:50 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15KSna04510; Tue, 5 Feb 2002 12:28:49 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 12:28:49 -0800 (PST) Message-Id: <200202052028.g15KSna04510@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <92661.1012938731@critter.freebsd.dk> References: <92661.1012938731@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <92661.1012938731@critter.freebsd.dk>, Poul-Henning Kamp wrote: > In message <200202051944.g15JiFw04286@vashon.polstra.com>, John Polstra writes: > Could you try this combination: > > NTIMECOUNTER = HZ (or even 5 * HZ) > tco_method = 0 > no splhigh protection for microuptime() ? After 25 minutes testing that with NTIMECOUNTER=50000, I haven't gotten any microuptime messages. So it appears that my problem was just that the current timecounter wrapped all the way around the ring while microuptime was interrupted, due to the high HZ value and the heavy interrupt load. I'm sorry I didn't try this sooner, when you suggested it. After lunch I'll try NTIMECOUNTER=HZ (10000 in my case). That sounds like a nice default value to me. It would be interesting to see whether this same fix also works in -current. I'm not sure yet if I can test that here or not. I haven't tried building my netgraph module under -current yet. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:29:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 74F0137B41F for ; Tue, 5 Feb 2002 12:29:39 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g15KSvj29739; Tue, 5 Feb 2002 12:28:57 -0800 (PST) (envelope-from dillon) Date: Tue, 5 Feb 2002 12:28:57 -0800 (PST) From: Matthew Dillon Message-Id: <200202052028.g15KSvj29739@apollo.backplane.com> To: Alfred Perlstein Cc: Bruce Evans , Mike Silbersack , Michal Mertl , hackers@FreeBSD.ORG, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues References: <20020205134035.M1617-100000@patrocles.silby.com> <20020206071049.S502-100000@gamplex.bde.org> <20020205121923.O59017@elvis.mu.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> > :> > What disgusting code. I find it amazing that they didn't even stick in :> > some peephole optimizer to at least limit it to one operation. :> :> It's clearly the result of work in progress :-). : :I see really cruddy stuff like this every time i do a gcc -S, don't :they watch for and try to fix this sort of thing? : :-- :-Alfred Perlstein [alfred@freebsd.org] I've been forced to add -mpreferred-stack-boundary=2 to critical code in certain projects to get rid of the crap GCC adds to the assembly. I don't mind if GCC aligns the stack for routines that actually need it, but what it does now - assume that the stack is already aligned and then realign in every single fragging procedure call is utterly and completely stupid. Someone should shoot the idiot that put that into the tree. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:35:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from chylonia.3miasto.net (chylonia.3miasto.net [217.96.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 101D337B423; Tue, 5 Feb 2002 12:35:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chylonia.3miasto.net (8.11.3nb1/8.11.3) with ESMTP id g15KcSM01956; Tue, 5 Feb 2002 21:38:28 +0100 (CET) Date: Tue, 5 Feb 2002 21:38:28 +0100 (CET) From: Wojciech Puchar To: Cc: , , , Subject: Re: Athlon XP SSE flag not set? (AMD's response) In-Reply-To: <858788618A93D111B45900805F85267A047D6508@caexmta3.amd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > - Our website has supported motherboards. > > - These motherboards have BIOSes that enable SSE on AthlonXP. it's strange that BIOS have to do it. > - The end user should upgrade their BIOS if they have these motherboards. ask AMD how to enable it - it's probably few lines of assembly that could be added to NetBSD initialization code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:37:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 6E91537B426 for ; Tue, 5 Feb 2002 12:37:18 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA11368 for ; Wed, 6 Feb 2002 07:37:17 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KDY2DP67I8VFNF5V@cim.alcatel.com.au> for freebsd-hackers@freebsd.org; Wed, 6 Feb 2002 07:37:07 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g15KbE992197 for freebsd-hackers@freebsd.org; Wed, 06 Feb 2002 07:37:14 +1100 Content-return: prohibited Date: Wed, 06 Feb 2002 07:37:13 +1100 From: Peter Jeremy Subject: Patching a kernel To: freebsd-hackers@freebsd.org Message-id: <20020206073713.Z7444@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd like to patch a running kernel to disable an annoying non-rate-limited message but gdb won't let me. (For various reasons, I don't want to have to build a new kernel and reboot). aalp03# chflags noschg /kernel aalp03# gdb -k /kernel /dev/mem GNU gdb 4.18 ... IdlePTD 3457024 initial pcb at 4d40000 panic messages: --- --- #0 0xc0159bf0 in mi_switch () (kgdb) set write on (kgdb) print {int}0xc01fffa4 = 0x00004eb8 kvm_write:write failed (kgdb) show write Writing into executable and core files is on. (kgdb) 0xc01fffa4 is in the kernel text area. This is 4.4-STABLE from mid-December running at securelevel -1. Is there any way around this? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:37:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 37B1237B405 for ; Tue, 5 Feb 2002 12:37:33 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 04CBE10DDF8; Tue, 5 Feb 2002 12:37:33 -0800 (PST) Date: Tue, 5 Feb 2002 12:37:32 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Bruce Evans , Mike Silbersack , Michal Mertl , hackers@FreeBSD.ORG, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues Message-ID: <20020205123732.Q59017@elvis.mu.org> References: <20020205134035.M1617-100000@patrocles.silby.com> <20020206071049.S502-100000@gamplex.bde.org> <20020205121923.O59017@elvis.mu.org> <200202052028.g15KSvj29739@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202052028.g15KSvj29739@apollo.backplane.com>; from dillon@apollo.backplane.com on Tue, Feb 05, 2002 at 12:28:57PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matthew Dillon [020205 12:28] wrote: > > I've been forced to add -mpreferred-stack-boundary=2 to critical code > in certain projects to get rid of the crap GCC adds to the assembly. > > I don't mind if GCC aligns the stack for routines that actually need > it, but what it does now - assume that the stack is already aligned and > then realign in every single fragging procedure call is utterly and > completely stupid. Someone should shoot the idiot that put that into > the tree. Now Matt... tell us how you really feel. :) Better yet, flame the gcc developers and tell them to fix this ungodly breakage. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 12:40:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C38AE37B417 for ; Tue, 5 Feb 2002 12:40:36 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15KbUM93253; Tue, 5 Feb 2002 21:37:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-Reply-To: Your message of "Tue, 05 Feb 2002 12:28:49 PST." <200202052028.g15KSna04510@vashon.polstra.com> Date: Tue, 05 Feb 2002 21:37:30 +0100 Message-ID: <93251.1012941450@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200202052028.g15KSna04510@vashon.polstra.com>, John Polstra writes: >After 25 minutes testing that with NTIMECOUNTER=50000, I haven't >gotten any microuptime messages. So it appears that my problem was >just that the current timecounter wrapped all the way around the ring >while microuptime was interrupted, due to the high HZ value and the >heavy interrupt load. I'm sorry I didn't try this sooner, when you >suggested it. > >After lunch I'll try NTIMECOUNTER=HZ (10000 in my case). That sounds >like a nice default value to me. Yup, if we preempt things for more than a second we have other problems too I think. My fault for not letting it depend in HZ in the first place. >It would be interesting to see whether this same fix also works in >-current. I'm not sure yet if I can test that here or not. I haven't >tried building my netgraph module under -current yet. Well, either way I will commit the volatile and this NTIMECOUNTER to -current now, it's certainly better than what is there now. Thanks for the help, I owe you one at BSDcon! Poul-Henning Ohh, and btw: do I need to say that I'm dying to know what the heck you are doing with that box ? :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 13:13:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.web.am (wizard.web.am [217.113.0.66]) by hub.freebsd.org (Postfix) with SMTP id 38E0537B429 for ; Tue, 5 Feb 2002 13:13:43 -0800 (PST) Received: (qmail 86252 invoked from network); 5 Feb 2002 21:26:29 -0000 Received: from unknown (HELO nm.web.am) (217.113.3.27) by wizard.web.am with SMTP; 5 Feb 2002 21:26:29 -0000 Received: (from nm@localhost) by nm.web.am (8.11.6/8.11.4) id g15LDwm01697; Wed, 6 Feb 2002 01:13:58 +0400 (AMT) (envelope-from nm) Date: Wed, 6 Feb 2002 01:13:58 +0400 From: nm To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fork rate limit Message-ID: <20020205211358.GA407@mail.web.am> References: <20020202201551.GA89061@mail.web.am> <200202022052.g12KqOM17214@apollo.backplane.com> <20020202223546.GA430@mail.web.am> <200202030754.g137saC40573@blackbox.pacbell.net> <20020203160433.A10920@mail.slc.edu> <20020203223946.B13336@mail.slc.edu> <20020204175616.A1056@mail.slc.edu> <20020204181724.B1633@mail.slc.edu> <20020204233550.GE88948@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020204233550.GE88948@dan.emsphone.com> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG First of all, thanks to all for telling their opinions :) I prefer to enforce both some preventive software measures as well administrative ones. But i do not what that some kiddie/newbie/clueless one to take down box that is shared among many other students as well. After listening to your all opinions I'm sure that this is to be implemented. i'll go on. -skip- -> Killing off parent procs could really upset a regular user who is -> running ./configure, which could easily spawn a couple undred processes -> in 10 seconds. Maybe simply delay the fork() until the rate drops? -> -> -- -> Dan Nelson -> dnelson@allantgroup.com First of all I suggest not to kill parent, but childs. They must die with EAGAIN error, as manual page fork(2) describes. If we will delay forks we will exhaust all kernel memory promptly. Second - i specially told about 2 limits - how many processes to spawn and in what time range - i.e. you can allow '1000 process for 60 secs' and it'll allow ./conifgure to run. [IMPLEMENTATION QUESTIONS] Can i suggest that rlim_t is at least 32 bit long ? I want to pack process limit and period length in one double word. (for example 16 bits for process count limit and 16 - for time, is gives range from 1 fork in 18 hours:) to 2^16 forks in 1 second) Or i should create 2 different RLIMIT_ constants ? thanx in advance -- Gaspar Chilingarov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 13:26:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 1F9EE37B405 for ; Tue, 5 Feb 2002 13:26:30 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15LQQo54684; Tue, 5 Feb 2002 13:26:26 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15LQQv04742; Tue, 5 Feb 2002 13:26:26 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 13:26:26 -0800 (PST) Message-Id: <200202052126.g15LQQv04742@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters In-Reply-To: <93251.1012941450@critter.freebsd.dk> References: <93251.1012941450@critter.freebsd.dk> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <93251.1012941450@critter.freebsd.dk>, Poul-Henning Kamp wrote: > > Well, either way I will commit the volatile and this NTIMECOUNTER to > -current now, it's certainly better than what is there now. Great, thanks. > Thanks for the help, I owe you one at BSDcon! I'll look forward to it! > Ohh, and btw: do I need to say that I'm dying to know what the heck > you are doing with that box ? :-) Making the room a good bit warmer, that's for sure. :-) First I should mention for the benefit of those listening in that it isn't something I can release publicly, and it will probably never be open source. It's a simulated web client and web server, running inside the kernel. It's good for load-testing and performance-testing many kinds of network devices. With two 1-GHz PIII boxes (one acting as the client and the other acting as the server) it can generate around 50000 (actually I think it's more than that) full web sessions per second. Also, you can dial in any rate you want, and it will generate that rate very precisely. Lots of fun! John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 13:28:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from amdext.amd.com (amdext.amd.com [139.95.251.1]) by hub.freebsd.org (Postfix) with ESMTP id ED72137B419; Tue, 5 Feb 2002 13:28:38 -0800 (PST) Received: from ssvlgs01.amd.com (ssvlgs01.amd.com [139.95.250.16]) by amdext.amd.com (8.9.3/8.9.3/AMD) with SMTP id NAA21692; Tue, 5 Feb 2002 13:28:35 -0800 (PST) From: marc.miller@amd.com Received: from 139.95.250.1 by ssvlgs01.amd.com with ESMTP (Tumbleweed MMS SMTP Relay (MMS v4.7)); Tue, 05 Feb 2002 13:28:33 -0800 X-Server-Uuid: 02753650-11b0-11d5-bbc5-00508bf987eb Received: from caexmta3.amd.com (caexmta3.amd.com [139.95.53.7]) by amdint.amd.com (8.9.3/8.9.3/AMD) with ESMTP id NAA01973; Tue, 5 Feb 2002 13:28:33 -0800 (PST) Received: by caexmta3.amd.com with Internet Mail Service (5.5.2653.19) id ; Tue, 5 Feb 2002 13:28:32 -0800 Message-ID: <858788618A93D111B45900805F85267A047D6519@caexmta3.amd.com> To: wojtek@chylonia.3miasto.net Cc: hackers@freebsd.org, freebsd-audit@freebsd.org, netbsd-users@netbsd.org, port-i386@netbsd.org Subject: RE: Athlon XP SSE flag not set? (AMD's response) Date: Tue, 5 Feb 2002 13:28:31 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 107E910B2570715-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Public document 20734 (http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/20734.pdf) should help with that. Marc J. Miller Open Source Relations Engineer marc.miller@amd.com 1-800-538-8450 x43325 -----Original Message----- From: Wojciech Puchar [mailto:wojtek@chylonia.3miasto.net] Sent: Tuesday, February 05, 2002 12:38 PM To: Miller, Marc Cc: hackers@freebsd.org; freebsd-audit@freebsd.org; netbsd-users@netbsd.org; port-i386@netbsd.org Subject: Re: Athlon XP SSE flag not set? (AMD's response) > > - Our website has supported motherboards. > > - These motherboards have BIOSes that enable SSE on AthlonXP. it's strange that BIOS have to do it. > - The end user should upgrade their BIOS if they have these motherboards. ask AMD how to enable it - it's probably few lines of assembly that could be added to NetBSD initialization code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 13:39:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from brainlink.com (mail.brainlink.com [149.2.32.129]) by hub.freebsd.org (Postfix) with ESMTP id 714F637B421 for ; Tue, 5 Feb 2002 13:39:26 -0800 (PST) Received: from [24.29.123.155] (HELO gronim.com) by brainlink.com (CommuniGate Pro SMTP 3.3.2) with ESMTP id 11106934 for freebsd-hackers@freebsd.org; Tue, 05 Feb 2002 16:32:37 -0500 Received: (from spork@localhost) by gronim.com (8.11.6/8.11.0) id g15LVTp25104 for freebsd-hackers@freebsd.org; Tue, 5 Feb 2002 16:31:29 -0500 (EST) (envelope-from spork) Date: Tue, 5 Feb 2002 16:31:29 -0500 From: Spike Gronim To: freebsd-hackers@freebsd.org Subject: Using vnconfig to do encrypted filesystems Message-ID: <20020205163129.A25078@spike.gronim.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey. OpenBSD suports an option (-k) to vnconfig(8) that causes it to prompt for a key which is used to encrypt whatever passes through the device. Are there plans to port this functionality in to FreeBSD? Thanks. -- --Spike Gronim gronimw@stuy.edu "Oh yes? An obscene triangle which, has more courage than the word." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 13:42:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 92B0437B422 for ; Tue, 5 Feb 2002 13:42:46 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g15LdcM94526; Tue, 5 Feb 2002 22:39:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Spike Gronim Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Using vnconfig to do encrypted filesystems In-Reply-To: Your message of "Tue, 05 Feb 2002 16:31:29 EST." <20020205163129.A25078@spike.gronim.com> Date: Tue, 05 Feb 2002 22:39:38 +0100 Message-ID: <94524.1012945178@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020205163129.A25078@spike.gronim.com>, Spike Gronim writes: >Hey. > > OpenBSD suports an option (-k) to vnconfig(8) that causes it to prompt >for a key which is used to encrypt whatever passes through the device. Are >there plans to port this functionality in to FreeBSD? Thanks. Yes, but not using the vndriver. There is DARPA sponsored work going on to do this "right". For an old overview of the concept: http://freefall.freebsd.org/~phk/Geom -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 14:13:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.panix.com (mail2.panix.com [166.84.0.213]) by hub.freebsd.org (Postfix) with ESMTP id 3792337B42A for ; Tue, 5 Feb 2002 14:13:12 -0800 (PST) Received: from panix1.panix.com (panix1.panix.com [166.84.1.1]) by mail2.panix.com (Postfix) with ESMTP id 6E4118F56; Tue, 5 Feb 2002 17:13:11 -0500 (EST) Received: (from tls@localhost) by panix1.panix.com (8.11.3nb1/8.8.8/PanixN1.0) id g15MDBa07361; Tue, 5 Feb 2002 17:13:11 -0500 (EST) Date: Tue, 5 Feb 2002 17:13:11 -0500 From: Thor Lancelot Simon To: Wojciech Puchar , hackers@freebsd.org, netbsd-users@netbsd.org, port-i386@netbsd.org Subject: Re: Athlon XP SSE flag not set? (AMD's response) Message-ID: <20020205221311.GA6958@rek.tjls.com> Reply-To: tls@rek.tjls.com References: <858788618A93D111B45900805F85267A047D6508@caexmta3.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 05, 2002 at 09:38:28PM +0100, Wojciech Puchar wrote: > > > > - Our website has supported motherboards. > > > > - These motherboards have BIOSes that enable SSE on AthlonXP. > it's strange that BIOS have to do it. > > - The end user should upgrade their BIOS if they have these motherboards. > > ask AMD how to enable it - it's probably few lines of assembly that could > be added to NetBSD initialization code If freestyle stupidity were an Olympic event, Wojtek, you'd be a four-time gold medal champion. What part of "" were you unable to read? -- Thor Lancelot Simon tls@rek.tjls.com But as he knew no bad language, he had called him all the names of common objects that he could think of, and had screamed: "You lamp! You towel! You plate!" and so on. --Sigmund Freud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 14:43: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from renown.cnchost.com (renown.concentric.net [207.155.248.7]) by hub.freebsd.org (Postfix) with ESMTP id E249E37B422 for ; Tue, 5 Feb 2002 14:42:56 -0800 (PST) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by renown.cnchost.com id RAA05212; Tue, 5 Feb 2002 17:42:45 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <200202052242.RAA05212@renown.cnchost.com> To: Poul-Henning Kamp Cc: John Polstra , hackers@freebsd.org Subject: Re: A question about timecounters In-reply-to: Your message of "Tue, 05 Feb 2002 20:52:11 +0100." <92661.1012938731@critter.freebsd.dk> Date: Tue, 05 Feb 2002 14:42:38 -0800 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Btw, regarding the volatile thing: > > If I do > extern volatile struct timecounter *timecounter; > > microtime() > { > struct timecounter *tc; > > tc = timecounter; > > The compiler complains about loosing the volatile thing. > > How do I tell it that it is the contents of the "timecounter" pointer which > is volatile, but now what it points at ? I don't want the "tc" pointer to > be volatile because it obviously isn't. Do I really need to cast it ? > > tc = (struct timecounter *)timecounter; [I see that jdp has answered your question but] cdecl is your friend! $ cdecl Type `help' or `?' for help cdecl> explain volatile struct timecounter *timecounter declare timecounter as pointer to volatile struct timecounter cdecl> declare timecounter as volatile pointer to struct timecounter struct timecounter * volatile timecounter -- bakul PS: Chances are most people don't have cdecl any more. You can get it like this: mkdir cdecl;cd cdecl fetch ftp://gatekeeper.dec.com/pub/usenet/comp.sources.unix/volume14/cdecl2/part0{1,2}.Z gzcat part01.Z | gunshar gzcat part02.Z | gunshar patch <<'EOF' diff -ru ../cdecl-orig/cdecl.c ./cdecl.c --- ../cdecl-orig/cdecl.c Tue Feb 5 14:24:23 2002 +++ ./cdecl.c Tue Feb 5 12:12:30 2002 @@ -57,6 +57,9 @@ # include # include # include +#ifdef BSD +#include +#endif #else # ifndef NOVARARGS # include @@ -110,6 +113,9 @@ void docast(char*, char*, char*, char*); void dodexplain(char*, char*, char*, char*); void docexplain(char*, char*, char*, char*); +#ifdef __FreeBSD__ +#define setprogname _bad_bad_bad_FreeBSD +#endif void setprogname(char *); int dotmpfile(int, char**), dofileargs(int, char**); #else diff -ru ../cdecl-orig/makefile ./makefile --- ../cdecl-orig/makefile Tue Feb 5 14:24:19 2002 +++ ./makefile Tue Feb 5 12:10:10 2002 @@ -13,7 +13,7 @@ # add -Ddodebug To compile in debugging trace statements. # add -Ddoyydebug To compile in yacc trace statements. -CFLAGS= -g -Ddodebug -Ddoyydebug +CFLAGS= -g -Ddodebug -Ddoyydebug -DBSD CC= cc ALLFILES= makefile cdgram.y cdlex.l cdecl.c cdecl.1 testset testset++ BIN= /usr/lubin EOF make # as root: make install BIN=/usr/local/bin No idea if c++decl is valid any more! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 14:59:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 4A06337B421 for ; Tue, 5 Feb 2002 14:59:26 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g15MxMo55233; Tue, 5 Feb 2002 14:59:22 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g15MxMv04928; Tue, 5 Feb 2002 14:59:22 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 14:59:22 -0800 (PST) Message-Id: <200202052259.g15MxMv04928@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: bakul@bitblocks.com Subject: Re: A question about timecounters In-Reply-To: <200202052242.RAA05212@renown.cnchost.com> References: <200202052242.RAA05212@renown.cnchost.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <200202052242.RAA05212@renown.cnchost.com>, Bakul Shah wrote: > [I see that jdp has answered your question but] cdecl is your friend! > > $ cdecl > Type `help' or `?' for help > cdecl> explain volatile struct timecounter *timecounter > declare timecounter as pointer to volatile struct timecounter > cdecl> declare timecounter as volatile pointer to struct timecounter > struct timecounter * volatile timecounter Is C a great language, or what? ;-) The way I always remember it is that you read the declaration inside-out: starting with the variable name and then heading toward the outside while obeying the precedence rules. When you hit a "*", you say "pointer to"; when you hit "[]", you say "array of"; and when you hit "()" you say "function returning." For example: struct timecounter * volatile timecounter; /* "Timecounter is a volatile pointer to a struct timecounter." */ volatile struct timecounter *timecounter; /* "Timecounter is a pointer to a struct timecounter which is volatile." */ The reason for the awkward "which is" in that last one is just because C lets you get sloppy with the ordering of the outermost keywords. The pedantically correct way to declare a pointer to volatile struct is like this: struct timecounter volatile *timecounter; /* "Timecounter is a pointer to a volatile struct timecounter." */ John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 15: 1:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pr0n.kutulu.org (pr0n.kutulu.org [151.196.107.157]) by hub.freebsd.org (Postfix) with ESMTP id 9415237B428 for ; Tue, 5 Feb 2002 15:01:09 -0800 (PST) Received: by pr0n.kutulu.org (Postfix, from userid 1000) id A07BB60; Tue, 5 Feb 2002 18:04:27 -0500 (EST) Date: Tue, 5 Feb 2002 18:04:27 -0500 From: Kutulu To: Bakul Shah Cc: Poul-Henning Kamp , John Polstra , hackers@freebsd.org Subject: Re: A question about timecounters Message-ID: <20020205180427.A29033@pr0n.kutulu.org> References: <92661.1012938731@critter.freebsd.dk> <200202052242.RAA05212@renown.cnchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202052242.RAA05212@renown.cnchost.com>; from bakul@bitblocks.com on Tue, Feb 05, 2002 at 02:42:38PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 05, 2002 at 02:42:38PM -0800, Bakul Shah wrote: > > PS: Chances are most people don't have cdecl any more. You > can get it like this: > You can also get it like this: cd /usr/ports/devel/cdecl ; make install which I just went and did. Pretty helpful utility :) --K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 15: 1:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d179.as0.nwbl0.wi.voyager.net [169.207.130.181]) by hub.freebsd.org (Postfix) with ESMTP id 203DB37B421 for ; Tue, 5 Feb 2002 15:01:24 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g15H4jq03301; Tue, 5 Feb 2002 17:04:47 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Tue, 5 Feb 2002 17:04:44 +0000 (GMT) From: Mike Silbersack To: Alfred Perlstein Cc: Bruce Evans , Michal Mertl , , Subject: Re: stack alignment issues In-Reply-To: <20020205121923.O59017@elvis.mu.org> Message-ID: <20020205170020.V1617-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 5 Feb 2002, Alfred Perlstein wrote: > * Bruce Evans [020205 12:09] wrote: > > On Tue, 5 Feb 2002, Mike Silbersack wrote: > > > > > On Tue, 5 Feb 2002, Bruce Evans wrote: > > > > foo: > > > > pushl %ebp > > > > movl %esp,%ebp > > > > subl $8,%esp # <- extra instruction for alignment (for foo) > > > > addl $-12,%esp # <- extra instruction for alignment (for f1) > > > > > > What disgusting code. I find it amazing that they didn't even stick in > > > some peephole optimizer to at least limit it to one operation. > > > > It's clearly the result of work in progress :-). > > I see really cruddy stuff like this every time i do a gcc -S, don't > they watch for and try to fix this sort of thing? > > -- > -Alfred Perlstein [alfred@freebsd.org] Did you see that press release about how Microsoft is taking a month off from coding new features and dedicating everyone to fixing bugs? I can see an analogous headline: "FreeBSD developers get sick of gcc's code generation, devote March to compiler rewrite" and in related news: "Brett Glass finds out that FreeBSD developers are working on gcc and suffers a nervous breakdown." Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 15: 8:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.slc.edu (Weir-01a.SLC.Edu [198.83.6.252]) by hub.freebsd.org (Postfix) with ESMTP id 0219737B431 for ; Tue, 5 Feb 2002 15:08:26 -0800 (PST) Received: (from aschneid@localhost) by mail.slc.edu (8.11.6/8.11.6) id g15I7Ht07585; Tue, 5 Feb 2002 18:07:17 GMT (envelope-from aschneid@mail.slc.edu) Date: Tue, 5 Feb 2002 18:07:17 +0000 From: Anthony Schneider To: Bakul Shah Cc: Poul-Henning Kamp , John Polstra , hackers@FreeBSD.ORG Subject: Re: A question about timecounters Message-ID: <20020205180717.A7540@mail.slc.edu> References: <92661.1012938731@critter.freebsd.dk> <200202052242.RAA05212@renown.cnchost.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202052242.RAA05212@renown.cnchost.com>; from bakul@bitblocks.com on Tue, Feb 05, 2002 at 02:42:38PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > PS: Chances are most people don't have cdecl any more. You > can get it like this: cd /usr/ports/devel/cdecl && make install :) -Anthony. --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxgH1QACgkQ+rDjkNht5F1KjwCeNBMjxjtycoP22vhNRFOqp4Am yCcAoJeT5rCjN2P8gb5c1hQby867W2lO =1rI9 -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 15:20:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from comp.chem.msu.su (comp-ext.chem.msu.su [158.250.32.157]) by hub.freebsd.org (Postfix) with ESMTP id 4FDE437B421 for ; Tue, 5 Feb 2002 15:20:39 -0800 (PST) Received: (from yar@localhost) by comp.chem.msu.su (8.11.1/8.11.1) id g15NKU997667; Wed, 6 Feb 2002 02:20:30 +0300 (MSK) (envelope-from yar) Date: Wed, 6 Feb 2002 02:20:30 +0300 From: Yar Tikhiy To: "M. Warner Losh" Cc: hackers@FreeBSD.ORG Subject: Re: Get disk device size? Message-ID: <20020206022029.A95467@comp.chem.msu.su> References: <20020205125557.A10266@comp.chem.msu.su> <20020205.093006.104650505.imp@village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020205.093006.104650505.imp@village.org>; from imp@village.org on Tue, Feb 05, 2002 at 09:30:06AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 05, 2002 at 09:30:06AM -0700, M. Warner Losh wrote: > In message: <20020205125557.A10266@comp.chem.msu.su> > Yar Tikhiy writes: > : Could anyone point out at an ioctl or any other way to get a disk > : device size granted the device has no BSD label or PC slice table > : on it? Ways for both the userland and kernel are welcome. > > For userland, look at how fdisk and/or disklabel get it. > > For kernel, look at kern/subr_disk*.c Thanks, the DIOCGDINFO ioctl is nearly what I was looking for. However, there seems to be a number of problems (or my misunderstandings?) about it. This ioctl can't be used against non-BSD slices; it fails on them with EINVAL due to code in kern/subr_diskslice.c. OTOH, invoking this ioctl on a partition (e.g. ad0s1a) will result in the parameters of the whole slice/disk (i.e. ad0s1.) Isn't all that a bit inconsistent? E.g. a filesystem layer doesn't need to distinguish between say ad0, ad0s1, and ad0s1a -- they're just disk devices for it. Or did I miss any important point? -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 15:59:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 1AD0737B432 for ; Tue, 5 Feb 2002 15:59:11 -0800 (PST) Received: from user-37kaovf.dialup.mindspring.com ([207.69.99.239] helo=mr-p.protolan) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 16YFUS-0006kc-00; Tue, 05 Feb 2002 18:59:08 -0500 Date: Tue, 5 Feb 2002 19:03:26 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <154433028622.20020205190326@mindspring.com> To: Doug White Cc: freebsd-hackers@FreeBSD.ORG Subject: Re[2]: natd UDP errors with PPP demand dial In-Reply-To: <20020204114052.Q61624-100000@resnet.uoregon.edu> References: <20020204114052.Q61624-100000@resnet.uoregon.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG DW> On Sat, 2 Feb 2002, Marko wrote: >> My question is concerning the popular "netd[pid] failed to write >> packet back [Permission denied]" message. DW> This is caused by ipfw blocking packets after natd has translated them. DW> Check your firewall rules. DW> It might be an odd race of the rules not getting installed before natd DW> fires up. Are you using ppp.linkup (or equivalent) to configure ipfw in DW> this case? DW> Doug White | FreeBSD: The Power to Serve DW> dwhite@resnet.uoregon.edu | www.FreeBSD.org Doug, thank you for responding. I understand the firewall is blocking the packets. As I mentioned in my original message, the firewall should block them because the machine is trying to send these packets to the address it held during the preceding dial-up session for some reason. I am trying to figure out why it needs to do that. Furthermore, why would the machine need to send them from port 53 when named is not running on it. Natd is already running when a ppp session is set up each time. So is ipfw. Ipfw is configured thourgh its own configuration file. So, it seems I shouldn't have to set anything extra up in the ppp.linkup. I am just trying to first figure out why the machine is even trying to send those packets from port 53, among others, to an address it held during the previous ppp session. Thanks again, for replying. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 16:21:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by hub.freebsd.org (Postfix) with ESMTP id F0D4437B439 for ; Tue, 5 Feb 2002 16:21:31 -0800 (PST) Received: from fwd09.sul.t-online.de by mailout11.sul.t-online.com with smtp id 16YFpk-0005Ry-00; Wed, 06 Feb 2002 01:21:08 +0100 Received: from spirit.corecode.ath.cx (320050403952-0001@[217.224.168.238]) by fmrl09.sul.t-online.com with esmtp id 16YFpj-0dk7G4C; Wed, 6 Feb 2002 01:21:07 +0100 Received: from elevation.zuhause.stoert.net (elevation.zuhause.stoert.net [192.168.66.46]) by spirit.corecode.ath.cx (8.11.6/8.11.6) with ESMTP id g160L5g82116; Wed, 6 Feb 2002 01:21:05 +0100 (CET) (envelope-from corecode@elevation.zuhause.stoert.net) Received: (from corecode@localhost) by elevation.zuhause.stoert.net (8.11.6/8.11.6) id g160L1q04886; Wed, 6 Feb 2002 01:21:01 +0100 (CET) (envelope-from corecode) Date: Wed, 6 Feb 2002 01:20:52 +0100 From: "Simon 'corecode' Schubert" To: Terry Lambert Cc: bright@mu.org, silby@silby.com, bde@zeta.org.au, mime@traveller.cz, hackers@FreeBSD.ORG, greg@bogslab.ucdavis.edu Subject: Re: stack alignment issues Message-Id: <20020206012052.4b1ee3d2.corecode@corecode.ath.cx> In-Reply-To: <3C5F1AEB.2946887D@mindspring.com> References: <20020205043744.G23848-100000@gamplex.bde.org> <20020204120547.B2144-100000@patrocles.silby.com> <20020204101118.A12744@elvis.mu.org> <3C5F1AEB.2946887D@mindspring.com> X-Mailer: Sylpheed version 0.7.0claws21 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=.4Y62Wvn88vLK9z" X-Sender: 320050403952-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=.4Y62Wvn88vLK9z Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 04 Feb 2002 15:36:11 -0800 Terry Lambert wrote: > Alfred Perlstein wrote: > > > Well, if Linux aligns the initial stack, the chance that gcc will > > > have auto-alignment added sounds to be about zero. You might as > > > well go ahead with your patch when you get a chance. > > > > I agree, either way we should try to optimized the current > > situation, especially if it seems to give a 2x perf boost! > > How about "aligning the initial stack"? i think this is a good idea (besides trying to optimize gcc). and it shouldn't be too hard to accomplish this (i don't know the code for rtld, but it really shouldn't be too hard to do this) unfortunately i don't have time ATM otherwise i'd look into this cheerz corecode -- /"\ http://corecode.ath.cx/ \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News --=.4Y62Wvn88vLK9z Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE8YHbtr5S+dk6z85oRAsN+AKCx12SVJlp8Pew4o2Gv+sN9oohSUACgo+M1 3YdvNP6yAnBYq9IV7HgJm5E= =H70j -----END PGP SIGNATURE----- --=.4Y62Wvn88vLK9z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 16:55:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from artemis.drwilco.net (diana.drwilco.net [66.48.127.79]) by hub.freebsd.org (Postfix) with ESMTP id A5C7737B417 for ; Tue, 5 Feb 2002 16:55:36 -0800 (PST) Received: from ceres.drwilco.net (docwilco.xs4all.nl [213.84.68.230]) by artemis.drwilco.net (8.11.6/8.11.6) with ESMTP id g160tKZ92847 (using TLSv1/SSLv3 with cipher DES-CBC3-SHA (168 bits) verified NO); Tue, 5 Feb 2002 19:55:21 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-Id: <5.1.0.14.0.20020206020222.01c18290@mail.drwilco.net> X-Sender: lists@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 06 Feb 2002 02:05:21 +0100 To: Anikin , Doug White From: "Rogier R. Mulhuijzen" Subject: Re[2]: natd UDP errors with PPP demand dial Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <154433028622.20020205190326@mindspring.com> References: <20020204114052.Q61624-100000@resnet.uoregon.edu> <20020204114052.Q61624-100000@resnet.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Natd is already running when a ppp session is set up each time. So is >ipfw. Ipfw is configured thourgh its own configuration file. So, it >seems I shouldn't have to set anything extra up in the ppp.linkup. 1) Have you told natd the interface is dynamic and might change IPs? 2) If you're using ppp, why even bother with natd? The NAT in ppp uses the exact same libalias and gives you less headaches with ipfw because the translation on incoming packets is done before they hit ipfw, and outgoing after ipfw let them go. I can tell you this helps a lot when trying to use dynamic rules. Or am I missing some part of the picture? Doc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 17:33:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ajax.cnchost.com (ajax.cnchost.com [207.155.248.31]) by hub.freebsd.org (Postfix) with ESMTP id AC50C37B419 for ; Tue, 5 Feb 2002 17:33:19 -0800 (PST) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by ajax.cnchost.com id UAA20243; Tue, 5 Feb 2002 20:33:15 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <200202060133.UAA20243@ajax.cnchost.com> To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters In-reply-to: Your message of "Tue, 05 Feb 2002 14:59:22 PST." <200202052259.g15MxMv04928@vashon.polstra.com> Date: Tue, 05 Feb 2002 17:33:16 -0800 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Is C a great language, or what? ;-) Nah, just mediocre even when it comes to obfuscation! Have you played with unlambda?! > The way I always remember it is that you read the declaration > inside-out: starting with the variable name and then heading toward > the outside while obeying the precedence rules. When you hit a "*", > you say "pointer to"; when you hit "[]", you say "array of"; and when > you hit "()" you say "function returning." For example: I remember something about switching declaration reading direction when you hit a bracket; but why bother once you have cdecl? cdecl> declare f as array of pointer to function returning pointer to function returning int int (*(*f[])())() It is not clear to me how to apply your rule. It doesn't matter though, it is gotten to the point where I can only store ptrs to ptrs to information in my ever shrinking brain! To the people who pointed out the cdecl port, I did look in /usr/ports/devel but missed cdecl somehow. Sigh... :-) -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 18:47:52 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 6202E37B417 for ; Tue, 5 Feb 2002 18:47:45 -0800 (PST) Received: from pool0362.cvx40-bradley.dialup.earthlink.net ([216.244.43.107] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YI7P-0005Da-00; Tue, 05 Feb 2002 18:47:32 -0800 Message-ID: <3C60993E.8FEE6BF0@mindspring.com> Date: Tue, 05 Feb 2002 18:47:26 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: hackers@freebsd.org, phk@critter.freebsd.dk Subject: Re: A question about timecounters References: <92661.1012938731@critter.freebsd.dk> <200202052028.g15KSna04510@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra wrote: > After 25 minutes testing that with NTIMECOUNTER=50000, I haven't > gotten any microuptime messages. So it appears that my problem was > just that the current timecounter wrapped all the way around the ring > while microuptime was interrupted, due to the high HZ value and the > heavy interrupt load. I'm sorry I didn't try this sooner, when you > suggested it. > > After lunch I'll try NTIMECOUNTER=HZ (10000 in my case). That sounds > like a nice default value to me. 5 * HZ @ 10,000 HZ * sizeof(struct timecounter) = 5 * 10000 * 23*4 = 4,600,000 = 4.5M in timecounter structures Even with your NTIMECOUNTER=HZ (assuming it even works), that is 1M of memory burned on timecounter structures to prevent wrap around. If the interrupts are happening fast enough that wrap is this bad a problem, then I suggest another counter that divides the interupt frequency down to a (much smaller) update frequency for the timecounter. Is having this many of these things really worthwhile? I can't see how off the top of my head, but I can imagine a situation where it miht be referenced with a higher than wrap frequency... but the question is, what's the highest access frequency? That should limit the update frequency to twice that, right, which would guarantee adequate update resolution to satisfy that use? If it is, could we maybe just count wraps, instead, and add 7.7? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 19: 8:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id 298F837B42B for ; Tue, 5 Feb 2002 19:08:48 -0800 (PST) Received: from fwd03.sul.t-online.de by mailout01.sul.t-online.com with smtp id 16YIRz-0006IB-00; Wed, 06 Feb 2002 04:08:47 +0100 Received: from frolic.no-support.loc (520094253176-0001@[80.130.202.111]) by fmrl03.sul.t-online.com with esmtp id 16YIRy-0bgWZ6C; Wed, 6 Feb 2002 04:08:46 +0100 Received: (from bjoern@localhost) by frolic.no-support.loc (8.11.6/8.9.3) id g1633w103183; Wed, 6 Feb 2002 04:03:58 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Wed, 6 Feb 2002 04:03:57 +0100 To: John Polstra Cc: hackers@FreeBSD.ORG Subject: [patch] using ldd on shared libraries Message-ID: <20020206030357.GB2162@frolic.no-support.loc> References: <20020201201018.GB2992@frolic.no-support.loc> <20020201212028.GC2992@frolic.no-support.loc> <200202020424.g124OXD03238@vashon.polstra.com> <20020202125107.GA481@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20020202125107.GA481@frolic.no-support.loc> User-Agent: Mutt/1.3.25i X-Sender: 520094253176-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello John, I had to closer look into shared objects wrt self-containedness. Here is a patch for ldd(1), that extends it to be used w/ shared libraries, too. The patch probably needs some cleanup, but it works. ldd-stub should be in /usr/libexec. Is /usr/libexec/elf preferable? Do you have an idea how to generate an ldd-stub without a DT_NEEDED for libc.so (and still working with ldd, of course)? -Bj=F6rn --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ldd-patch.udif" --- ldd.c 2002/02/06 02:17:46 1.1 +++ ldd.c 2002/02/06 02:39:49 @@ -42,6 +42,8 @@ #include #include +#define LDD_STUB "/usr/libexec/ldd-stub" + extern void dump_file __P((const char *)); extern int error_count; @@ -116,6 +118,9 @@ int n; int status; int file_ok; + int shared_object; + + shared_object = 0; if ((fd = open(*argv, O_RDONLY, 0)) < 0) { warn("%s", *argv); @@ -152,6 +157,10 @@ warnx("%s: can't read program header", *argv); file_ok = 0; } else { + if (ehdr.e_type == ET_DYN) { + shared_object = 1; + dynamic = 1; + } else { /* need to fix white spaces */ for (i = 0; i < ehdr.e_phnum; i++) { if (read(fd, &phdr, ehdr.e_phentsize) != sizeof phdr) { @@ -163,6 +172,7 @@ if (phdr.p_type == PT_DYNAMIC) dynamic = 1; } + } } if (!dynamic) { warnx("%s: not a dynamic executable", *argv); @@ -204,7 +214,11 @@ } break; case 0: - rval |= execl(*argv, *argv, NULL) != 0; + if (shared_object) { + setenv("LD_PRELOAD", *argv, 1); + rval |= execl(LDD_STUB, LDD_STUB, NULL) != 0; + } else + rval |= execl(*argv, *argv, NULL) != 0; warn("%s", *argv); _exit(1); } --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ldd-stub.c" int main(int argc, char *argv[]) { } --EeQfGwPcQSOJBaQU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 19:15: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 943A937B417; Tue, 5 Feb 2002 19:15:01 -0800 (PST) Received: from pool0362.cvx40-bradley.dialup.earthlink.net ([216.244.43.107] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YIY0-0000li-00; Tue, 05 Feb 2002 19:15:00 -0800 Message-ID: <3C609FAE.9B4B4EA1@mindspring.com> Date: Tue, 05 Feb 2002 19:14:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yar Tikhiy Cc: "M. Warner Losh" , hackers@FreeBSD.ORG Subject: Re: Get disk device size? References: <20020205125557.A10266@comp.chem.msu.su> <20020205.093006.104650505.imp@village.org> <20020206022029.A95467@comp.chem.msu.su> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yar Tikhiy wrote: > Thanks, the DIOCGDINFO ioctl is nearly what I was looking for. > > However, there seems to be a number of problems (or my misunderstandings?) > about it. This ioctl can't be used against non-BSD slices; it > fails on them with EINVAL due to code in kern/subr_diskslice.c. > OTOH, invoking this ioctl on a partition (e.g. ad0s1a) will result > in the parameters of the whole slice/disk (i.e. ad0s1.) Isn't all > that a bit inconsistent? E.g. a filesystem layer doesn't need to > distinguish between say ad0, ad0s1, and ad0s1a -- they're just > disk devices for it. Or did I miss any important point? You missed the fact that there is not a uniform kernel API for manipulating disk space. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 19:50:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from 207-194-143-195.dsl.axion.net (207-194-143-195.dsl.axion.net [207.194.143.195]) by hub.freebsd.org (Postfix) with ESMTP id D1F6C37B400; Tue, 5 Feb 2002 19:50:23 -0800 (PST) Received: from roller.pangolin-systems.com (h24-77-105-71.vc.shawcable.net [24.77.105.71] (may be forged)) by 207-194-143-195.dsl.axion.net (8.11.6/8.11.6) with ESMTP id g163oFG43139; Tue, 5 Feb 2002 19:50:16 -0800 (PST) (envelope-from jhanna@shaw.ca) Message-Id: <200202060350.g163oFG43139@207-194-143-195.dsl.axion.net> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200112071631.fB7GVgr36045@h24-79-126-98.vc.shawcable.net> Date: Tue, 05 Feb 2002 19:50:14 -0800 (PST) Reply-To: Jonathan Hanna From: Jonathan Hanna To: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: Whats with this -> sendto: No buffer space available Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Dec-01 Jonathan Hanna wrote: > > Latest data point here: this time it was fixed mysteriously. > After noticing it was down, "netstat -m" showed no serious mbuf > use or peak use. "ep0" had: > ep0: flags=cc43 mtu 1500 > and the IP address was set up correctly > > "tcpdump -n -i ep0" worked, and after that the behavior was back to normal. > No restart of natd was done, no firewall rules flushed or reset. > This is on 4.3-STABLE FreeBSD 4.3-STABLE #3: Sun Jul 15 00:27:41 PDT 2001 I think I may have found the problem; it may be a bug in the ep 3c509 driver. The OACTIVE flag being set was a clue and I think tcpdump setting promiscuous mode may have reset the adapter. I have sent mail to the maintainer, but I am having some mail problems and am not sure it was received. Can anyone confirm that my number (3) question below does identify the problem? I am having ENBUFS problems with a 486 running 4.X stable on an 10BaseT ep interface. The ENOBUFS comes from ip_output seeing that the send queue is full. When this happens the OACTIVE flag is set and the interface is stuck untill ifconfig down/up is done. Looking at the ep driver, a few questions arise: (This is $FreeBSD: src/sys/dev/ep/if_ep.c,v 1.95.2.2 2000/07/17 21:24:26 archie Exp $) 1) in ep_if_start: if (inw(BASE + EP_W1_FREE_TX) < len + pad + 4) { /* no room in FIFO */ outw(BASE + EP_COMMAND, SET_TX_AVAIL_THRESH | (len + pad + 4)); /* make sure */ if (inw(BASE + EP_W1_FREE_TX) < len + pad + 4) { ifp->if_flags |= IFF_OACTIVE; return; } } else { outw(BASE + EP_COMMAND, SET_TX_AVAIL_THRESH | EP_THRESH_DISABLE); } If the second test of available TX space decides there is enough, should there be a disabling of the threshold as there is in the else clause? 2) in ep_intr: void ep_intr(arg) void *arg; { struct ep_softc *sc; register int status; struct ifnet *ifp; int x; x = splbio(); sc = (struct ep_softc *)arg; if (sc->gone) return; Should there not be an splx(x) if sc->gone is true? 3) in ep_intr: rescan: while ((status = inw(BASE + EP_STATUS)) & S_5_INTS) { /* first acknowledge all interrupt sources */ outw(BASE + EP_COMMAND, ACK_INTR | (status & S_MASK)); if (status & (S_RX_COMPLETE | S_RX_EARLY)) { old_status = status; epread(sc); continue; } It seems that if an RX is done then any TX conditions are lost as an ack of all sources has been done. I have verified that on the next look after the epread TX conditions have disappeared without being handled. If OACTIVE is set, then no if_start will not kikl the driver out of this condition. I suspect this is the problem I am seeing. 4) if_timer is set when a packet is sent out, but disabled as soon as any TX space is available. Any reason not to wait for completion? Thanks. Jonathan Hanna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 20:51:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8FFF737B417 for ; Tue, 5 Feb 2002 20:51:07 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g164owi13331; Tue, 5 Feb 2002 21:50:59 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g164owL34763; Tue, 5 Feb 2002 21:50:58 -0700 (MST) (envelope-from imp@village.org) Date: Tue, 05 Feb 2002 21:50:36 -0700 (MST) Message-Id: <20020205.215036.93760885.imp@village.org> To: jdp@polstra.com Cc: hackers@FreeBSD.ORG, phk@critter.freebsd.dk Subject: Re: A question about timecounters From: "M. Warner Losh" In-Reply-To: <200202051906.g15J68E04216@vashon.polstra.com> References: <91801.1012935515@critter.freebsd.dk> <200202051906.g15J68E04216@vashon.polstra.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <200202051906.g15J68E04216@vashon.polstra.com> John Polstra writes: : I'm testing that now. But for how long would microuptime have to : be interrupted to make this happen? Surely not 7.81 seconds! On : this same machine I have a curses application running which is : updating the screen once a second. It never misses a beat, and : userland is very responsive. Silly hypothesis. It isn't losing 7.81 seconds of time. Rather it is being interrupt at the wrong time and the wrap detection code works badly when interrupted at that point. So you aren't blocked for 7.81 seconds, but rather for 0.02 seconds since you are seeing the 7.79 jump. You are basically catching the wrong edge of the phase of the TSC. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 21:21: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 48C4F37B41A for ; Tue, 5 Feb 2002 21:21:03 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g165Kxo57020; Tue, 5 Feb 2002 21:20:59 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g165Kwj05514; Tue, 5 Feb 2002 21:20:58 -0800 (PST) (envelope-from jdp) Date: Tue, 5 Feb 2002 21:20:58 -0800 (PST) Message-Id: <200202060520.g165Kwj05514@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: bfischer@Techfak.Uni-Bielefeld.DE Subject: Re: [patch] using ldd on shared libraries In-Reply-To: <20020206030357.GB2162@frolic.no-support.loc> References: <20020201201018.GB2992@frolic.no-support.loc> <200202020424.g124OXD03238@vashon.polstra.com> <20020202125107.GA481@frolic.no-support.loc> <20020206030357.GB2162@frolic.no-support.loc> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020206030357.GB2162@frolic.no-support.loc>, Bjoern Fischer wrote: > I had to closer look into shared objects wrt self-containedness. > Here is a patch for ldd(1), that extends it to be used w/ shared > libraries, too. Thanks. Strangely enough, Maxim Sobolev committed changes to -current to do exactly the same thing (in a different way) just yesterday. Your patch won't be needed, but I do appreciate your having worked on it. You'd better watch your step if you don't want to wake up one morning and find that you've become the new maintainer of the dynamic linker. :-) Sorry I haven't replied to your earlier posting yet. I haven't really had time to give it much thought yet. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 22:36:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 39E3337B437 for ; Tue, 5 Feb 2002 22:36:38 -0800 (PST) Received: from pool0120.cvx22-bradley.dialup.earthlink.net ([209.179.198.120] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16YLgv-00060q-00; Tue, 05 Feb 2002 22:36:25 -0800 Message-ID: <3C60CEE4.FB1385BA@mindspring.com> Date: Tue, 05 Feb 2002 22:36:20 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: hackers@freebsd.org, bfischer@Techfak.Uni-Bielefeld.DE Subject: Re: [patch] using ldd on shared libraries References: <20020201201018.GB2992@frolic.no-support.loc> <200202020424.g124OXD03238@vashon.polstra.com> <20020202125107.GA481@frolic.no-support.loc> <20020206030357.GB2162@frolic.no-support.loc> <200202060520.g165Kwj05514@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra wrote: > In article <20020206030357.GB2162@frolic.no-support.loc>, Bjoern > Fischer wrote: > > I had to closer look into shared objects wrt self-containedness. > > Here is a patch for ldd(1), that extends it to be used w/ shared > > libraries, too. > > Thanks. Strangely enough, Maxim Sobolev committed changes to -current > to do exactly the same thing (in a different way) just yesterday. > Your patch won't be needed, but I do appreciate your having worked on > it. You'd better watch your step if you don't want to wake up one > morning and find that you've become the new maintainer of the dynamic > linker. :-) Any chance of getting one or the other of these into -stable? I've been missing this functionality since the ELF changeover first occurred. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 23: 0:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id CEA3937B404 for ; Tue, 5 Feb 2002 23:00:40 -0800 (PST) Received: (qmail 10669 invoked by uid 100); 6 Feb 2002 07:00:39 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15456.54422.979854.862471@guru.mired.org> Date: Wed, 6 Feb 2002 01:00:38 -0600 To: John Polstra Cc: hackers@freebsd.org Subject: Re: [patch] using ldd on shared libraries In-Reply-To: <200202060520.g165Kwj05514@vashon.polstra.com> References: <20020201201018.GB2992@frolic.no-support.loc> <200202020424.g124OXD03238@vashon.polstra.com> <20020202125107.GA481@frolic.no-support.loc> <20020206030357.GB2162@frolic.no-support.loc> <200202060520.g165Kwj05514@vashon.polstra.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-STABLE-i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra types: > Thanks. Strangely enough, Maxim Sobolev committed changes to -current > to do exactly the same thing (in a different way) just yesterday. > Your patch won't be needed, but I do appreciate your having worked on > it. You'd better watch your step if you don't want to wake up one > morning and find that you've become the new maintainer of the dynamic > linker. :-) How does this relate to PR bin/30908? Can it be closed? http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Feb 5 23:50:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from chylonia.3miasto.net (chylonia.3miasto.net [217.96.12.12]) by hub.freebsd.org (Postfix) with ESMTP id B2E7237B41C for ; Tue, 5 Feb 2002 23:50:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by chylonia.3miasto.net (8.11.3nb1/8.11.3) with ESMTP id g167s4700806; Wed, 6 Feb 2002 08:54:04 +0100 (CET) Date: Wed, 6 Feb 2002 08:54:04 +0100 (CET) From: Wojciech Puchar To: Thor Lancelot Simon Cc: , , Subject: Re: Athlon XP SSE flag not set? (AMD's response) In-Reply-To: <20020205221311.GA6958@rek.tjls.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > - These motherboards have BIOSes that enable SSE on AthlonXP. > > it's strange that BIOS have to do it. > > > - The end user should upgrade their BIOS if they have these motherboards. > > > > ask AMD how to enable it - it's probably few lines of assembly that could > > be added to NetBSD initialization code > > If freestyle stupidity were an Olympic event, Wojtek, you'd be a four-time > gold medal champion. now you show it not me. i could miss something in mail, but it's not reason to attack me in such child-like way. > What part of "" were you unable to read? so point me out instead of generating SMTP noise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 1:14:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 784E037B420 for ; Wed, 6 Feb 2002 01:14:23 -0800 (PST) Received: (qmail 19492 invoked by uid 1000); 6 Feb 2002 09:15:02 -0000 Date: Wed, 6 Feb 2002 11:15:02 +0200 From: Peter Pentchev To: Zhihui Zhang Cc: Poul-Henning Kamp , freebsd-hackers@freebsd.org Subject: Re: What is HIDE_POSIX & HIDE_BSD? Message-ID: <20020206111502.A5015@straylight.oblivion.bg> Mail-Followup-To: Zhihui Zhang , Poul-Henning Kamp , freebsd-hackers@freebsd.org References: <20020130111231.B4374@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from zzhang@cs.binghamton.edu on Wed, Jan 30, 2002 at 05:11:37PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 30, 2002 at 05:11:37PM -0500, Zhihui Zhang wrote: [top-posting; format recovered] > On Wed, 30 Jan 2002, Peter Pentchev wrote: > > > On Tue, Jan 29, 2002 at 03:58:16PM -0500, Zhihui Zhang wrote: > > > > > > While adding a system call, I notice in file syscall-hide.h there are > > > many instances of HIDE_POSIX() and HIDE_BSD(). What is the purpose of > > > these macros? Maybe they are now obsolete? > > > > The syscalls-hide.h file was generated from sys/kern/makesyscalls.sh > > from the third field of sys/kern/syscalls.master - POSIX, BSD or NOHIDE. > > However, three months ago Poul Henning-Kamp removed the syscalls-hide.h > > file and the relevant parts of makesyscalls.sh. I think that this may > > be scheduled for MFC'ing some time in the future, but you might have > > to ask phk for specifics. > > > > Also, I would also like to know what was the original purpose of > > the POSIX/BSD/NOHIDE distinction. BTW, should that field be removed > > from syscalls.master, too? > > I can't guess what does it mean by "hiding". Maybe any system call can be > hidden from some configuration of the kernel. Maybe we should CC phk@ explicitly then :) Poul-Henning, you removed the syscalls-hide file; could you shed some light on what it was meant to be used for? :) G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence would be seven words long if it were six words shorter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 1:54: 6 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (29.74.149.210.economy.2iij.net [210.149.74.29]) by hub.freebsd.org (Postfix) with SMTP id B3E6837B421; Wed, 6 Feb 2002 01:53:27 -0800 (PST) Received: from 158.26.35.129 ([158.26.35.129]) by hd.regsoft.net with asmtp; Wed, 06 Feb 2002 00:54:11 -0300 Received: from 32.241.57.187 ([32.241.57.187]) by q4.quik.com with local; 05 Feb 2002 15:50:02 +0600 Received: from [198.181.75.231] by n9.groups.yahoo.com with smtp; Wed, 06 Feb 2002 05:45:54 -0800 Received: from [197.61.143.88] by rly-yk04.mx.aol.com with NNFMP; Tue, 05 Feb 2002 20:41:46 +0100 Received: from unknown (HELO smtp-server1.cfl.rr.com) (155.40.236.237) by n9.groups.yahoo.com with QMQP; Tue, 05 Feb 2002 17:37:38 +0400 Reply-To: Message-ID: <004d36b40dda$1442e6c7$2eb00db1@fdymoq> From: To: Cc: , , , , , , , , Subject: See Real Babes (0384CuMg3-126YqKc6577@20) MiME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00C4_03E14D8D.A0707E67" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: QUALCOMM Windows Eudora Version 5.1 Importance: Normal Date: Wed, 6 Feb 2002 01:53:27 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------=_NextPart_000_00C4_03E14D8D.A0707E67 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQgc2l6ZT0i MiI+PHU+PGI+V0FSTklORzwvYj48L3U+OiBUaGUgZm9sbG93aW5nIG1hdGVy aWFsIGlzIG9mIGFuIGV4dHJlbWUNCmFkdWx0IG5hdHVyZS4gSWYgeW91IGFy ZTxicj4NCm9mZmVuZGVkIGJ5IGV4cGxpY2l0IGFkdWx0IG1hdGVyaWFsIG9y IGFyZSB1bmRlciB0aGUgYWdlIG9mIDE4LCZuYnNwOyBkZWxldGUNCnRoaXMg ZW1haWwgbm93PC9mb250Pjxmb250IHNpemU9IjEiPi48L2ZvbnQ+DQo8cD4N CjxhIGltZyBTUkM9ImcwMS5qcGciIEJPUkRFUj0iMCIgaGVpZ2h0PSIxMDUi IHdpZHRoPSIxNDAiIGhyZWY9Imh0dHA6Ly93d3cuZnJlZXdlYmhvc3Q0dS5j b20vc2V4eTA4L2luZGV4b3MuaHRtIj4NCjxpbWcgU1JDPSJodHRwOi8vd3d3 OS5raW5naG9zdC5jb20vdGVlbi90bTMxNDUwLzIzLmpwZyIgQk9SREVSPTAg aGVpZ2h0PTEwNSB3aWR0aD0xNDA+DQo8aW1nIFNSQz0iaHR0cDovL3d3dzku a2luZ2hvc3QuY29tL3RlZW4vdG0zMTQ1MC9idXR0MS5qcGciIEJPUkRFUj0w IGhlaWdodD0xMDUgd2lkdGg9MTQwPg0KPGltZyBTUkM9Imh0dHA6Ly93d3c5 Lmtpbmdob3N0LmNvbS90ZWVuL3RtMzE0NTAvc2hlMS5qcGciIEJPUkRFUj0w IGhlaWdodD0xMDUgd2lkdGg9MTQwPg0KDQo8L2E+PC9wPg0KPHA+PGEgaW1n IFNSQz0iZzAxLmpwZyIgQk9SREVSPSIwIiBoZWlnaHQ9IjEwNSIgd2lkdGg9 IjE0MCIgaHJlZj0iaHR0cDovL3d3dy5mcmVld2ViaG9zdDR1LmNvbS9zZXh5 MDgvaW5kZXhvcy5odG0iPg0KPHU+VEhFIDxmb250IGNvbG9yPSIjRkYwMDAw Ij48Yj5IT1QtRVNUPC9iPjwvZm9udD4mbmJzcDsmbmJzcDsgKipYWFgqKiZu YnNwOw0KVEVFTiBIQVJEQ09SRSA8YnI+DQpBQ1RJT04gT04gVEhFIE5FVCBU T0RBWSEhPC91PjwvYT48L3A+DQo8cD48YSBpbWcgU1JDPSJnMDEuanBnIiBC T1JERVI9IjAiIGhlaWdodD0iMTA1IiB3aWR0aD0iMTQwIiBocmVmPSJodHRw Oi8vd3d3LmZyZWV3ZWJob3N0NHUuY29tL3NleHkwOC9pbmRleG9zLmh0bSI+ DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio8YnI+DQpD TElDSyBIRVJFIEZPUiBJTlNUQU5UIEFDQ0VTUzxicj4NCioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKjwvYT48L3A+DQo8cD48dT48Yj5C ZXN0IGNvbnRlbnQgYXJvdW5kPC9iPjwvdT4gLSA8YnI+DQpDVU1TSE9UIEZh bnRhc2llczxicj4NCkFTUyBGYW50YXNpZXM8YnI+DQpTTVVUIEZhbnRhc2ll czxicj4NCkxFU0JJQU4gRmFudGFzaWVzPGJyPg0KT1JJRU5UQUwgRmFudGFz aWVzIEdBTE9SRTwvcD4NCjxwPjx1PlNQRUNJQUwgQk9OVVMgRk9SIFRSSUFM IE1FTUJFUlNISVA8YnI+DQo8L3U+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 IDxmb250IHNpemU9IjQiPiEhITkgYnJhbmQgbmV3IGNlbGViIG1vdmllcyEh ITwvZm9udD48L3A+DQo8cD4qKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0 dHA6Ly93d3cuZnJlZXdlYmhvc3Q0dS5jb20vc2V4eTA4L2luZGV4b3MuaHRt Ij5DTElDSw0KSEVSRSBGT1IgSU5TVEFOVCBBQ0NFU1M8L2E+PGJyPg0KKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxicj4NCklmIHlv dSBoYXZlIHJlY2VpdmVkIHRoaXMgbWVzc2FnZSBpbiBlcnJvciZuYnNwOzxi cj4NCmFuZCB3aXNoIHRvIGJlIHJlbW92ZWQgcGxlYXNlIDxhIGhyZWY9Im1h aWx0bzp0bTMxMDQ1NkB5YWhvby5jb20iPmNsaWNrDQpoZXJlPC9hPiBhbmQg cHV0Jm5ic3A7PGJyPg0KJnF1b3Q7R0VUIE1FIE9GRiZxdW90OyBpbiB0aGUg c3ViamVjdCBsaW5lPC9wPg0KPHA+Jm5ic3A7PC9wPg0KPC9ib2R5Pg0KPC9o dG1sPg0KDQpbMDM4NEA0XQ0K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 2: 0: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A7F1F37B425 for ; Wed, 6 Feb 2002 02:00:00 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g169uFM04162; Wed, 6 Feb 2002 10:56:46 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Pentchev Cc: Zhihui Zhang , freebsd-hackers@FreeBSD.org Subject: Re: What is HIDE_POSIX & HIDE_BSD? In-Reply-To: Your message of "Wed, 06 Feb 2002 11:15:02 +0200." <20020206111502.A5015@straylight.oblivion.bg> Date: Wed, 06 Feb 2002 10:56:15 +0100 Message-ID: <4160.1012989375@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020206111502.A5015@straylight.oblivion.bg>, Peter Pentchev writes: >Maybe we should CC phk@ explicitly then :) Poul-Henning, you removed >the syscalls-hide file; could you shed some light on what it was meant >to be used for? :) I have no idea and I couldn't find anybody using it so I nuked it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 4: 5: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f272.law10.hotmail.com [64.4.14.147]) by hub.freebsd.org (Postfix) with ESMTP id 6304837B423 for ; Wed, 6 Feb 2002 04:05:02 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 6 Feb 2002 04:05:02 -0800 Received: from 202.129.95.21 by lw10fd.law10.hotmail.msn.com with HTTP; Wed, 06 Feb 2002 12:05:01 GMT X-Originating-IP: [202.129.95.21] From: "Paulo Valdez" To: mwm@mired.org Cc: hackers@FreeBSD.org Subject: Re: VCD file system? Date: Wed, 06 Feb 2002 23:05:01 +1100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 06 Feb 2002 12:05:02.0251 (UTC) FILETIME=[81A037B0:01C1AF06] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This was a problem of mine awhile back it seems that in linux you are able to mount vcds but in Freebsd it is not well supported. I have managed to mount my vcds and use xine and mplayer to view them, but as far a looking into the vcd itself like a directory Freebsd seems to have lack of support. I hope i have managed to shed some light on the matter and hopefully someone will look into it. By the way if you need help playing your vcds give me hollar. Cheers Paulo _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 4:51:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from businessconnect.businessconnect.nl (www.bconnect.nl [194.109.100.125]) by hub.freebsd.org (Postfix) with ESMTP id 60C1837B42A for ; Wed, 6 Feb 2002 04:51:31 -0800 (PST) Received: from [195.38.249.132] by businessconnect.businessconnect.nl (Post.Office MTA v3.5 release 215 ID# 0-53760U1000L100S0V35) with SMTP id nl for ; Wed, 6 Feb 2002 13:44:24 +0000 From: Kempen Jobs BV To: freebsd-hackers@FreeBSD.org Subject: De Banenladder X-Mailer: TOS 6.0 SMTP SERVER Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 6 Feb 2002 13:44:24 +0000 Message-ID: <20020206134424765.DCY312@businessconnect.businessconnect.nl@[195.38.249.132]> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Op zoek naar een baan, opleiding, personeel of informatie over een bedrijf? Kijk dan op www.banenladder.nl De Banenladder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 5:21:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from vega.dhis.co.it.pt (a213-22-99-40.netcabo.pt [213.22.99.40]) by hub.freebsd.org (Postfix) with ESMTP id 4444137B43C; Wed, 6 Feb 2002 05:21:30 -0800 (PST) Received: (from nsubtil@localhost) by vega.dhis.co.it.pt (8.11.3/8.11.3) id g16DLQ913739; Wed, 6 Feb 2002 13:21:26 GMT (envelope-from nsubtil) Date: Wed, 6 Feb 2002 13:21:26 +0000 From: Nuno Subtil To: Jonathan Hanna Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Whats with this -> sendto: No buffer space available Message-ID: <20020206132126.A13595@vega.dhis.co.it.pt> References: <200112071631.fB7GVgr36045@h24-79-126-98.vc.shawcable.net> <200202060350.g163oFG43139@207-194-143-195.dsl.axion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202060350.g163oFG43139@207-194-143-195.dsl.axion.net>; from jhanna@shaw.ca on Tue, Feb 05, 2002 at 07:50:14PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 05, 2002 at 07:50:14PM -0800, Jonathan Hanna wrote: > > On 07-Dec-01 Jonathan Hanna wrote: > > > > Latest data point here: this time it was fixed mysteriously. > > After noticing it was down, "netstat -m" showed no serious mbuf > > use or peak use. "ep0" had: > > ep0: flags=cc43 mtu 1500 > > and the IP address was set up correctly > > > > "tcpdump -n -i ep0" worked, and after that the behavior was back to normal. > > No restart of natd was done, no firewall rules flushed or reset. > > This is on 4.3-STABLE FreeBSD 4.3-STABLE #3: Sun Jul 15 00:27:41 PDT 2001 I have also seen these symptoms, but on an ISDN interface. The machine does NAT, and sometimes it just stops working. I can ssh into it through the "internal" NIC (an ISA NE2000 clone), but no traffic ever goes out through the ISDN interface --- any program that generates traffic through that interface returns the same error: "No buffer space available". netstat -m also shows nothing apparently wrong with mbuf usage. This happens about once or twice every two months or so, and a reboot fixes it. I can't recall seeing any special flags on the interface when this happens, nor do I remember trying to run tcpdump on the interface, but I can try that if it happens again. The ISDN card is a mysterious "combo" card which apparently does video-capture as well. The ISDN part works with the Teles S0/16.3 driver, modified to accept the card's signature. NAT is done through ipnat, and the ppp connection is managed by the userland ppp daemon. It runs 4.3-STABLE from around the beginning of May 2001. Nuno Subtil nsubtil@vega.dhis.co.it.pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 6:11:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from clientmail.ehsrealtime.com (eris.ehsrealtime.com [213.52.146.130]) by hub.freebsd.org (Postfix) with ESMTP id C353D37B420 for ; Wed, 6 Feb 2002 06:11:25 -0800 (PST) Received: from set.ehsrealtime.com ([213.52.146.197]) by clientmail.ehsrealtime.com with esmtp (Exim 3.33 #2) id 16YSQq-000IdD-01 for freebsd-hackers@freebsd.org; Wed, 06 Feb 2002 13:48:16 +0000 Received: from waynep by set.ehsrealtime.com with local (Exim 3.34 #3) id 16YSnv-0000Ss-00 for freebsd-hackers@freebsd.org; Wed, 06 Feb 2002 14:12:07 +0000 From: Wayne Pascoe To: freebsd-hackers@freebsd.org Subject: Where are the closed PR's ? Date: 06 Feb 2002 14:12:06 +0000 Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.5 (bamboo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, I am trying to break into contributing to FreeBSD. I've been reading through the PR database, but the one thing that I do not see is the closed PR's. The reason I want to see these is to see some sample problems, and how they were closed. Being able to see the patch, etc. would also be great. So in short, where can I find the closed PR's ? Thanks, -- - Wayne Pascoe | WINDOWS: Where do you want to go today? freebsd@molemanarmy.com | LINUX: Where do you want to go tomorrow? http://www.molemanarmy.com | FreeBSD: Are you guys coming or what? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 6:19:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [66.31.234.148]) by hub.freebsd.org (Postfix) with ESMTP id 149B137B41B for ; Wed, 6 Feb 2002 06:19:07 -0800 (PST) Received: (from root@localhost) by thehousleys.net (8.11.6/8.11.2) id g16EJ1x06972; Wed, 6 Feb 2002 09:19:01 -0500 (EST) (envelope-from jim@Thehousleys.net) Received: from Thehousleys.net (baby.int.thehousleys.net [192.168.0.125]) (authenticated) by thehousleys.net (8.11.6/8.11.6) with ESMTP id g16EIxp06964; Wed, 6 Feb 2002 09:18:59 -0500 (EST) (envelope-from jim@Thehousleys.net) Message-ID: <3C613B53.5B74F3A1@Thehousleys.net> Date: Wed, 06 Feb 2002 09:18:59 -0500 From: James Housley X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Wayne Pascoe Cc: freebsd-hackers@freebsd.org Subject: Re: Where are the closed PR's ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wayne Pascoe wrote: > > Hi there, > > I am trying to break into contributing to FreeBSD. I've been reading > through the PR database, but the one thing that I do not see is the > closed PR's. > > The reason I want to see these is to see some sample problems, and how > they were closed. Being able to see the patch, etc. would also be > great. > > So in short, where can I find the closed PR's ? > I assume you are at http://www.FreeBSD.org/cgi/query-pr-summary.cgi , right. In the last paragraph before all the PRs this is a link to "Include closed reports too" Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net jhousley@SimTel.Net http://www.SimTel.Net --------------------------------------------------------------------- "It's a damn poor mind that can only think of one way to spell a word." -- Andrew Jackson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 6:58:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90]) by hub.freebsd.org (Postfix) with ESMTP id D34C137B400 for ; Wed, 6 Feb 2002 06:58:21 -0800 (PST) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g16EwC824894; Wed, 6 Feb 2002 09:58:12 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g16EwAk17899; Wed, 6 Feb 2002 09:58:10 -0500 (EST) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 9156165; Wed, 06 Feb 2002 09:58:07 -0500 Message-ID: <3C614480.D1D46012@mitre.org> Date: Wed, 06 Feb 2002 09:58:08 -0500 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Paulo Valdez Cc: mwm@mired.org, hackers@freebsd.org Subject: Re: VCD file system? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Paulo Valdez wrote: > > This was a problem of mine awhile back it seems that in linux you are able > to mount vcds but in Freebsd it is not well supported. I have managed to > mount my vcds and use xine and mplayer to view them, but as far a looking > into the vcd itself like a directory Freebsd seems to have lack of support. > I hope i have managed to shed some light on the matter and hopefully someone > will look into it. By the way if you need help playing your vcds give me > hollar. One more thing. In Win2k if you tried to copy the mpeg data off of the VCD it would get slightly corrupted. You have to use a special tool to get the regular data off of the CD. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 8:56:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from sandbox.sandstorm.net (user-v3qtgdr.biz.mindspring.com [199.174.193.187]) by hub.freebsd.org (Postfix) with ESMTP id 902E137C423 for ; Wed, 6 Feb 2002 08:53:02 -0800 (PST) Received: from cjp by sandbox.sandstorm.net with local-esmtp (Exim 2.05 #2 (Debian)) id 16YUzG-0004TY-00; Wed, 6 Feb 2002 11:31:58 -0500 Date: Wed, 6 Feb 2002 11:31:58 -0500 (EST) From: Charles Peterman To: Subject: Binding a Process to a specific CPU Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am currently playing with a dual CPU machine. With 4.5, is there a way to guarantee that two specific processes never end up on the same processor? Or does this question betray my fundamental ignorance of how processes are allocated on an SMP based machine? Thanks much, Charles Peterman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 9:45:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 83DCA37B419 for ; Wed, 6 Feb 2002 09:45:48 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g16Hjft49656; Wed, 6 Feb 2002 12:45:41 -0500 (EST) (envelope-from mwlucas) Date: Wed, 6 Feb 2002 12:45:40 -0500 From: Michael Lucas To: Charles Peterman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Binding a Process to a specific CPU Message-ID: <20020206124540.A49624@blackhelicopters.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from cjp@sandbox.sandstorm.net on Wed, Feb 06, 2002 at 11:31:58AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Short answer: no. This requires some way of telling processes which CPU to bind to, i.e., CPU affinity. Right now, FreeBSD assigns processors based on a simple "scatter" algorithm. On Wed, Feb 06, 2002 at 11:31:58AM -0500, Charles Peterman wrote: > > I am currently playing with a dual CPU machine. > With 4.5, is there a way to guarantee that > two specific processes never end up on the same > processor? > > Or does this question betray my fundamental > ignorance of how processes are allocated on an > SMP based machine? > > Thanks much, > > Charles Peterman > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 10:42: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 8DD4A37B423 for ; Wed, 6 Feb 2002 10:41:56 -0800 (PST) Received: from user-37kaot0.dialup.mindspring.com ([207.69.99.160] helo=mr-p.protolan) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16YWyu-0002qQ-00; Wed, 06 Feb 2002 13:39:44 -0500 Date: Wed, 6 Feb 2002 13:44:04 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <165500266655.20020206134404@mindspring.com> To: "Rogier R. Mulhuijzen" Cc: Doug White , freebsd-hackers@FreeBSD.ORG Subject: Re[3]: natd UDP errors with PPP demand dial In-Reply-To: <5.1.0.14.0.20020206020222.01c18290@mail.drwilco.net> References: <20020204114052.Q61624-100000@resnet.uoregon.edu> <20020204114052.Q61624-100000@resnet.uoregon.edu> <5.1.0.14.0.20020206020222.01c18290@mail.drwilco.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thank you for your response, Rogier. RRM> 1) Have you told natd the interface is dynamic and might change IPs? Yes, of course. RRM> 2) If you're using ppp, why even bother with natd? The NAT in ppp uses the RRM> exact same libalias and gives you less headaches with ipfw because the RRM> translation on incoming packets is done before they hit ipfw, and outgoing RRM> after ipfw let them go. I can tell you this helps a lot when trying to use RRM> dynamic rules. That's a great idea! I had not considered it until now. I would just need to work the anti-spoofing and private net rules into the ppp nat process somehow. I guess, I would have to use ppp filtering just for those rules. If I can do that, your way does seem to be a good place to start in resolving my error messages. Thank you very much for your help! Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 11: 1:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (host086134.metrored.net.ar [200.49.86.134]) by hub.freebsd.org (Postfix) with SMTP id 0884437B41F; Wed, 6 Feb 2002 11:01:24 -0800 (PST) Received: from 39.214.100.236 ([39.214.100.236]) by rly-xl04.mx.aol.com with esmtp; Thu, 07 Feb 2002 01:17:43 -0600 Received: from [16.108.56.96] by mailout2-eri1.midsouth.rr.com with smtp; Wed, 06 Feb 2002 23:15:49 -0400 Received: from [20.207.216.155] by rly-xr02.mx.aol.com with esmtp; 06 Feb 2002 07:13:56 +1200 Received: from 207.160.75.113 ([207.160.75.113]) by rly-xl05.mx.aol.com with esmtp; Thu, 07 Feb 2002 04:12:03 -0900 Received: from 195.150.25.162 ([195.150.25.162]) by ssymail.ssy.co.kr with QMQP; 06 Feb 2002 09:10:10 +1000 Reply-To: Message-ID: <005b47e23aaa$6437b4a6$6ac10dd2@uryymh> From: To: Cc: , , Subject: COME PLAY WITH ME (2598RXGx3-@9) MiME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00C8_61B51E0B.B8331E48" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2462.0000 Importance: Normal Date: Wed, 6 Feb 2002 11:01:24 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------=_NextPart_000_00C8_61B51E0B.B8331E48 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjwvaGVhZD4NCjxib2R5Pg0KPGZvbnQgc2l6ZT0i MiI+PHU+PGI+V0FSTklORzwvYj48L3U+OiBUaGUgZm9sbG93aW5nIG1hdGVy aWFsIGlzIG9mIGFuIGV4dHJlbWUNCmFkdWx0IG5hdHVyZS4gSWYgeW91IGFy ZTxicj4NCm9mZmVuZGVkIGJ5IGV4cGxpY2l0IGFkdWx0IG1hdGVyaWFsIG9y IGFyZSB1bmRlciB0aGUgYWdlIG9mIDE4LCZuYnNwOyBkZWxldGUNCnRoaXMg ZW1haWwgbm93PC9mb250Pjxmb250IHNpemU9IjEiPi48L2ZvbnQ+DQo8cD4N CjxhIGltZyBTUkM9ImcwMS5qcGciIEJPUkRFUj0iMCIgaGVpZ2h0PSIxMDUi IHdpZHRoPSIxNDAiIGhyZWY9Imh0dHA6Ly93d3cuZnJlZXdlYmhvc3Q0dS5j b20vc2V4eTA4L2luZGV4b3MuaHRtIj4NCjxpbWcgU1JDPSJodHRwOi8vd3d3 OS5raW5naG9zdC5jb20vdGVlbi90bTMxNDUwLzIzLmpwZyIgQk9SREVSPTAg aGVpZ2h0PTEwNSB3aWR0aD0xNDA+DQo8aW1nIFNSQz0iaHR0cDovL3d3dzku a2luZ2hvc3QuY29tL3RlZW4vdG0zMTQ1MC9idXR0MS5qcGciIEJPUkRFUj0w IGhlaWdodD0xMDUgd2lkdGg9MTQwPg0KPGltZyBTUkM9Imh0dHA6Ly93d3c5 Lmtpbmdob3N0LmNvbS90ZWVuL3RtMzE0NTAvc2hlMS5qcGciIEJPUkRFUj0w IGhlaWdodD0xMDUgd2lkdGg9MTQwPg0KDQo8L2E+PC9wPg0KPHA+PGEgaW1n IFNSQz0iZzAxLmpwZyIgQk9SREVSPSIwIiBoZWlnaHQ9IjEwNSIgd2lkdGg9 IjE0MCIgaHJlZj0iaHR0cDovL3d3dy5mcmVld2ViaG9zdDR1LmNvbS9zZXh5 MDgvaW5kZXhvcy5odG0iPg0KPHU+VEhFIDxmb250IGNvbG9yPSIjRkYwMDAw Ij48Yj5IT1QtRVNUPC9iPjwvZm9udD4mbmJzcDsmbmJzcDsgKipYWFgqKiZu YnNwOw0KVEVFTiBIQVJEQ09SRSA8YnI+DQpBQ1RJT04gT04gVEhFIE5FVCBU T0RBWSEhPC91PjwvYT48L3A+DQo8cD48YSBpbWcgU1JDPSJnMDEuanBnIiBC T1JERVI9IjAiIGhlaWdodD0iMTA1IiB3aWR0aD0iMTQwIiBocmVmPSJodHRw Oi8vd3d3LmZyZWV3ZWJob3N0NHUuY29tL3NleHkwOC9pbmRleG9zLmh0bSI+ DQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio8YnI+DQpD TElDSyBIRVJFIEZPUiBJTlNUQU5UIEFDQ0VTUzxicj4NCioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKjwvYT48L3A+DQo8cD48dT48Yj5C ZXN0IGNvbnRlbnQgYXJvdW5kPC9iPjwvdT4gLSA8YnI+DQpDVU1TSE9UIEZh bnRhc2llczxicj4NCkFTUyBGYW50YXNpZXM8YnI+DQpTTVVUIEZhbnRhc2ll czxicj4NCkxFU0JJQU4gRmFudGFzaWVzPGJyPg0KT1JJRU5UQUwgRmFudGFz aWVzIEdBTE9SRTwvcD4NCjxwPjx1PlNQRUNJQUwgQk9OVVMgRk9SIFRSSUFM IE1FTUJFUlNISVA8YnI+DQo8L3U+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 IDxmb250IHNpemU9IjQiPiEhITkgYnJhbmQgbmV3IGNlbGViIG1vdmllcyEh ITwvZm9udD48L3A+DQo8cD4qKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7IDxhIGhyZWY9Imh0 dHA6Ly93d3cuZnJlZXdlYmhvc3Q0dS5jb20vc2V4eTA4L2luZGV4b3MuaHRt Ij5DTElDSw0KSEVSRSBGT1IgSU5TVEFOVCBBQ0NFU1M8L2E+PGJyPg0KKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKjxicj4NCklmIHlv dSBoYXZlIHJlY2VpdmVkIHRoaXMgbWVzc2FnZSBpbiBlcnJvciZuYnNwOzxi cj4NCmFuZCB3aXNoIHRvIGJlIHJlbW92ZWQgcGxlYXNlIDxhIGhyZWY9Im1h aWx0bzp0bTMxMDQ1NkB5YWhvby5jb20iPmNsaWNrDQpoZXJlPC9hPiBhbmQg cHV0Jm5ic3A7PGJyPg0KJnF1b3Q7R0VUIE1FIE9GRiZxdW90OyBpbiB0aGUg c3ViamVjdCBsaW5lPC9wPg0KPHA+Jm5ic3A7PC9wPg0KPC9ib2R5Pg0KPC9o dG1sPg0KDQpbMjMwNlNQYk8zLTQxOGNsbG84Mzg5dkduWTMtMDQ0bFl1VDY2 MDhySEAzOF0NCg== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 12: 5:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from vega.dhis.co.it.pt (a213-22-99-40.netcabo.pt [213.22.99.40]) by hub.freebsd.org (Postfix) with ESMTP id 7467A37B41D; Wed, 6 Feb 2002 12:05:26 -0800 (PST) Received: (from nsubtil@localhost) by vega.dhis.co.it.pt (8.11.3/8.11.3) id g16K5Ob15233; Wed, 6 Feb 2002 20:05:24 GMT (envelope-from nsubtil) Date: Wed, 6 Feb 2002 20:05:24 +0000 From: Nuno Subtil To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Whats with this -> sendto: No buffer space available Message-ID: <20020206200524.A14992@vega.dhis.co.it.pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Karl Dietz asked for this to be forwarded to the lists, so here it is. ----- Forwarded message from Karl Dietz ----- From: "Karl Dietz" Date: Wed, 6 Feb 2002 19:02:51 +0100 To: "Jonathan Hanna" , Subject: Re: Whats with this -> sendto: No buffer space available X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Meanwhile I have browsed through the code of ep and vx. > 3) in ep_intr: > > rescan: > > while ((status = inw(BASE + EP_STATUS)) & S_5_INTS) { > > /* first acknowledge all interrupt sources */ > outw(BASE + EP_COMMAND, ACK_INTR | (status & S_MASK)); > > if (status & (S_RX_COMPLETE | S_RX_EARLY)) { > old_status = status; > epread(sc); > continue; > } > > It seems that if an RX is done then any TX conditions are lost as an ack of all > sources has been done. I have verified that on the next look after the epread > TX conditions have disappeared without being handled. If OACTIVE is set, the vx driver (which is to be folded back into ep) has a more verbose comment on the code in question: /* * Acknowledge any interrupts. It's important that we do this * first, since there would otherwise be a race condition. * Due to the i386 interrupt queueing, we may get spurious * interrupts occasionally. */ But the handler is written in a way that tx interupts get lost only if a card failure occurs. Anyway the modified driver has transfered more than 4 million packets already without a problem (two interfaces, some flood pings, and the whole internet traffic) Regards, Karl PS: Can one of you forward this to the list? ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 12:15: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id A53AB37B42B for ; Wed, 6 Feb 2002 12:14:58 -0800 (PST) Received: by seven.Alameda.net (Postfix, from userid 1000) id 3D7D23A3EC; Wed, 6 Feb 2002 12:14:58 -0800 (PST) Date: Wed, 6 Feb 2002 12:14:58 -0800 From: Ulf Zimmermann To: hackers@freebsd.org Subject: Can someone fix releng4.freebsd.org to name snapshots right ? Message-ID: <20020206121458.N45642@seven.alameda.net> Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG drwxr-xr-x 20 root wheel 1024 Jan 30 17:13 4.4-20020130-STABLE drwxr-xr-x 20 root wheel 1024 Jan 31 18:06 4.4-20020131-STABLE drwxr-xr-x 20 root wheel 1024 Feb 1 16:59 4.4-20020201-STABLE drwxr-xr-x 20 root wheel 1024 Feb 2 16:47 4.4-20020202-STABLE drwxr-xr-x 20 root wheel 1024 Feb 3 16:48 4.4-20020203-STABLE drwxr-xr-x 20 root wheel 1024 Feb 4 17:04 4.4-20020204-STABLE drwxr-xr-x 20 root wheel 1024 Feb 5 17:09 4.4-20020205-STABLE drwxr-xr-x 20 root wheel 1024 Feb 6 16:42 4.4-20020206-STABLE Shouldn't these directories be named 4.5-xxxxx-STABLE by now ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 14:39: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129]) by hub.freebsd.org (Postfix) with ESMTP id 0D88737B41A for ; Wed, 6 Feb 2002 14:38:58 -0800 (PST) Received: from umesh-bsd.juniper.net (umesh-bsd.juniper.net [172.17.12.70]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id g16Mcl668686 for ; Wed, 6 Feb 2002 14:38:47 -0800 (PST) (envelope-from umesh@juniper.net) Received: (from umesh@localhost) by umesh-bsd.juniper.net (8.8.8/8.7.3) id OAA26239 for freebsd-hackers@freebsd.org; Wed, 6 Feb 2002 14:38:47 -0800 (PST) Date: Wed, 6 Feb 2002 14:38:47 -0800 From: Umesh Krishnaswamy To: freebsd-hackers@freebsd.org Subject: porting multithreaded app from linux to FreeBSD Message-ID: <20020206143846.Q17649@juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Folks, Are there any gotchas about porting over from Linux a multi-threaded application? FreeBSD version that I am using is 4.2. Thanks. Umesh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 14:46:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by hub.freebsd.org (Postfix) with ESMTP id 3E34437B421 for ; Wed, 6 Feb 2002 14:46:27 -0800 (PST) Received: from k7.mavetju.org (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id 1D3B52B74A; Wed, 6 Feb 2002 23:46:24 +0100 (CET) Received: by k7.mavetju.org (Postfix, from userid 1001) id D5D8AEF; Thu, 7 Feb 2002 09:46:15 +1100 (EST) Date: Thu, 7 Feb 2002 09:46:15 +1100 From: Edwin Groothuis To: Umesh Krishnaswamy Cc: freebsd-hackers@freebsd.org Subject: Re: porting multithreaded app from linux to FreeBSD Message-ID: <20020207094615.A1598@k7.mavetju.org> Mail-Followup-To: Edwin Groothuis , Umesh Krishnaswamy , freebsd-hackers@freebsd.org References: <20020206143846.Q17649@juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020206143846.Q17649@juniper.net>; from umesh@juniper.net on Wed, Feb 06, 2002 at 02:38:47PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 06, 2002 at 02:38:47PM -0800, Umesh Krishnaswamy wrote: > Are there any gotchas about porting over from Linux a multi-threaded > application? FreeBSD version that I am using is 4.2. Anything which uses libpcap doesn't work in a multithreaded environment until version 4.5. Edwin -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions: ------------------+ http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 15:20:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from valen.gwi.net (valen.gwi.net [207.5.128.33]) by hub.freebsd.org (Postfix) with ESMTP id E8BFA37B426 for ; Wed, 6 Feb 2002 15:20:09 -0800 (PST) Received: from ABERRATION (dieselgeek.outofspec.com [207.5.188.11]) by valen.gwi.net (8.11.6/8.11.6) with SMTP id g16NK9r07874 for ; Wed, 6 Feb 2002 18:20:09 -0500 (EST) Message-ID: <004f01c1af64$cf5eee20$fa01a8c0@ABERRATION> Reply-To: "Predius" From: "Predius" To: Subject: Fw: Diskless USB Issue Date: Wed, 6 Feb 2002 18:20:04 -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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Looks like I stumped freebsd-questions, anyone else care to take a whack at this? Joshua Coombs ----- Original Message ----- From: "Predius" To: Sent: Tuesday, February 05, 2002 11:47 PM Subject: Diskless USB Issue > I'm working on setting up a Compaq iPaq for netbooting, and have run into a > small problem that's got me stumped. > > My Setup: > > Parasite (iPaq): 32MB Compact Flash card, formated as a FAT fs, loads DOS, > and uses dosboot.com (from netbsd) to load a freebsd kernel on the > filesystem. > > The kernel is built for bootp, and specifically has bootp wired to aue0. > When booting, all is good, usb is detected, aue0 is detected, and it > attempts to do bootp. Problem is at no point in time does the unit detect a > link, causing dhcp to just repeatedly timeout. > > I've observed this system when netbooting via a NetBSD kernel, and see > similar behavior, the link isn't autodetected till it actually starts > sending bootp requests. (It's a Linksys USB100TX Ver B1 btw). Is there any > way to hardwire a media setting in the kernel to get around this? > > And for those rolling their eyes at this arrangement, it's actually working > pretty good under netbsd right now, which is what I use to transfer content > to the CF media as I'm too lazy to get a usb cf reader for my desktop. > > Considering USB is only going to get more and more popular, might as well > start playing with it, right? : ) > > Joshua Coombs > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 15:39:57 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id D0B5B37B420 for ; Wed, 6 Feb 2002 15:39:53 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g16Ndlv34672; Wed, 6 Feb 2002 17:39:47 -0600 (CST) (envelope-from dan) Date: Wed, 6 Feb 2002 17:39:47 -0600 From: Dan Nelson To: Predius Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Diskless USB Issue Message-ID: <20020206233947.GN1066@dan.emsphone.com> References: <004f01c1af64$cf5eee20$fa01a8c0@ABERRATION> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004f01c1af64$cf5eee20$fa01a8c0@ABERRATION> User-Agent: Mutt/1.3.27i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Feb 06), Predius said: > > Parasite (iPaq): 32MB Compact Flash card, formated as a FAT fs, loads DOS, > > and uses dosboot.com (from netbsd) to load a freebsd kernel on the > > filesystem. > > Looks like I stumped freebsd-questions, anyone else care to take a whack at > this? I think you're lucky it even boots, since I don't think booting a kernel after DOS has has its hand on the system has been supported since 2.2.something. If that CF card really must be a FAT FS, I believe both the Grub bootloader and /boot/loader can run on FAT, so you should be able to boot straight into FreeBSD without using DOS (have grub load /boot/loader which in turn loads the kernel). -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 15:39:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 4C99637B41C for ; Wed, 6 Feb 2002 15:39:40 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g16Nddh12269; Thu, 7 Feb 2002 00:39:39 +0100 Received: (nullmailer pid 97465 invoked by uid 1000); Wed, 06 Feb 2002 23:39:36 -0000 Date: Thu, 7 Feb 2002 00:39:36 +0100 From: Mark Santcroos To: hackers@freebsd.org Cc: Julian Elischer Subject: [PATCH] nmdm fixes Message-ID: <20020207003936.K16264@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Using the nmdm driver for serial console debugging in vmware I was really surprised to notice that the thing actually doesn't work at all (anymore). As far as I could find out it only supported one pair. Also after a close, when I would do a "ls -al /dev/nmdm*", I would get a kernel panic. I rewrote nmdm.c to the basic point that it works fine for me. One can now create multiple pairs and I haven't got any panics or problems whatsoever. I also took the liberty to remove the ancient K&R requirements at the same time now there is a large code change anyway. Please review the patch at: http://www.ripe.net/home/mark/files/nmdm.diff I would appreciate any feedback ranging from: 'hey, you should do it like this!' to 'committed!'. I only used/tested this on -CURRENT btw. Thanks to Julian for writing the driver initially. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 17: 7:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 0C9D537B400 for ; Wed, 6 Feb 2002 17:07:17 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020207000015.CAIO3578.rwcrmhc52.attbi.com@InterJet.elischer.org>; Thu, 7 Feb 2002 00:00:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA93117; Wed, 6 Feb 2002 15:57:53 -0800 (PST) Date: Wed, 6 Feb 2002 15:57:53 -0800 (PST) From: Julian Elischer To: Umesh Krishnaswamy Cc: freebsd-hackers@freebsd.org Subject: Re: porting multithreaded app from linux to FreeBSD In-Reply-To: <20020206143846.Q17649@juniper.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG use the linuxthreads port.. that will give you exact linux-threads compatibility.. On Wed, 6 Feb 2002, Umesh Krishnaswamy wrote: > Hi Folks, > > Are there any gotchas about porting over from Linux a multi-threaded > application? FreeBSD version that I am using is 4.2. > > Thanks. > Umesh. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 17:32:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 8D43A37B416 for ; Wed, 6 Feb 2002 17:32:17 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id ED8D41CCF; Wed, 6 Feb 2002 18:32:16 -0700 (MST) Received: from axcsbh1.cos.agilent.com (axcsbh1.cos.agilent.com [130.29.152.143]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 8417B166; Wed, 6 Feb 2002 18:32:16 -0700 (MST) Received: by axcsbh1.cos.agilent.com with Internet Mail Service (5.5.2653.19) id ; Wed, 6 Feb 2002 18:32:16 -0700 Message-ID: <0D9185CE635BD511ACA50090277A6FCF1359BF@axcs18.cos.agilent.com> From: "DOROVSKOY,IGOR (A-Portsmouth,ex1)" To: 'John Polstra' , hackers@freebsd.org Cc: phk@critter.freebsd.dk Subject: RE: A question about timecounters Date: Wed, 6 Feb 2002 18:32:15 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >be open source. It's a simulated web client and web server, running >inside the kernel. It's good for load-testing and performance-testing >many kinds of network devices. With two 1-GHz PIII boxes (one acting >as the client and the other acting as the server) it can generate >around 50000 (actually I think it's more than that) full web sessions >per second. Also, you can dial in any rate you want, and it will >generate that rate very precisely. Lots of fun! ... yea yea :-) It reminds me an 2 years old feature in our product (was QARobot originally, now it's a part of RouterTester) where we had an Session Storm module generates HTTP traffic with kernel support too. I did remember how it was killing any httpd server in secs even from one slave with possible up to 20 with thousands ssm's running on each cpu. Unfortunately it's obsolete now (qa and development, but code and qbol language support still be inside new product for free :). I may try to find some performance data tomorrow if it's interesting for you off cause... Igor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 17:52: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 0892F37B41B; Wed, 6 Feb 2002 17:51:57 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g171psD88109; Wed, 6 Feb 2002 20:51:55 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 6 Feb 2002 20:51:52 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Bi-Monthly Development Status Report (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Reminder: status reports are due on Friday. Please submit them in a timely manner so I can have the report ready in time for BSDCon. Thanks, (submission instructions below) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Mon, 4 Feb 2002 13:46:50 -0500 (EST) From: Robert Watson To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Request for submissions: FreeBSD Bi-Monthly Development Status Report This is a solicitation for submissions for the December 2001 - January 2002 FreeBSD Bi-Monthly Development Status Report. All submissions are due by February 8, 2002. Submissions should be made by filling out the template found at: http://www.FreeBSD.org/news/status/report-sample.xml Submissions must then be e-mailed to the following address: robert+freebsd.monthly@cyrus.watson.org For automatic processing. Reports must be submitted in the XML format described, or they will be silently dropped. Submissions made to other e-mail addresses will be ignored. Status reports should be submitted once per project, although project developers may choose to submit additional reports on specific sub-projects of substantial size. Status reports are typically one or two short paragraphs, but the text may be up to 20 lines in length. Submissions are welcome on a variety of topics relating to FreeBSD, including development, documentation, advocacy, and development processes. Prior status reports may be viewed at: http://www.FreeBSD.org/news/status/ Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 18: 4:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 2D9C737B404 for ; Wed, 6 Feb 2002 18:04:10 -0800 (PST) Received: from pool0137.cvx22-bradley.dialup.earthlink.net ([209.179.198.137] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Ydux-0006g5-00; Wed, 06 Feb 2002 18:04:07 -0800 Message-ID: <3C61E092.5E5A7B45@mindspring.com> Date: Wed, 06 Feb 2002 18:04:02 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Charles Peterman Cc: freebsd-hackers@freebsd.org Subject: Re: Binding a Process to a specific CPU References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What you are asking for is called "process group negaffinity"; a cheesy way to achieve this is to lock processes to a particular processor instead (forced affinity), which will make sure they don't run on the same processor. THis is a cheesy way of doing it because with two processes on a four CPU system, you won't necessarily get the least loaded CPU. To get forced affinity rather than true negaffinity, use Alfred Perlsteins scheduler patches, or make your own. -- Terry Charles Peterman wrote: > > I am currently playing with a dual CPU machine. > With 4.5, is there a way to guarantee that > two specific processes never end up on the same > processor? > > Or does this question betray my fundamental > ignorance of how processes are allocated on an > SMP based machine? > > Thanks much, > > Charles Peterman > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 18:41:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 03C8637B41E for ; Wed, 6 Feb 2002 18:41:50 -0800 (PST) Received: from pool0137.cvx22-bradley.dialup.earthlink.net ([209.179.198.137] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YeVP-0005da-00; Wed, 06 Feb 2002 18:41:47 -0800 Message-ID: <3C61E966.338CA0@mindspring.com> Date: Wed, 06 Feb 2002 18:41:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Umesh Krishnaswamy Cc: freebsd-hackers@freebsd.org Subject: Re: porting multithreaded app from linux to FreeBSD References: <20020206143846.Q17649@juniper.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Umesh Krishnaswamy wrote: > Are there any gotchas about porting over from Linux a multi-threaded > application? FreeBSD version that I am using is 4.2. FreeBSD 4.2 uses a user space threading model. Linux threads are supported through the use of a GPL'ed kernel module and library, so you will need to consider licensing issues if you go that route. If you just use pthreads, Linux programmers often make some assumptions about thread scheduling which are not correct in the case of a user space threads scheduler, even though that is perfectly legal. For example, the Java GIF renderer in Netscape was not thread reentrant, because it assumed that the active thread would be restarted, instead of another thread, should the entire process be involuntarily context switched, and then rescheduled to run. This led to problems with Java applications causing Netscape to crash on FreeBSD and Macintosh, when they worked fine on Windows, Linux, and other OSs using the Windows assumptions. Another program that is commonly written is an infinite "printf" loop, with another infinite loop with a "sleep" for one secong in a seperate thread. This assumes that the preemption of one thread vs. another will occur at the kernel quantum distribution level, and thus the resulting program will crank out a bunch of the firt printf's (e.g. "x"), and the second will crank out its printf once a second (e.g. "o"). This fails, because the first thread is never context switched away by the user thread scheduler, which does not do quantum distribution (round-robin or otherwise). This is all beside the fact that a buzz loop is incredibly bad programming practice under any circumstances, because it will take all available CPU, and drop in priority as a result of being such a pig. If you don't make scheduling assumptions, and you don't write infinite loops and expect context switches, you should not have problems. If you want more examples, check the mailing list archives for problem reports involving threads, or the PR database, including resolved problem reports about threads, where the resolution was "programmer error" or otherwise "won't fix". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 18:50:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hall.mail.mindspring.net (hall.mail.mindspring.net [207.69.200.60]) by hub.freebsd.org (Postfix) with ESMTP id A2BF537B41F for ; Wed, 6 Feb 2002 18:50:05 -0800 (PST) Received: from user-37kaot9.dialup.mindspring.com ([207.69.99.169] helo=mr-p.protolan) by hall.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16YedH-00026d-00; Wed, 06 Feb 2002 21:49:55 -0500 Date: Wed, 6 Feb 2002 21:54:17 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <199529679048.20020206215417@mindspring.com> To: "Rogier R. Mulhuijzen" Cc: Doug White , freebsd-hackers@FreeBSD.ORG Subject: Re[4]: natd UDP errors with PPP demand dial In-Reply-To: <165500266655.20020206134404@mindspring.com> References: <20020204114052.Q61624-100000@resnet.uoregon.edu> <20020204114052.Q61624-100000@resnet.uoregon.edu> <5.1.0.14.0.20020206020222.01c18290@mail.drwilco.net> <165500266655.20020206134404@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG M> Thank you for your response, Rogier. RRM>> 1) Have you told natd the interface is dynamic and might change IPs? M> Yes, of course. RRM>> 2) If you're using ppp, why even bother with natd? The NAT in ppp uses the RRM>> exact same libalias and gives you less headaches with ipfw because the RRM>> translation on incoming packets is done before they hit ipfw, and outgoing RRM>> after ipfw let them go. I can tell you this helps a lot when trying to use RRM>> dynamic rules. M> That's a great idea! I had not considered it until now. I would M> just need to work the anti-spoofing and private net rules into the ppp nat process M> somehow. I guess, I would have to use ppp filtering just for those M> rules. If I can do that, your way does seem to be a good place to M> start in resolving my error messages. I think having ppp do the NAT for me is not going to work. The ppp manual I have here says that ppp does incoming filtering after it does incoming NAT. I don't see how one can have private nets, spoofing, Reserved-1 and such filtering that has to happen on the outside interface before NAT. Plus, I think I will run out of "in" filter rule numbers. I think I have to stick with the conventional setup, and go back to trying to answer my original questions: 1. Why is the machine trying to send packets to its own previous IP? 2. How do I stop that? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 19:23:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 854EB37B405 for ; Wed, 6 Feb 2002 19:23:20 -0800 (PST) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.11.6/8.11.6) with ESMTP id g173NJv37963 for ; Wed, 6 Feb 2002 20:23:20 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Wed, 06 Feb 2002 20:23:20 -0700 Subject: Re: Re[4]: natd UDP errors with PPP demand dial From: Ian To: freebsd-hackers Message-ID: In-Reply-To: <199529679048.20020206215417@mindspring.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I think I have to stick with the conventional setup, and go back to > trying to answer my original questions: > > 1. Why is the machine trying to send packets to its own previous IP? > 2. How do I stop that? Well, for some brute-force debugging, maybe you can get some extra clues by manually running natd -v in a console rather than running it as a daemon. The -v output shows each packet being aliased, and also shows the activity on the routing socket that it's monitoring for the -dynamic stuff. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 20:50:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id A3AFF37B405 for ; Wed, 6 Feb 2002 20:49:27 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g174uvh34503 for ; Thu, 7 Feb 2002 09:56:57 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g174mqZ13690 for ; Thu, 7 Feb 2002 09:48:52 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g174kD706308 for ; Thu, 7 Feb 2002 09:46:13 +0500 (YEKT) Message-ID: <004501c1af93$79b0fca0$02010101@wall> From: "Dmitry A. Bondareff" To: Subject: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Thu, 7 Feb 2002 09:54:07 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0042_01C1AFBD.627180D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0042_01C1AFBD.627180D0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Hi! I have FreeBSD 4.0: # uname -a FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT = 2001 root@xxx:/usr/src/sys/compile/xxx i386 Yesterday I've tried to update it teel 4.5-RELEASE. Here is my cvsupfile: # more /etc/cvsupfile *default host=3Dcvsup.FreeBSD.org *default base=3D/usr *default prefix=3D/usr *default release=3Dcvs *default delete compress use-rel-suffix *default tag=3DRELENG_4_5 src-all # cvsup -g -L 2 /etc/cvsupfile Sync of the source was success. # cd /usr/src # make buildworld ............................ ............................ patch.o: In function `main': patch.o(.text+0xc8): warning: mktemp() possibly used unsafely; consider = using mkstemp() /usr/src/gnu/usr.bin/ptx/doc/ptx.texinfo:116: warning: `.' or `,' must = follow cross reference, n ot f. /usr/src/gnu/usr.bin/ptx/doc/ptx.texinfo:256: warning: `.' or `,' must = follow cross reference, n ot f. /usr/src/gnu/usr.bin/rcs/lib/rcsutil.c: In function `setup_catchsig': /usr/src/gnu/usr.bin/rcs/lib/rcsutil.c:634: warning: assignment from = incompatible pointer type /usr/src/gnu/usr.bin/tar/prepend_args.c: In function = `prepend_default_options': /usr/src/gnu/usr.bin/tar/prepend_args.c:74: warning: initialization = makes pointer from integer w ithout a cast texindex.o: In function `main': texindex.o(.text+0xbd): warning: mktemp() possibly used unsafely; = consider using mkstemp() ELF binary type not known. Use "brandelf" to brand it. Abort trap What's wrong ?? P.S. Day before it I was upgrade from 4.4-RELEASE to 4.5-RELEASE easy. Regards, Dmitry A. Bondareff ------=_NextPart_000_0042_01C1AFBD.627180D0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
Hi!
 
I have FreeBSD 4.0:
# uname -a
FreeBSD xxx 4.0-RELEASE = FreeBSD=20 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT 2001
  root@xxx:/u= sr/src/sys/compile/xxx =20 i386
 
Yesterday I've tried to update it teel=20 4.5-RELEASE.
 
Here is my cvsupfile:
# more /etc/cvsupfile
*default =20 host=3Dcvsup.FreeBSD.org
*default  base=3D/usr
*default  = prefix=3D/usr
*default  release=3Dcvs
*default  delete = compress=20 use-rel-suffix
*default tag=3DRELENG_4_5
 
src-all
 
# cvsup -g -L 2 = /etc/cvsupfile
Sync of the source was = success.
 
# cd /usr/src
# make buildworld
 
............................
............................
 
patch.o: In function = `main':
patch.o(.text+0xc8):=20 warning: mktemp() possibly used unsafely; consider using=20 mkstemp()
/usr/src/gnu/usr.bin/ptx/doc/ptx.texinfo:116: warning: `.' = or `,'=20 must follow cross reference, n
ot=20 f.
/usr/src/gnu/usr.bin/ptx/doc/ptx.texinfo:256: warning: `.' or `,' = must=20 follow cross reference, n
ot = f.
/usr/src/gnu/usr.bin/rcs/lib/rcsutil.c: In=20 function = `setup_catchsig':
/usr/src/gnu/usr.bin/rcs/lib/rcsutil.c:634:=20 warning: assignment from incompatible pointer=20 type
/usr/src/gnu/usr.bin/tar/prepend_args.c: In function=20 `prepend_default_options':
/usr/src/gnu/usr.bin/tar/prepend_args.c:74:= =20 warning: initialization makes pointer from integer w
ithout a=20 cast
texindex.o: In function `main':
texindex.o(.text+0xbd): = warning:=20 mktemp() possibly used unsafely; consider using mkstemp()
ELF binary = type not=20 known.  Use "brandelf" to brand it.
Abort trap
 
What's wrong ??
 
P.S. Day before it I was upgrade from = 4.4-RELEASE to=20 4.5-RELEASE easy.
 
Regards,
Dmitry A. = Bondareff
------=_NextPart_000_0042_01C1AFBD.627180D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 21: 0:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from valen.gwi.net (valen.gwi.net [207.5.128.33]) by hub.freebsd.org (Postfix) with ESMTP id 36B7837B423 for ; Wed, 6 Feb 2002 21:00:49 -0800 (PST) Received: from ABERRATION (dieselgeek.outofspec.com [207.5.188.11]) by valen.gwi.net (8.11.6/8.11.6) with SMTP id g1750gr18214; Thu, 7 Feb 2002 00:00:42 -0500 (EST) Message-ID: <000201c1af94$63125150$fa01a8c0@ABERRATION> Reply-To: "Predius" From: "Predius" To: "Dan Nelson" Cc: References: <004f01c1af64$cf5eee20$fa01a8c0@ABERRATION> <20020206233947.GN1066@dan.emsphone.com> Subject: Re: Diskless USB Issue Date: Wed, 6 Feb 2002 23:53:00 -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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've played around with this a bit, and so far on my other test systems, as long as I don't do anything beyond basic booting, ie load a mem manager, device drivers, etc, it seems to work pretty well. Near as I can tell the problem I'm running up against is in the initilization of the mii section of my nic. As a test I tried an older Kawasaki based USB nic, which only does 10baseT, half duplex. It's detected, gets link, and attempts to netboot. Problem is the kawasaki chipset is flakier than all hell, so it randomly starts timing out durring the process. Best so far is bootp's completed, nfs has mounted root, and it's begun to init before the nic crapped out. I've looked at the aue driver for FreeBSD, and NetBSD, hoping I could spot a difference, but unfortunatly the code is way over my head. I'm pretty sure if I can mangle it either via driver butchery or a kernel option to hardwire it for one media setting I can get it to work, I just don't have the expertise to do so myself. Joshua Coombs > I think you're lucky it even boots, since I don't think booting a kernel > after DOS has has its hand on the system has been supported since > 2.2.something. > > If that CF card really must be a FAT FS, I believe both the Grub > bootloader and /boot/loader can run on FAT, so you should be able to > boot straight into FreeBSD without using DOS (have grub load > /boot/loader which in turn loads the kernel). > > -- > Dan Nelson > dnelson@allantgroup.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 21:11: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id C8DEF37B41A for ; Wed, 6 Feb 2002 21:11:01 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id QAA11588; Thu, 7 Feb 2002 16:10:59 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KDZYLXD2VKVFN0J2@cim.alcatel.com.au>; Thu, 7 Feb 2002 16:10:49 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g175Au303666; Thu, 07 Feb 2002 16:10:56 +1100 Content-return: prohibited Date: Thu, 07 Feb 2002 16:10:56 +1100 From: Peter Jeremy Subject: Re: problem w/ dlopen(); bug or feature? To: John Polstra Cc: hackers@freebsd.org Message-id: <20020207161056.A3626@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 1 Feb 2002 20:24:33 -0800 (PST), John Polstra wrote: >If you're talking about efficiency, it doesn't matter very much. It's >a rare program that loads more than, say, 20 shared libraries. We have an application toolchain which basically puts each object into its own shared library. One application wound up with 209 shared libraries. I personally think that this is taking "modularity" past the extreme, but it does work. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 23:46:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bilbo.in.mat.cc (bilbo.in.mat.cc [212.43.217.121]) by hub.freebsd.org (Postfix) with ESMTP id 1FE9B37B416 for ; Wed, 6 Feb 2002 23:46:15 -0800 (PST) Received: from bilbo.org (localhost [127.0.0.1]) by bilbo.in.mat.cc (Postfix) with ESMTP id 1C5A671055 for ; Thu, 7 Feb 2002 08:46:08 +0100 (CET) Received: from club-internet.fr (sauron.in.mat.cc [212.43.217.122]) by bilbo.in.mat.cc (Postfix) with ESMTP id ABA5471055 for ; Thu, 7 Feb 2002 08:46:05 +0100 (CET) Message-ID: <3C6230BD.C3D6CD2E@club-internet.fr> Date: Thu, 07 Feb 2002 08:46:05 +0100 From: Mathieu Arnold Organization: http://www.absolight.fr/ X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: Can someone fix releng4.freebsd.org to name snapshots right ? References: <20020206121458.N45642@seven.alameda.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ulf Zimmermann wrote: > > drwxr-xr-x 20 root wheel 1024 Jan 30 17:13 4.4-20020130-STABLE > drwxr-xr-x 20 root wheel 1024 Jan 31 18:06 4.4-20020131-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 1 16:59 4.4-20020201-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 2 16:47 4.4-20020202-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 3 16:48 4.4-20020203-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 4 17:04 4.4-20020204-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 5 17:09 4.4-20020205-STABLE > drwxr-xr-x 20 root wheel 1024 Feb 6 16:42 4.4-20020206-STABLE > > Shouldn't these directories be named 4.5-xxxxx-STABLE by now ? shouldn't they be named 4-xxxxx-STABLE ? -- Mathieu Arnold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Feb 6 23:59:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail3.rambler.ru (mail3.rambler.ru [217.73.192.32]) by hub.freebsd.org (Postfix) with SMTP id 7A36837B400 for ; Wed, 6 Feb 2002 23:59:32 -0800 (PST) Received: from 216.230.139.29 by rambler.ru with SMTP id AA25025 for hackers@freebsd.org; Thu, 7 Feb 2002 10:55:09 +0300 (MSK) From: äÏÂÒÏÖÅÌÁÔÅÌØ To: "" <> Subject: ËÁË ÌÀÄÉ ÚÁÒÁÂÁÔÙ×ÁÀÔ × ÉÎÔÅÒÎÅÔÅ??? Organization: ÎÅÔÕ ÔÁËÏÊ! :) Reply-To: S-AS@yandex.ru X-Mailer: X-Mailer Mime-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Date: Thu, 7 Feb 2002 10:57:21 +0300 Message-Id: <3C6232DD.AA25025@mail3.rambler.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG äÏÂÒÏÇÏ ×ÒÅÍÅÎÉ ÓÕÔÏË! åÓÌÉ ÷ÁÍ ÉÎÔÅÒÅÓÎÏ, ËÁË ÌÀÄÉ ÚÁÒÁÂÁÔÙ×ÁÀÔ ÄÅÎØÇÉ × ÓÅÔÉ ÉÎÔÅÒÎÅÔ É ×Ù ÓÁÍÉ ÈÏÔÉÔÅ ÉÈÚÁÒÁÂÁÔÙ×ÁÔØ... ôÏ $5 + ÎÅÍÎÏÇÏ ÕÓÅÒÄÉÑ = ÐÏÌÕÞÁÊÔÅ ÄÅÎØÇÉ ×ÓÀ ÖÉÚÎØ ðÏÄÒÏÂÎÏÓÔÉ: http://5dolors.non.ru ÉÌÉ http://5dolors.maza.ru/ úÁÒÅÇÉÓÔÒÉÒÏ×Á×ÛÉÓØ, ×Ù ÐÏÌÕÞÉÔÅ ÂÅÓÐÌÁÔÎÕÀ ËÏÎÓÕÌØÔÁÃÉÀ É ÎÁÂÏÒ ÐÒÏÇÒÁÍÍ ÎÅÏÂÈÏÄÉÍÙÈ ÄÌÑ ÒÁÂÏÔÙ!!! öÅÌÁÀ ÕÄÁÞÉ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 0:39:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 0B2A037B41B for ; Thu, 7 Feb 2002 00:39:07 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g178cGB22353; Thu, 7 Feb 2002 10:38:16 +0200 (EET) (envelope-from ru) Date: Thu, 7 Feb 2002 10:38:16 +0200 From: Ruslan Ermilov To: "Dmitry A. Bondareff" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Message-ID: <20020207103816.A18883@sunbay.com> References: <004501c1af93$79b0fca0$02010101@wall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > Hi! > > I have FreeBSD 4.0: > # uname -a > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT 2001 > root@xxx:/usr/src/sys/compile/xxx i386 > > Yesterday I've tried to update it teel 4.5-RELEASE. > We don't (yet) support upgrades from 4.0. I plan on making it work in time for 4.6-RELEASE. Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 0:55:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 46FEB37B425; Thu, 7 Feb 2002 00:55:14 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g1792gh43162; Thu, 7 Feb 2002 14:02:42 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g178sdA29343; Thu, 7 Feb 2002 13:54:39 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g178px101644; Thu, 7 Feb 2002 13:51:59 +0500 (YEKT) Message-ID: <039201c1afb5$d0ec1a00$02010101@wall> From: "Dmitry A. Bondareff" To: "Ruslan Ermilov" Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Thu, 7 Feb 2002 13:59:56 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok! And what's you can recommend me ? ----- Original Message ----- From: "Ruslan Ermilov" To: "Dmitry A. Bondareff" Cc: Sent: Thursday, February 07, 2002 1:38 PM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > Hi! > > > > I have FreeBSD 4.0: > > # uname -a > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT 2001 > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > We don't (yet) support upgrades from 4.0. I plan on making it work > in time for 4.6-RELEASE. > > > Cheers, > -- > Ruslan Ermilov Sysadmin and DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 0:58: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id DEFB637B417; Thu, 7 Feb 2002 00:57:54 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g1795Qh43257; Thu, 7 Feb 2002 14:05:26 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g178vNm29587; Thu, 7 Feb 2002 13:57:23 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g178sh101663; Thu, 7 Feb 2002 13:54:43 +0500 (YEKT) Message-ID: <03ab01c1afb6$32d086c0$02010101@wall> From: "Dmitry A. Bondareff" To: "Ruslan Ermilov" Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Thu, 7 Feb 2002 14:02:40 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG How to minimize traffic for upgrading remote host ? ----- Original Message ----- From: "Ruslan Ermilov" To: "Dmitry A. Bondareff" Cc: Sent: Thursday, February 07, 2002 1:38 PM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > Hi! > > > > I have FreeBSD 4.0: > > # uname -a > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT 2001 > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > We don't (yet) support upgrades from 4.0. I plan on making it work > in time for 4.6-RELEASE. > > > Cheers, > -- > Ruslan Ermilov Sysadmin and DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 1:11:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 8E2E437B41A; Thu, 7 Feb 2002 01:11:37 -0800 (PST) Received: from pool0079.cvx22-bradley.dialup.earthlink.net ([209.179.198.79] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16YkaP-0002we-00; Thu, 07 Feb 2002 01:11:21 -0800 Message-ID: <3C6244B2.EF135CC7@mindspring.com> Date: Thu, 07 Feb 2002 01:11:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Dmitry A. Bondareff" Cc: Ruslan Ermilov , freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <03ab01c1afb6$32d086c0$02010101@wall> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Dmitry A. Bondareff" wrote: > > How to minimize traffic for upgrading remote host ? The best upgrade process I have come up with so far for remote hosts (or rach mount systems withoout CDROM drives in them) is to: 1) Create a new directory on the CDROM before you burn it called "upgrade". 2) Put the CDROM copy of /stand/sysinstall in that directory as "sysinstall". This is a lot harder than it looks. 3) Put copies of the /dev/MAKEDEV and /dev/MAKEDEV.local scripts in the directory, too (ignore this step for 5.x or other mandatory use of devfs). Then: A) Mount the CDROM on a system and export it via NFS. B) NFS mount the exported CDROM onto the target system. C) Run "sysinstall" off the mounted CDROM (this only works because you manually copied it into the magic directory). D) Do the upgrade; tell it to use "local media", and then point it to the NFS mounted directory. E) Manually copy the MAKEDEV and MAKEDEV.local to the target system, prior to the "reboot". F) disklabel -B to install the new bootblocks (if any); this is reallly important if you have a FreeBSD that was in flux for the switchover debacle. G) Install the source package to overwrite /usr/src, if you care. Note that this is an overwrite, so if you have local changes, move the directory out of the way, or back them up. H) cd /dev; sh MAKEDEV all Other than the /etc/pam.conf crap because of the gratuitous ssh changes, where you might have to manually add lines to it so that you can ssh back in, this pretty much covers the upgrade process. This should probably be automated as part of sysinstall. I have no idea why doing it without booting to the new version doesn't do the MAKEDEV stuff correctly. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 2:31:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.rambler.ru (mail4.rambler.ru [217.73.192.33]) by hub.freebsd.org (Postfix) with SMTP id 66ACE37B425 for ; Thu, 7 Feb 2002 02:31:32 -0800 (PST) Received: from 216.5.73.30 by rambler.ru with SMTP id AA04269 for freebsd-hackers@freebsd.org; Thu, 7 Feb 2002 10:52:46 +0300 (MSK) From: äÏÂÒÏÖÅÌÁÔÅÌØ To: "" <> Subject: ËÁË ÌÀÄÉ ÚÁÒÁÂÁÔÙ×ÁÀÔ × ÉÎÔÅÒÎÅÔÅ??? Organization: ÎÅÔÕ ÔÁËÏÊ! :) Reply-To: S-AS@yandex.ru X-Mailer: X-Mailer Mime-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Date: Thu, 7 Feb 2002 10:55:56 +0300 Message-Id: <3C62324E.AA04269@mail4.rambler.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG äÏÂÒÏÇÏ ×ÒÅÍÅÎÉ ÓÕÔÏË! åÓÌÉ ÷ÁÍ ÉÎÔÅÒÅÓÎÏ, ËÁË ÌÀÄÉ ÚÁÒÁÂÁÔÙ×ÁÀÔ ÄÅÎØÇÉ × ÓÅÔÉ ÉÎÔÅÒÎÅÔ É ×Ù ÓÁÍÉ ÈÏÔÉÔÅ ÉÈÚÁÒÁÂÁÔÙ×ÁÔØ... ôÏ $5 + ÎÅÍÎÏÇÏ ÕÓÅÒÄÉÑ = ÐÏÌÕÞÁÊÔÅ ÄÅÎØÇÉ ×ÓÀ ÖÉÚÎØ ðÏÄÒÏÂÎÏÓÔÉ: http://5dolors.non.ru ÉÌÉ http://5dolors.maza.ru/ úÁÒÅÇÉÓÔÒÉÒÏ×Á×ÛÉÓØ, ×Ù ÐÏÌÕÞÉÔÅ ÂÅÓÐÌÁÔÎÕÀ ËÏÎÓÕÌØÔÁÃÉÀ É ÎÁÂÏÒ ÐÒÏÇÒÁÍÍ ÎÅÏÂÈÏÄÉÍÙÈ ÄÌÑ ÒÁÂÏÔÙ!!! öÅÌÁÀ ÕÄÁÞÉ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 2:43:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id D7C1037B41F; Thu, 7 Feb 2002 02:43:07 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g17Aoah47599; Thu, 7 Feb 2002 15:50:36 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g17AgXc07940; Thu, 7 Feb 2002 15:42:33 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g17Adr103295; Thu, 7 Feb 2002 15:39:53 +0500 (YEKT) Message-ID: <045e01c1afc4$e4172f20$02010101@wall> From: "Dmitry A. Bondareff" To: "Ruslan Ermilov" Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Thu, 7 Feb 2002 15:47:51 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I have another machine in Internet with 4.1-RELEASE. An I want upgrade to 4.5-RELEASE. Will upgrade work ? ----- Original Message ----- From: "Ruslan Ermilov" To: "Dmitry A. Bondareff" Cc: Sent: Thursday, February 07, 2002 1:38 PM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > Hi! > > > > I have FreeBSD 4.0: > > # uname -a > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT 2001 > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > We don't (yet) support upgrades from 4.0. I plan on making it work > in time for 4.6-RELEASE. > > > Cheers, > -- > Ruslan Ermilov Sysadmin and DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 2:54:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by hub.freebsd.org (Postfix) with ESMTP id BCABB37B41F; Thu, 7 Feb 2002 02:54:05 -0800 (PST) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id CAA27357; Thu, 7 Feb 2002 02:53:30 -0800 Message-ID: <3C625CA9.202@owt.com> Date: Thu, 07 Feb 2002 02:53:29 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: "Dmitry A. Bondareff" Cc: Ruslan Ermilov , freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <045e01c1afc4$e4172f20$02010101@wall> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dmitry A. Bondareff wrote: > Hi! > I have another machine in Internet with 4.1-RELEASE. > An I want upgrade to 4.5-RELEASE. > Will upgrade work ? I have a friend trying that on 2 or 3 machines right now. His make buildkernel is dying because of the ipfilter move from modules/ to contrib/ change. Kent > > ----- Original Message ----- > From: "Ruslan Ermilov" > To: "Dmitry A. Bondareff" > Cc: > Sent: Thursday, February 07, 2002 1:38 PM > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > >>On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: >> >>>Hi! >>> >>>I have FreeBSD 4.0: >>># uname -a >>>FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT >>> > 2001 > >>> root@xxx:/usr/src/sys/compile/xxx i386 >>> >>>Yesterday I've tried to update it teel 4.5-RELEASE. >>> >>> >>We don't (yet) support upgrades from 4.0. I plan on making it work >>in time for 4.6-RELEASE. >> >> >>Cheers, >>-- >>Ruslan Ermilov Sysadmin and DBA, >>ru@sunbay.com Sunbay Software AG, >>ru@FreeBSD.org FreeBSD committer, >>+380.652.512.251 Simferopol, Ukraine >> >>http://www.FreeBSD.org The Power To Serve >>http://www.oracle.com Enabling The Information Age >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-hackers" in the body of the message >> >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > . > > -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 3:32:45 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by hub.freebsd.org (Postfix) with ESMTP id A64CB37B42B for ; Thu, 7 Feb 2002 03:32:40 -0800 (PST) Received: from fwd06.sul.t-online.de by mailout09.sul.t-online.com with smtp id 16Ymn9-0005Pp-08; Thu, 07 Feb 2002 12:32:39 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.235.123.237]) by fmrl06.sul.t-online.com with esmtp id 16Ymn1-1xgxv6C; Thu, 7 Feb 2002 12:32:31 +0100 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.11.6/8.11.6) with ESMTP id g17BWkL52065; Thu, 7 Feb 2002 12:32:48 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200202071132.g17BWkL52065@peedub.jennejohn.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: hackers To: Peter Jeremy Cc: freebsd-hackers@freebsd.org Subject: Re: Patching a kernel Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 06 Feb 2002 07:37:13 +1100." <20020206073713.Z7444@gsmx07.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain Date: Thu, 07 Feb 2002 12:32:46 +0100 From: Gary Jennejohn X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Jeremy writes: > I'd like to patch a running kernel to disable an annoying non-rate-limited > message but gdb won't let me. (For various reasons, I don't want to have > to build a new kernel and reboot). > > aalp03# chflags noschg /kernel > aalp03# gdb -k /kernel /dev/mem > GNU gdb 4.18 > ... > IdlePTD 3457024 > initial pcb at 4d40000 > panic messages: > --- > --- > #0 0xc0159bf0 in mi_switch () > (kgdb) set write on > (kgdb) print {int}0xc01fffa4 = 0x00004eb8 > kvm_write:write failed > (kgdb) show write > Writing into executable and core files is on. > (kgdb) > > 0xc01fffa4 is in the kernel text area. > > This is 4.4-STABLE from mid-December running at securelevel -1. > > Is there any way around this? > RTFM :) You have to use the wcore option to turn on writing in kgdb mode. The ``show write'' command is totally unrelated to this and only shows what's set for _normal_ debugging. There's no way to tell from within gdb whether wcore was used or not. Unfortunately, the -w option is overloaded. Normally it means ``use a windowing system''. In FreeBSD it's an alias for wcore. --- Gary Jennejohn / garyj@jennejohn.org gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 3:37:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id F0EDB37B416 for ; Thu, 7 Feb 2002 03:37:36 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g17BawK49160; Thu, 7 Feb 2002 13:36:58 +0200 (EET) (envelope-from ru) Date: Thu, 7 Feb 2002 13:36:58 +0200 From: Ruslan Ermilov To: "Dmitry A. Bondareff" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Message-ID: <20020207133658.A49110@sunbay.com> References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <039201c1afb5$d0ec1a00$02010101@wall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <039201c1afb5$d0ec1a00$02010101@wall> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 01:59:56PM +0500, Dmitry A. Bondareff wrote: > Ok! > And what's you can recommend me ? > Wait until I fix it. > ----- Original Message ----- > From: "Ruslan Ermilov" > To: "Dmitry A. Bondareff" > Cc: > Sent: Thursday, February 07, 2002 1:38 PM > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > > Hi! > > > > > > I have FreeBSD 4.0: > > > # uname -a > > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT > 2001 > > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > > > We don't (yet) support upgrades from 4.0. I plan on making it work > > in time for 4.6-RELEASE. > > > > > > Cheers, > > -- > > Ruslan Ermilov Sysadmin and DBA, > > ru@sunbay.com Sunbay Software AG, > > ru@FreeBSD.org FreeBSD committer, > > +380.652.512.251 Simferopol, Ukraine > > > > http://www.FreeBSD.org The Power To Serve > > http://www.oracle.com Enabling The Information Age > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 3:41:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 9261637B417 for ; Thu, 7 Feb 2002 03:41:10 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g17BdkU49502; Thu, 7 Feb 2002 13:39:46 +0200 (EET) (envelope-from ru) Date: Thu, 7 Feb 2002 13:39:46 +0200 From: Ruslan Ermilov To: Kent Stewart Cc: "Dmitry A. Bondareff" , freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Message-ID: <20020207133946.B49110@sunbay.com> References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <045e01c1afc4$e4172f20$02010101@wall> <3C625CA9.202@owt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C625CA9.202@owt.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 02:53:29AM -0800, Kent Stewart wrote: > > > Dmitry A. Bondareff wrote: > > >Hi! > >I have another machine in Internet with 4.1-RELEASE. > >An I want upgrade to 4.5-RELEASE. > >Will upgrade work ? > > > I have a friend trying that on 2 or 3 machines right now. His make > buildkernel is dying because of the ipfilter move from modules/ to > contrib/ change. > I only test with the GENERIC kernels and pretty "standard" worlds. I ran 4.5-STABLE buildworld and buildkernel on a 4.1-RELEASE test box two hours ago; it should finish within an hour or so. > >----- Original Message ----- > >From: "Ruslan Ermilov" > >To: "Dmitry A. Bondareff" > >Cc: > >Sent: Thursday, February 07, 2002 1:38 PM > >Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > > > > >>On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > >> > >>>Hi! > >>> > >>>I have FreeBSD 4.0: > >>># uname -a > >>>FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT > >>> > >2001 > > > >>> root@xxx:/usr/src/sys/compile/xxx i386 > >>> > >>>Yesterday I've tried to update it teel 4.5-RELEASE. > >>> > >>> > >>We don't (yet) support upgrades from 4.0. I plan on making it work > >>in time for 4.6-RELEASE. -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 4: 6:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 2EF7D37B41F; Thu, 7 Feb 2002 04:06:11 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g17CDch51202; Thu, 7 Feb 2002 17:13:38 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g17C5ZS12079; Thu, 7 Feb 2002 17:05:35 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g17C2t103610; Thu, 7 Feb 2002 17:02:55 +0500 (YEKT) Message-ID: <04b401c1afd0$7e60dc60$02010101@wall> From: "Dmitry A. Bondareff" To: "Ruslan Ermilov" Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <039201c1afb5$d0ec1a00$02010101@wall> <20020207133658.A49110@sunbay.com> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Thu, 7 Feb 2002 17:10:55 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That's good! But how much time you need for it ? Regards, Dmitry. ----- Original Message ----- From: "Ruslan Ermilov" To: "Dmitry A. Bondareff" Cc: Sent: Thursday, February 07, 2002 4:36 PM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > On Thu, Feb 07, 2002 at 01:59:56PM +0500, Dmitry A. Bondareff wrote: > > Ok! > > And what's you can recommend me ? > > > Wait until I fix it. > > > ----- Original Message ----- > > From: "Ruslan Ermilov" > > To: "Dmitry A. Bondareff" > > Cc: > > Sent: Thursday, February 07, 2002 1:38 PM > > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > > > > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > > > Hi! > > > > > > > > I have FreeBSD 4.0: > > > > # uname -a > > > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 GMT > > 2001 > > > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > > > > > We don't (yet) support upgrades from 4.0. I plan on making it work > > > in time for 4.6-RELEASE. > > > > > > > > > Cheers, > > > -- > > > Ruslan Ermilov Sysadmin and DBA, > > > ru@sunbay.com Sunbay Software AG, > > > ru@FreeBSD.org FreeBSD committer, > > > +380.652.512.251 Simferopol, Ukraine > > > > > > http://www.FreeBSD.org The Power To Serve > > > http://www.oracle.com Enabling The Information Age > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > -- > Ruslan Ermilov Sysadmin and DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 4:17:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B2E2E37B429 for ; Thu, 7 Feb 2002 04:17:36 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g17CH5S55113; Thu, 7 Feb 2002 14:17:05 +0200 (EET) (envelope-from ru) Date: Thu, 7 Feb 2002 14:17:05 +0200 From: Ruslan Ermilov To: "Dmitry A. Bondareff" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Message-ID: <20020207141705.A53826@sunbay.com> References: <004501c1af93$79b0fca0$02010101@wall> <20020207103816.A18883@sunbay.com> <039201c1afb5$d0ec1a00$02010101@wall> <20020207133658.A49110@sunbay.com> <04b401c1afd0$7e60dc60$02010101@wall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <04b401c1afd0$7e60dc60$02010101@wall> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 05:10:55PM +0500, Dmitry A. Bondareff wrote: > That's good! > But how much time you need for it ? > If you like to pay me for this job, let's say a week or so. Otherwise, as my spare time allows. I've already started working on this. > ----- Original Message ----- > From: "Ruslan Ermilov" > To: "Dmitry A. Bondareff" > Cc: > Sent: Thursday, February 07, 2002 4:36 PM > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > On Thu, Feb 07, 2002 at 01:59:56PM +0500, Dmitry A. Bondareff wrote: > > > Ok! > > > And what's you can recommend me ? > > > > > Wait until I fix it. > > > > > ----- Original Message ----- > > > From: "Ruslan Ermilov" > > > To: "Dmitry A. Bondareff" > > > Cc: > > > Sent: Thursday, February 07, 2002 1:38 PM > > > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > > > > > > > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > > > > Hi! > > > > > > > > > > I have FreeBSD 4.0: > > > > > # uname -a > > > > > FreeBSD xxx 4.0-RELEASE FreeBSD 4.0-RELEASE #5: Wed Apr 11 16:06:03 > GMT > > > 2001 > > > > > root@xxx:/usr/src/sys/compile/xxx i386 > > > > > > > > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > > > > > > > > We don't (yet) support upgrades from 4.0. I plan on making it work > > > > in time for 4.6-RELEASE. -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 7:18: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 050E637B405 for ; Thu, 7 Feb 2002 07:17:59 -0800 (PST) Received: from user-37kaotf.dialup.mindspring.com ([207.69.99.175] helo=mr-p.protolan) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16YqIL-0007mR-00; Thu, 07 Feb 2002 10:17:05 -0500 Date: Thu, 7 Feb 2002 10:21:29 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <70574510802.20020207102129@mindspring.com> To: Ian Cc: freebsd-hackers Subject: Re[6]: natd UDP errors with PPP demand dial In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> >> I think I have to stick with the conventional setup, and go back to >> trying to answer my original questions: >> >> 1. Why is the machine trying to send packets to its own previous IP? >> 2. How do I stop that? I> Well, for some brute-force debugging, maybe you can get some extra clues by I> manually running natd -v in a console rather than running it as a daemon. I> The -v output shows each packet being aliased, and also shows the activity I> on the routing socket that it's monitoring for the -dynamic stuff. I> -- Ian Thanks, Ian. That's a good idea. When I did the above, I saw that natd enters some kind of a confused state after the IP change. I really don't see why it's doing that, or how to stop it. Is there someone, perhaps, from the natd development group that I should ask. What I did was just start from a link down state. Then I requested a connection for email from my workstation, waited for the link to disconnect again, and repeated the process a few times. The actors here are: my workstation 192.168.0.10 the firewall machine tun0 (depending on the ppp session) 207.69.102.20 207.69.100.116 207.69.100.110 207.69.100.52 Earthlink mail server 207.69.200.225 Earthlink DNS 207.69.188.185 207.69.188.186 Some web server said a couple of lines 63.210.68.198:80 Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 Above is where I think the end of one ppp session is. My workstation is finishing talking with the mail server. I think the next ppp session is dialed here somewhere. Routing message 0x2 received. Routing message 0xd received. Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Routing message 0x2 received. Routing message 0xd received. Routing message 0xc received. Interface address/MTU has probably changed. Routing message 0x1 received. Routing message 0xc received. Interface address/MTU has probably changed. Routing message 0x1 received. Routing message 0x1 received. Routing message 0x3 received. I see that the IP changed above and natd recognized that Here is where natd enters the cone of confusion. It starts relaying messages from the mail server to its previous IP. In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 Out [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to >>>>>>>> [TCP] 207.69.100.116:110 -> 207.69.102.20:3979 In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 Out [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to [TCP] 207.69.100.116:110 -> 207.69.102.20:3979 In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 Out [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to [TCP] 207.69.100.116:110 -> 207.69.102.20:3979 In [TCP] [TCP] 207.69.102.20:3979 -> 207.69.100.116:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Out [TCP] [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 In [TCP] [TCP] 207.69.102.20:3979 -> 207.69.100.116:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Out [TCP] [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 In [TCP] [TCP] 207.69.102.20:3979 -> 207.69.100.116:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Out [TCP] [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 aliased to [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 I don't understand at all what happens above. The machine seems to try to talk to the mail server for a while using its previous IP. I think the next ppp session dialup happens here. It seems the machine tries to send some DNS queries using its previous IP. Routing message 0x2 received. Routing message 0xd received. Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.185:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.185:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.185:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.185:53 Out [UDP] [UDP] 192.168.0.10:3980 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3980 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3981 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3981 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3981 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3981 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3981 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.116:3981 -> 207.69.188.186:53 Routing message 0x2 received. Routing message 0xd received. Routing message 0xc received. Interface address/MTU has probably changed. Routing message 0x1 received. Routing message 0xc received. Interface address/MTU has probably changed. Routing message 0x1 received. Routing message 0x1 received. Routing message 0x3 received. I think here is again where natd enters the serious cone of confusion and starts relaying responses from the DNS server to its previous IP. In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to >>>>>>>>> [UDP] 207.69.100.110:53 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:50535 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.185:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:50535 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3980 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3980 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3981 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3981 In [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 Out [UDP] [UDP] 207.69.188.186:53 -> 207.69.100.116:3981 aliased to [UDP] 207.69.100.110:53 -> 207.69.100.116:3981 I think somewhere here another ppp session was dialed. However, natd continues to send out some DNS queries using its previous IP until it recognizes that the IP changed a few lines down. In [TCP] [TCP] 63.210.68.198:80 -> 207.69.100.52:1040 aliased to [TCP] 63.210.68.198:80 -> 207.69.100.52:1040 Out [TCP] [TCP] 207.69.100.52:1040 -> 63.210.68.198:80 aliased to [TCP] 207.69.100.52:1040 -> 63.210.68.198:80 Routing message 0x2 received. Routing message 0xd received. Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.185:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.185:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.185:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.185:53 Out [UDP] [UDP] 192.168.0.10:3982 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3982 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3983 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3983 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3983 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3983 -> 207.69.188.186:53 Out [UDP] [UDP] 192.168.0.10:3983 -> 207.69.188.186:53 aliased to [UDP] 207.69.100.110:3983 -> 207.69.188.186:53 Routing message 0x2 received. Routing message 0xd received. Routing message 0xc received. Interface address/MTU has probably changed. Routing message 0x1 received. Routing message 0xc received Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 7:59: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail009.syd.optusnet.com.au (mail009.syd.optusnet.com.au [203.2.75.170]) by hub.freebsd.org (Postfix) with ESMTP id 69FD837B422; Thu, 7 Feb 2002 07:58:59 -0800 (PST) Received: from bsd (ocmax6-217.dialup.optusnet.com.au [198.142.39.217]) by mail009.syd.optusnet.com.au (8.11.1/8.11.1) with SMTP id g17FwvD32638; Fri, 8 Feb 2002 02:58:57 +1100 Date: Fri, 8 Feb 2002 02:59:00 +1100 From: Nero To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: new page cache for linux Message-Id: <20020208025900.4717cf72.neroz@dingoblue.net.au> X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just thought I'd bring your attention to the new "radix tree page cache" in use by linux - I dont know what freebsd do at the moment, but it looks like it will improve scalability (you guys might want to use the idea). Anyway, heres the link: http://lwn.net/2002/0207/kernel.php3 -- It's not reality or how you perceive things that's important, it's what you're taking for it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 9:51: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from moebius2.Space.Net (moebius2.Space.Net [195.30.1.100]) by hub.freebsd.org (Postfix) with SMTP id 5546937B416 for ; Thu, 7 Feb 2002 09:50:54 -0800 (PST) Received: (qmail 88832 invoked by uid 1013); 7 Feb 2002 17:50:52 -0000 Date: Thu, 7 Feb 2002 18:50:52 +0100 From: Markus Stumpf To: freebsd-hackers@freebsd.org Subject: dump(8) race conditions? Message-ID: <20020207185052.A87994@Space.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: SpaceNet AG, Muenchen, Germany X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F 1A C7 77 88 4A B6 70 DF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We use amanda and dump for backups. Some hosts have rather busy disks even during non prime time hours when backup is run. From time to time amanda reports dump(8) errors like the following: sendbackup: info end | DUMP: Date of this level 5 dump: Wed Feb 6 01:53:12 2002 | DUMP: Date of last level 4 dump: Mon Feb 4 02:31:40 2002 | DUMP: Dumping /dev/rda4s1e (/share/turing/disk07) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 2423080 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] | DUMP: 14.72% done, finished in 0:28 | DUMP: 33.78% done, finished in 0:19 | DUMP: 52.84% done, finished in 0:13 | DUMP: 71.65% done, finished in 0:07 ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921522]: count=3072 ? DUMP: DUMP: read error from /dev/rda4s1e: Invalid argument: [sector -410921522]: count=512 ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921532]: count=5120 ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -1001057530]: count=1024 [ ... ] First time we saw this we took down the machine to single user, unmounted the disk and fsck'd it. No errors where found and the next backups (even level 0) made it without errors. As we where still suspicious as to what might be the reason for this really sporadic error messages from different machines and different disks I look through the source of dump. If I do interpret the code correctly dump caches directory inode lists. Now, if during a dump and after caching the inode infos files get removed/shrunk dump has a "dirty" cache and tries to access blocks that are not/no longer allocated and the result are the above errors. Am I right with my interpretation or are this really hardware errors? Thanks, \Maex -- SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299 "The security, stability and reliability of a computer system is reciprocally proportional to the amount of vacuity between the ears of the admin" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 9:54: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 1AFA737B404 for ; Thu, 7 Feb 2002 09:54:06 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g17Hs2T06153; Thu, 7 Feb 2002 11:54:02 -0600 (CST) (envelope-from dan) Date: Thu, 7 Feb 2002 11:54:02 -0600 From: Dan Nelson To: Markus Stumpf Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dump(8) race conditions? Message-ID: <20020207175402.GA79258@dan.emsphone.com> References: <20020207185052.A87994@Space.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020207185052.A87994@Space.Net> User-Agent: Mutt/1.3.27i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Feb 07), Markus Stumpf said: > We use amanda and dump for backups. Some hosts have rather busy disks > even during non prime time hours when backup is run. > > >From time to time amanda reports dump(8) errors like the following: > > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921522]: count=3072 > ? DUMP: DUMP: read error from /dev/rda4s1e: Invalid argument: [sector -410921522]: count=512 > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921532]: count=5120 > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -1001057530]: count=1024 > [ ... ] Dump should ideally be run on an unmounted filesystem. The next best is to create a snapshot ( /usr/src/sys/ufs/ffs/README.snapshot ) and dump that. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 10: 9: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from moebius2.Space.Net (moebius2.Space.Net [195.30.1.100]) by hub.freebsd.org (Postfix) with SMTP id 0248137B41C for ; Thu, 7 Feb 2002 10:08:51 -0800 (PST) Received: (qmail 89784 invoked by uid 1013); 7 Feb 2002 18:08:49 -0000 Date: Thu, 7 Feb 2002 19:08:49 +0100 From: Markus Stumpf To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dump(8) race conditions? Message-ID: <20020207190849.B87994@Space.Net> References: <20020207185052.A87994@Space.Net> <20020207175402.GA79258@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020207175402.GA79258@dan.emsphone.com>; from dnelson@allantgroup.com on Thu, Feb 07, 2002 at 11:54:02AM -0600 Organization: SpaceNet AG, Muenchen, Germany X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F 1A C7 77 88 4A B6 70 DF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 11:54:02AM -0600, Dan Nelson wrote: > Dump should ideally be run on an unmounted filesystem. The next best > is to create a snapshot ( /usr/src/sys/ufs/ffs/README.snapshot ) and > dump that. True. But on systems that host e.g. mailservers or webservers its unacceptable to disrupt services tp umount and backup the system :/ $ uname -a FreeBSD 4.4-RELEASE $ more /usr/src/sys/ufs/ffs/README.snapshot /usr/src/sys/ufs/ffs/README.snapshot: No such file or directory :-))) Located it in stable, but the READNE says: 2) Run dump on the snapshot. You will get a dump that is consistent with the filesystem as of the timestamp of the snapshot. Note that I have not yet changed dump to set the dumpdates file correctly, so do not use this feature in production until that fix is made. :-(( Anyway, I have no problem with the errors per se, just wanted to know if they could result from the race conditions or if I have to better change the disks. \Maex -- SpaceNet AG | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research & Development | D-80807 Muenchen | Fax: +49 (89) 32356-299 "The security, stability and reliability of a computer system is reciprocally proportional to the amount of vacuity between the ears of the admin" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 10:21: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from thalia.fm.intel.com (fmfdns02.fm.intel.com [132.233.247.11]) by hub.freebsd.org (Postfix) with ESMTP id AA4D737B41B; Thu, 7 Feb 2002 10:20:57 -0800 (PST) Received: from fmsmsxvs041.fm.intel.com (fmsmsxv041-1.fm.intel.com [132.233.48.109]) by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.49 2002/01/25 02:16:58 root Exp $) with SMTP id SAA09758; Thu, 7 Feb 2002 18:20:57 GMT Received: from FMSMSX018.fm.intel.com ([132.233.42.197]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.1.16) with SMTP id M2002020710214701311 ; Thu, 07 Feb 2002 10:21:47 -0800 Received: by fmsmsx018.fm.intel.com with Internet Mail Service (5.5.2653.19) id <13HR8GPC>; Thu, 7 Feb 2002 10:20:57 -0800 Message-ID: From: "Frost, Stephen C" To: "'freebsd-questions@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Cc: "Frost, Stephen C" Subject: FreeBSD onto An Intel Saber 8-Proc Server Date: Thu, 7 Feb 2002 10:20:52 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG All - I am relatively new to the FreeBSD environs and am a test engineer for Intel, testing NICs and NIC drivers. I have installed/uninstalled FreeBSD 4.3 thru 4.5 on a diverse array of machines, but am stumped when it comes to the Intel Saber. (This is an 8-proc box running 700MHz Zeons, 8 GIG RAM - and yes, I do know the "set hw.physmem=3G" workaround for over 4 GIG machines) line in the loader.conf. Using the same install process that I have for all other successful installs, I am currently installing 4.5 off of NFS. I get results I have not seen before - none of which lead to a properly built box. It is worth noting that this same box runs Linux, Solaris and OpenUNIX8 without issue. I boot to a FreeBSD Kernel floppy which spins and prompts for the MFS Root disk. It announces that 'Memory above 4 GIG will be ignored". The kernel boots, I skip kernel configuration, it goes through the regular rigamaroll, announces an error on IRQ7, and then pauses ahc0: port 0x1000-0x88000000-0x88000fff irq 10 at device 4.0 on pci0 aic7892: Wide Channel A, SCSI Id=7, 32/25 SCBs isp0: port 0x4000-0x40ff mem 0x8b000000-0x8b000fff irq 7 at device 10.0 on pci0 Now it pauses for several (~5) minutes... isp0: Polled Mailbox Command (0x2) Timeout pauses for another several minutes.... isp0: Polled Mailbox Command (0x34) Timeout isp0:Mailbox Command 'SET CLOCK RATE' failed (TIMEOUT) pauses for another several minutes.... then shows: pci0: unknown card or vendor... and then into the rest of the stuff. At which point, it finally goes into sysinstall - precisely 20:07 minutes later! All things look great until, after choosing NFS for installation preference, it does not see my standard Intel 10/100 NIC, and installation can go no further. If instead of NFS, I choose 'CD' (Using 4.5 taken from the freebsd.org's released ISO image) I am able to install up the system, but once rebooted (allow another 20:07), cannot see the NIC (i.e. doesn't show up in ifconfig, even though it's built into the kernel.) Also, if I interrupt the kernel boot and add the "set hw.physmem=3G" statement before booting, I get a 'panic': "RAM parity error, likely a hardware failure. blah, blah...". I presume that has to do with the message upfront saying "memory above 4GIG ignored..." I don't know why it is doing that automatically. So I'm not doing that. Please reply to me directly. Thank you. - -=C. Stephen Frost=- Intel Corp. ICG - Network Quality Labs Software Test Engineer 503.264.8300 Any opinions stated are my own and not those of my employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 10:34: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 59F0937B400 for ; Thu, 7 Feb 2002 10:33:58 -0800 (PST) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.11.6/8.11.6) with ESMTP id g17IXvv44892 for ; Thu, 7 Feb 2002 11:33:57 -0700 (MST) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Thu, 07 Feb 2002 11:33:59 -0700 Subject: Re: Re[6]: natd UDP errors with PPP demand dial From: Ian To: freebsd-hackers Message-ID: In-Reply-To: <70574510802.20020207102129@mindspring.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm starting to feel like I *almost* understand what's happening here. I'm actually in the middle of making some changes to natd, but not to this part of it. (I'm just fixing some bugs in the code that translates IRC DCC control message packets.) From the output you posted, things start out looking normal. Your IP on this PPP session appears to be 207.69.102.20: > > Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to > [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 > In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to > [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 > Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to > [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 > In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to > [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 > > Above is where I think the end of one ppp session is. My workstation > is finishing talking with the mail server. > I think the next ppp session is dialed here somewhere. > > Routing message 0x2 received. > Routing message 0xd received. As I understand it, you have no PPP IP at this point, that's what the 0x2 and 0xd routing messages were telling natd: a route and an address were removed from the interface. But natd ignores this condition (other than logging that it got the notification on the routing socket). Now it gets some outgoing packets from the workstation, and translates them using the old IP address: > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 Where did these packets go? I can't answer that. However I can speculate that perhaps they didn't go very far at all, just into the IP stack on the local machine. Then we get some more routing info: > Routing message 0x2 received. > Routing message 0xd received. > Routing message 0xc received. > Interface address/MTU has probably changed. > Routing message 0x1 received. > Routing message 0xc received. > Interface address/MTU has probably changed. > Routing message 0x1 received. > Routing message 0x1 received. > Routing message 0x3 received. > > I see that the IP changed above and natd recognized that Here is where > natd enters the cone of confusion. It starts relaying messages from > the mail server to its previous IP. It's the 0xc messages that cause natd to notice it has a new address on the dynamic interface. This causes it to discard existing stale alias entries in its internal tables and obtain the new IP from the interface (actually it just sets a flag to get the new address the next time a packet comes through). I think the new IP at this point is 207.69.100.116. Now we get the really confusing part: > In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to > [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 > Out [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to >>>>>>>>> [TCP] 207.69.100.116:110 -> 207.69.102.20:3979 I think the "In" packet here may be the last "Out" packet from above. It floated around in the IP stack and since IP forwarding is on it decided the packet needs to be routed out the default gateway to get where it's going (because 207.69.102.20 isn't us anymore). Or maybe something else is going on here, but it's hard to explain how a packet for 207.69.102.20 ended up on the input side since that isn't our IP anymore. Then, the "Out" packet here is the attempt to route that same packet back out the default gateway. This time, on the way out, the packet is aliased so that the source address is the new IP for the PPP interface. I think the bulk of the problem happens when outbound packets appear during the brief time when the PPP interface has no IP yet (at least from natd's point of view, because it received the DELADDR routing message but hasn't gotten the NEWADDR message yet). I think when natd gets the DELADDR it should clean up its aliasing tables at that point, and forget any old IP addresses for that interface. But then what does it do about packets that come through while it's in that state? I'm not sure what the right answer is, maybe one of the people who maintains this part of natd would have a better answer. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 11: 3:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 0624C37B416 for ; Thu, 7 Feb 2002 11:03:41 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g17J3J464470; Thu, 7 Feb 2002 11:03:19 -0800 (PST) (envelope-from obrien) Date: Thu, 7 Feb 2002 11:03:19 -0800 From: "David O'Brien" To: "Dmitry A. Bondareff" Cc: freebsd-hackers@FreeBSD.org Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Message-ID: <20020207110319.A64437@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <004501c1af93$79b0fca0$02010101@wall> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004501c1af93$79b0fca0$02010101@wall>; from freebsd@mmk.ru on Thu, Feb 07, 2002 at 09:54:07AM +0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > Yesterday I've tried to update it teel 4.5-RELEASE. ... > P.S. Day before it I was upgrade from 4.4-RELEASE to 4.5-RELEASE easy. That means if you need to upgrade the box right now, you can upgrade your 4.0 box to 4.4 and then to 4.5. (you might also need to upgrade to 4.1 or 4.2 first). Or wait for ru. :) -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 11:58:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from home.cg.nu (home.cg.nu [213.196.2.115]) by hub.freebsd.org (Postfix) with ESMTP id A368037B417 for ; Thu, 7 Feb 2002 11:58:22 -0800 (PST) Received: from wevers.org (netfreak.xs4all.nl [213.84.69.96]) by home.cg.nu (Postfix) with ESMTP id 3DCC6158ECD for ; Thu, 7 Feb 2002 20:58:16 +0100 (CET) Message-ID: <3C62DC57.5050703@wevers.org> Date: Thu, 07 Feb 2002 20:58:15 +0100 From: Henk Wevers Reply-To: henk@wevers.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: vfs.ufs.dirhash_docheck? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Just to try the "thing" out i did put vfs.ufs.dirhash_docheck to 1. My active memory use was in 30 minutes 75 MB lower, and the io is faster, the load is lower. The OS is FreeBSD 4.5-REL with 1250MB ram on a PIII 733, it runs 30+ active jail() enviorements. What does it exactly, this hidden sysctl value? Henk Wevers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 12:18:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 0491137B422 for ; Thu, 7 Feb 2002 12:18:07 -0800 (PST) Received: from user-37kap07.dialup.mindspring.com ([207.69.100.7] helo=mr-p.protolan) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 16Yuza-0004UJ-00; Thu, 07 Feb 2002 15:18:03 -0500 Date: Thu, 7 Feb 2002 15:22:21 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <103592563401.20020207152221@mindspring.com> To: Ian Cc: freebsd-hackers Subject: Re[8]: natd UDP errors with PPP demand dial In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I> I'm starting to feel like I *almost* understand what's happening here. I'm I> actually in the middle of making some changes to natd, but not to this part I> of it. (I'm just fixing some bugs in the code that translates IRC DCC I> control message packets.) I> From the output you posted, things start out looking normal. Your IP on I> this PPP session appears to be 207.69.102.20: >> >> Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to >> [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 >> In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to >> [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 >> Out [TCP] [TCP] 192.168.0.10:3978 -> 207.69.200.225:110 aliased to >> [TCP] 207.69.102.20:3978 -> 207.69.200.225:110 >> In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3978 aliased to >> [TCP] 207.69.200.225:110 -> 192.168.0.10:3978 >> >> Above is where I think the end of one ppp session is. My workstation >> is finishing talking with the mail server. >> I think the next ppp session is dialed here somewhere. >> >> Routing message 0x2 received. >> Routing message 0xd received. I> As I understand it, you have no PPP IP at this point, that's what the 0x2 I> and 0xd routing messages were telling natd: a route and an address were I> removed from the interface. But natd ignores this condition (other than I> logging that it got the notification on the routing socket). Now it gets I> some outgoing packets from the workstation, and translates them using the I> old IP address: >> Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to >> [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 >> Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to >> [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 >> Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to >> [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 I> Where did these packets go? I can't answer that. However I can speculate I> that perhaps they didn't go very far at all, just into the IP stack on the I> local machine. Then we get some more routing info: >> Routing message 0x2 received. >> Routing message 0xd received. >> Routing message 0xc received. >> Interface address/MTU has probably changed. >> Routing message 0x1 received. >> Routing message 0xc received. >> Interface address/MTU has probably changed. >> Routing message 0x1 received. >> Routing message 0x1 received. >> Routing message 0x3 received. >> >> I see that the IP changed above and natd recognized that Here is where >> natd enters the cone of confusion. It starts relaying messages from >> the mail server to its previous IP. I> It's the 0xc messages that cause natd to notice it has a new address on the I> dynamic interface. This causes it to discard existing stale alias entries I> in its internal tables and obtain the new IP from the interface (actually it I> just sets a flag to get the new address the next time a packet comes I> through). I think the new IP at this point is 207.69.100.116. I> Now we get the really confusing part: >> In [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to >> [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 >> Out [TCP] [TCP] 207.69.200.225:110 -> 207.69.102.20:3979 aliased to >>>>>>>>>> [TCP] 207.69.100.116:110 -> 207.69.102.20:3979 I> I think the "In" packet here may be the last "Out" packet from above. It I> floated around in the IP stack and since IP forwarding is on it decided the I> packet needs to be routed out the default gateway to get where it's going I> (because 207.69.102.20 isn't us anymore). Or maybe something else is going I> on here, but it's hard to explain how a packet for 207.69.102.20 ended up on I> the input side since that isn't our IP anymore. I> Then, the "Out" packet here is the attempt to route that same packet back I> out the default gateway. This time, on the way out, the packet is aliased I> so that the source address is the new IP for the PPP interface. I> I think the bulk of the problem happens when outbound packets appear during I> the brief time when the PPP interface has no IP yet (at least from natd's I> point of view, because it received the DELADDR routing message but hasn't I> gotten the NEWADDR message yet). I think when natd gets the DELADDR it I> should clean up its aliasing tables at that point, and forget any old IP I> addresses for that interface. But then what does it do about packets that I> come through while it's in that state? I'm not sure what the right answer I> is, maybe one of the people who maintains this part of natd would have a I> better answer. I> -- Ian I think you are right, Ian. after I sent the last post, and thought more about it, I think I almost understand it also. You guys correct me if I am wrong somewhere, please. 1. The link is down. Natd has no way of knowing what the next IP will be. So, it keeps the previous IP in its database. 2. I send natd something outgoing. Since the link is not up yet, and the IP is not known yet, natd translates the packet with using a previous public IP and gives it to ppp. 3. Ppp sets up a link, and sends the packets given to it by natd with a previous sessions source IP. It seems that at this point the machine is actually spoofing some packets using an address that may have already been reassigned by Earthlink dial-up servers to another dial-up machine. 4. Worse than that, the receiving server accepts the invalid source address as valid, and replies to me, even though I now have a different valid source IP. I think arp is somehow involved here. 5. While that whole spoofing transaction is going on on the Internet, natd on my machine realizes that it now has a different IP, and updates its database. 6. When the replies from the spoofed packets return to natd, what Ian said happens. Natd realizes that the destination IP is not local, and tries to route the packet back out to the proper destination IP. I have it set to keep ports the same if possible. So, if the packet came from a DNS server, natd uses source port 53 to route the packet back out. 7. Of course, these nonsense packets run into the firewall rules, as they should. That's where I see the error messages from natd. I think I have 2 things to work out here: 1. Stop ppp from sending out spoof packets on initial link setup. 2. Stop replies to those packets from getting to natd. Perhaps, if I can do the first, the second won't be necessary. I am working on setting up ppp filters just for that using MYADDR variable. Does that sound like the best way to do it? Thank you very much, Ian. I think this is almost solved. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 12:42: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 58ECB37B41D for ; Thu, 7 Feb 2002 12:41:57 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 2B15F10DE02; Thu, 7 Feb 2002 12:41:57 -0800 (PST) Date: Thu, 7 Feb 2002 12:41:57 -0800 From: Alfred Perlstein To: Henk Wevers Cc: freebsd-hackers@freebsd.org Subject: Re: vfs.ufs.dirhash_docheck? Message-ID: <20020207124157.K3623@elvis.mu.org> References: <3C62DC57.5050703@wevers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C62DC57.5050703@wevers.org>; from henk@wevers.org on Thu, Feb 07, 2002 at 08:58:15PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Henk Wevers [020207 11:58] wrote: > Hi, > > Just to try the "thing" out i did put vfs.ufs.dirhash_docheck to 1. > My active memory use was in 30 minutes 75 MB lower, and the io is > faster, the load is lower. > The OS is FreeBSD 4.5-REL with 1250MB ram on a PIII 733, it runs 30+ > active jail() enviorements. > > What does it exactly, this hidden sysctl value? It's a debugging sysctl that is wasting cpu cycles. Turn it off, don't touch the flashing lights and keep your dirty mitts away from the big red button. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 12:46:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 52D1437B41A; Thu, 7 Feb 2002 12:46:36 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g17KkSM05459; Thu, 7 Feb 2002 21:46:28 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Date: Thu, 7 Feb 2002 21:46:28 +0100 (CET) Message-Id: <200202072046.g17KkSM05459@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: USB "Memorybird" quirks User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.5-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I've got a small problem with a nice little thing called "USB Memorybird" (Fujitsu-Siemens) ... It is bascially a 64 MB Flash chip in a small plastic pen that you can carry with your keys. It doesn't need any battery and you can plug it directly into a USB socket. Very neat. Works without any drivers on WinME and Win2k, so I assume it should be some standard USB mass storage device. FreeBSD 4.5 recognizes it out of the box and attaches it as a SCSI disk, but I cannot access it. This is what happens: From the boot log: uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered This appears when I connect the Memorybird: umass0: Fujitsu Memorybird, rev 1.00/1.00, addr 2 da2 at umass-sim0 bus 0 target 0 lun 0 da2: Removable Direct Access SCSI-0 device da2: 650KB/s transfers da2: 62MB (128000 512 byte sectors: 64H 32S/T 62C) This is the output from "usbdevs -v" (note that there is a ~10 seconds delay!): Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 port 1 powered < ~10 seconds delay > port 2 addr 2: power 100 mA, config 1, product 0x0100(0x0100), vendor 0x0d7d(0x0d7d), rev 0x0100 When I type "fdisk da2", it hangs for a while, then prints: fdisk: can't open device /dev/da2 fdisk: cannot open disk /dev/da2: Input/output error At the same time, the kernel logs this: Feb 7 20:00:31 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 20:00:36 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 20:00:41 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Feb 7 20:00:51 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 20:00:56 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 20:01:01 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT The same happens when I try to dd some block from the device to /dev/null. During my experiments I also got these messages (I don't know if they're important): Feb 7 19:54:46 lurza /kernel: da2: reading primary partition table: error reading fsbn 0 Feb 7 19:54:56 lurza /kernel: umass0: BBB reset failed, TIMEOUT Feb 7 19:55:01 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Feb 7 19:55:06 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Feb 7 19:55:06 lurza /kernel: (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Is there a chance to get this to run? Clearly the umass driver recognizes it and attaches it as a SCSI disk, so I assume that it can't be _that_ hard to convince it to work with FreeBSD. :) Are there any quirks that I should try? I'm not extremely familiar with that kind of stuff, but I'm willing to experiment. Thanks in advance for any help! I would _really_ love to get this thing working. Regards Oliver BTW: More information on the Memorybird: http://www.fujitsu-siemens.com/rl/peripherals/homeperipherals/memorybird.html -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 12:55:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id BDE6737B405; Thu, 7 Feb 2002 12:54:54 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g17KsnO09885; Thu, 7 Feb 2002 12:54:49 -0800 (PST) Date: Thu, 7 Feb 2002 12:54:49 -0800 From: "Eugene M. Kim" To: Oliver Fromme Cc: FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207125449.A9620@alicia.nttmcl.com> References: <200202072046.g17KkSM05459@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200202072046.g17KkSM05459@lurza.secnetix.de>; from olli@secnetix.de on Thu, Feb 07, 2002 at 09:46:28PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a common problem of most umass devices that implements BBB protocol, and arises from the fact that those devices don't understand the 6-byte SCSI READ command. You can add a quirk entry to src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). IIRC this problem is being addressed at a more fundamental level on -current, by adding a 6-byte-to-10-byte READ command translator somewhere in the abstraction layer. Eugene On Thu, Feb 07, 2002 at 09:46:28PM +0100, Oliver Fromme wrote: > > > Hi, > > I've got a small problem with a nice little thing called > "USB Memorybird" (Fujitsu-Siemens) ... > > It is bascially a 64 MB Flash chip in a small plastic pen > that you can carry with your keys. It doesn't need any > battery and you can plug it directly into a USB socket. > Very neat. > > Works without any drivers on WinME and Win2k, so I assume > it should be some standard USB mass storage device. > > FreeBSD 4.5 recognizes it out of the box and attaches it as > a SCSI disk, but I cannot access it. This is what happens: > > >From the boot log: > > uhci0: port 0xd400-0xd41f irq 10 at device 7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > > This appears when I connect the Memorybird: > > umass0: Fujitsu Memorybird, rev 1.00/1.00, addr 2 > da2 at umass-sim0 bus 0 target 0 lun 0 > da2: Removable Direct Access SCSI-0 device > da2: 650KB/s transfers > da2: 62MB (128000 512 byte sectors: 64H 32S/T 62C) > > This is the output from "usbdevs -v" (note that there is a > ~10 seconds delay!): > > Controller /dev/usb0: > addr 1: self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 0x0100 > port 1 powered > < ~10 seconds delay > > port 2 addr 2: power 100 mA, config 1, product 0x0100(0x0100), vendor 0x0d7d(0x0d7d), rev 0x0100 > > When I type "fdisk da2", it hangs for a while, then prints: > > fdisk: can't open device /dev/da2 > fdisk: cannot open disk /dev/da2: Input/output error > > At the same time, the kernel logs this: > > Feb 7 20:00:31 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 20:00:36 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 20:00:41 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > Feb 7 20:00:51 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 20:00:56 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 20:01:01 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > > The same happens when I try to dd some block from the > device to /dev/null. During my experiments I also got > these messages (I don't know if they're important): > > Feb 7 19:54:46 lurza /kernel: da2: reading primary partition table: error reading fsbn 0 > Feb 7 19:54:56 lurza /kernel: umass0: BBB reset failed, TIMEOUT > Feb 7 19:55:01 lurza /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT > Feb 7 19:55:06 lurza /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT > Feb 7 19:55:06 lurza /kernel: (da2:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 > > Is there a chance to get this to run? Clearly the umass > driver recognizes it and attaches it as a SCSI disk, so > I assume that it can't be _that_ hard to convince it to > work with FreeBSD. :) > > Are there any quirks that I should try? I'm not extremely > familiar with that kind of stuff, but I'm willing to > experiment. > > Thanks in advance for any help! I would _really_ love to > get this thing working. > > Regards > Oliver > > BTW: More information on the Memorybird: > http://www.fujitsu-siemens.com/rl/peripherals/homeperipherals/memorybird.html > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "All that we see or seem is just a dream within a dream" (E. A. Poe) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 13:44:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id DB98E37B425; Thu, 7 Feb 2002 13:42:50 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g17LgjV01787; Thu, 7 Feb 2002 22:42:45 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202072142.g17LgjV01787@lurza.secnetix.de> Subject: kern/34712 (was: USB "Memorybird" quirks) To: gene@nttmcl.com (Eugene M. Kim) Date: Thu, 7 Feb 2002 22:42:45 +0100 (CET) Cc: hardware@freebsd.org (FreeBSD Hardware Mailing List), hackers@freebsd.org (FreeBSD Hackers Mailing List) In-Reply-To: <20020207125449.A9620@alicia.nttmcl.com> from "Eugene M. Kim" at Feb 07, 2002 12:54:49 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene M. Kim wrote: > This is a common problem of most umass devices that implements BBB > protocol, and arises from the fact that those devices don't understand > the 6-byte SCSI READ command. You can add a quirk entry to > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). Thankyou very much! It works. Very cool indeed. # mount -t msdos /dev/da2s1 /mnt # df -k /mnt Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da2s1 63718 4 63714 0% /mnt This is with the following patch applied to 4.5-RELEASE: --- src/sys/cam/scsi/scsi_da.c.orig Mon Jan 14 10:25:43 2002 +++ src/sys/cam/scsi/scsi_da.c Thu Feb 7 22:07:33 2002 @@ -345,6 +345,14 @@ */ {T_DIRECT, SIP_MEDIA_REMOVABLE, "DIVA USB", "Media Reader","*"}, /*quirks*/ DA_Q_NO_6_BYTE + }, + { + /* + * Fujitsu-Siemens Memorybird. + * Doesn't work correctly with 6 byte reads/writes. + */ + {T_DIRECT, SIP_MEDIA_REMOVABLE, "Fujitsu", "Memorybird", "*"}, + /*quirks*/ DA_Q_NO_6_BYTE } }; I've submitted a PR accordingly, it's kern/34712. Can someone please commit it? Thanks! Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 13:54:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 2ABB537B41D; Thu, 7 Feb 2002 13:54:38 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YwV1-00010K-00; Thu, 07 Feb 2002 13:54:36 -0800 Message-ID: <3C62F744.96069B4A@mindspring.com> Date: Thu, 07 Feb 2002 13:53:08 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nero Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: new page cache for linux References: <20020208025900.4717cf72.neroz@dingoblue.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nero wrote: > Just thought I'd bring your attention to the new "radix tree page cache" > in use by linux - I dont know what freebsd do at the moment, but it looks > like it will improve scalability (you guys might want to use the idea). > Anyway, heres the link: http://lwn.net/2002/0207/kernel.php3 You should look at how FreeBSD already handles this problem. Note also that as physical memory approaches real memory in size, the sparseness of the mapping goes to zero. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 14:24:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from neo.spbnit.ru (mail.spbnit.ru [212.48.192.115]) by hub.freebsd.org (Postfix) with ESMTP id 47C9237B41E for ; Thu, 7 Feb 2002 14:24:33 -0800 (PST) Received: from default (ppp-108.pool-123.spbnit.ru [212.48.201.108]) by neo.spbnit.ru (8.9.3+mPOP/8.9.3) with ESMTP id BAA19085 for ; Fri, 8 Feb 2002 01:24:30 +0300 (MSK) Message-Id: <200202072224.BAA19085@neo.spbnit.ru> From: "Vladislav V. Anikiev" To: Subject: MAC address Date: Thu, 7 Feb 2002 22:45:01 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello everyone, I'm writing some license management software. It needs to be node-locked. I would like to use an ethernet MAC address. There are two addresses (default hardware address and current physical address). I would prefer to use the default hardware address, because it can't be changed by setting in software. How can I take this default hardware address (I'm using FreeBSD 4.4 curently)? I've found out the way how it works in "ifconfig", but in this case I've got the current physical address, I think (right?), which can be changed. Help me, please Vladislav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 14:31: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CCE0337B4B6 for ; Thu, 7 Feb 2002 14:30:19 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Feb 2002 22:30:18 +0000 (GMT) Date: Thu, 7 Feb 2002 22:30:18 +0000 From: David Malone To: Alfred Perlstein Cc: Henk Wevers , freebsd-hackers@freebsd.org Subject: Re: vfs.ufs.dirhash_docheck? Message-ID: <20020207223018.GB67018@walton.maths.tcd.ie> References: <3C62DC57.5050703@wevers.org> <20020207124157.K3623@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020207124157.K3623@elvis.mu.org> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 12:41:57PM -0800, Alfred Perlstein wrote: > * Henk Wevers [020207 11:58] wrote: > > Just to try the "thing" out i did put vfs.ufs.dirhash_docheck to 1. > > My active memory use was in 30 minutes 75 MB lower, and the io is > > faster, the load is lower. > > The OS is FreeBSD 4.5-REL with 1250MB ram on a PIII 733, it runs 30+ > > active jail() enviorements. > > > > What does it exactly, this hidden sysctl value? > > It's a debugging sysctl that is wasting cpu cycles. Turn it off, > don't touch the flashing lights and keep your dirty mitts away > from the big red button. Actually, Ian told me that it enables some secret inline assembley that increases the RPM of your hard disk and defragments the microcode on the CPU... Another good tip is to regurally unplug the RJ45 from your ethernet card and clean out the socket with a old toothbrush. It gets rid of any ether which has built up due to heave network usage. ;-) But seriously, as Alfred says - it enables some extra sanity checks in the dirhash code. It shouldn't make any difference, except that it burns a few CPU cycles. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 15:17:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 6B43337B416 for ; Thu, 7 Feb 2002 15:17:09 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Yxmo-0002Fn-00; Thu, 07 Feb 2002 15:17:02 -0800 Message-ID: <3C630A88.5986BF8E@mindspring.com> Date: Thu, 07 Feb 2002 15:15:20 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Cc: freebsd-hackers Subject: Re: natd UDP errors with PPP demand dial References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian wrote: > > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 > > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 > > Out [TCP] [TCP] 192.168.0.10:3979 -> 207.69.200.225:110 aliased to > > [TCP] 207.69.102.20:3979 -> 207.69.200.225:110 > > Where did these packets go? I can't answer that. However I can speculate > that perhaps they didn't go very far at all, just into the IP stack on the > local machine. Then we get some more routing info: FWIW: I've seen something similar with an IPSEC based VPN; it's my opinion that the problems are related, and that this is a routing issue, not a NAT issue. In the IPSEC case, if there is an explicit point-to-point route, and the default route is *NOT* set, then you get packets. If the default route is used to deliver the packets to the tunnel, then the packets get to the remote end, but the reply packets to the local end, which show up in tcpdump as hitting the local wire, don't make it up the stack for some reason. There appears to be a problem with the route cloning code not noticing correctly when a new route is established that applies to an already cloned connection, I think. This normally isn't a problem, but in the IPSEC or NAT case, wheere you are on a network border with another network in the same box, and you effectively need to have the moral equivalent of two different default routes, it seems to become an issue. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 15:27:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id A642537B41D for ; Thu, 7 Feb 2002 15:27:37 -0800 (PST) Received: by seven.Alameda.net (Postfix, from userid 1000) id B066E3A242; Thu, 7 Feb 2002 15:27:36 -0800 (PST) Date: Thu, 7 Feb 2002 15:27:36 -0800 From: Ulf Zimmermann To: Josef Karthauser Cc: "Duane H. Hesser" , hackers@FreeBSD.ORG, Ulf Zimmermann Subject: Re: USB UHCI speed issue ? Message-ID: <20020207152736.T45642@seven.alameda.net> Reply-To: ulf@Alameda.net References: <20020116110612.B16252@genius.tao.org.uk> <200201200139.g0K1dv621605@androcles.com> <20020120112349.B7430@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020120112349.B7430@genius.tao.org.uk>; from joe@tao.org.uk on Sun, Jan 20, 2002 at 11:23:49AM +0000 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jan 20, 2002 at 11:23:49AM +0000, Josef Karthauser wrote: > On Sat, Jan 19, 2002 at 05:39:56PM -0800, Duane H. Hesser wrote: > > > > I can confirm the problem, and point you to a message in the "current" > > archives (Dec 15) which contains a simple 3 or 4 line patch to uhui.c. > > The message, authored by Andrew Gordon, may be found at > > > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=775757+780830+/usr/local/www/db/text/2001/freebsd-current/20011216.freebsd-curren > > t > > Hmm. :) Looking at the NetBSD code, they made a major commit to fix the > same issue: > > uhci.c revision 1.123 > date: 2000/08/13 16:18:09; author: augustss; state: Exp; lines: +136 -31 > Implement what in Intel-speech is known as "bandwidth reclamation". > It means that we continously poll USB devices that have a pending transfer > instead of polling just once every ms. This speeds up some transfers > at the expense of using more PCI bandwidth. > > I'm looking at what is necessary to port that change over. > > Joe I was wondering if this has been ported over and if so, how about a -stable version. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 15:36: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mailer2.webgiro.com [213.162.131.18]) by hub.freebsd.org (Postfix) with ESMTP id 53DB237B41B for ; Thu, 7 Feb 2002 15:36:04 -0800 (PST) Received: from ftl (mailer2.webgiro.com [213.162.131.18]) by mimer.webgiro.com (Postfix) with ESMTP id 4B91E68469; Fri, 8 Feb 2002 00:35:55 +0100 (CET) Message-ID: <005e01c1b030$15589450$01000001@ftl> From: "Andrzej Bialecki" To: "Frost, Stephen C" , Cc: "Frost, Stephen C" References: Subject: Re: FreeBSD onto An Intel Saber 8-Proc Server Date: Fri, 8 Feb 2002 00:35:08 +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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > later! All things look great until, after choosing NFS for installation > preference, it does not see my standard Intel 10/100 NIC, and installation > can go no further. > > If instead of NFS, I choose 'CD' (Using 4.5 taken from the freebsd.org's > released ISO image) I am able to install up the system, but once rebooted > (allow another 20:07), cannot see the NIC (i.e. doesn't show up in ifconfig, > even though it's built into the kernel.) I can't offer any insights as for the SCSI adapters, but re: NIC - I've had similar symptoms quite a few times with Intel motherboards, and usually the cause was that the NIC was disabled in BIOS. FreeBSD could still see it, but something was missing on the low level and any access to the card would lock up the machine solid... Best regards, Andrzej // ---------------------------------------------------------------- // Andrzej Bialecki , Chief System Architect // WebGiro AB, Sweden (http://www.webgiro.com) // ---------------------------------------------------------------- // FreeBSD developer (http://www.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 15:54:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 5D1C437B41A; Thu, 7 Feb 2002 15:54:32 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YyMw-00059O-00; Thu, 07 Feb 2002 15:54:23 -0800 Message-ID: <3C63133A.CF411A74@mindspring.com> Date: Thu, 07 Feb 2002 15:52:26 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene M. Kim" wrote: > > This is a common problem of most umass devices that implements BBB > protocol, and arises from the fact that those devices don't understand > the 6-byte SCSI READ command. You can add a quirk entry to > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > IIRC this problem is being addressed at a more fundamental level on > -current, by adding a 6-byte-to-10-byte READ command translator > somewhere in the abstraction layer. Could this be "auto-quirked"? It seems to me that you should be able to add the quirk flag to the device instance after the first failure... Unfortunately, I don't have one of these toys, so he'll have to do the code himself. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 15:57:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id BBBA037B405; Thu, 7 Feb 2002 15:57:47 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id C2CA9410; Thu, 7 Feb 2002 23:57:46 +0000 (GMT) Date: Thu, 7 Feb 2002 23:57:46 +0000 From: Josef Karthauser To: Terry Lambert Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207235746.E46984@genius.tao.org.uk> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UnaWdueM1EBWVRzC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C63133A.CF411A74@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 03:52:26PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UnaWdueM1EBWVRzC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > >=20 > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. >=20 > Could this be "auto-quirked"? >=20 As in, try a 6 byte command, and if that fails try a 10 byte command instead? Unfortunately although I'm maintaining USB in -current, I don't have a complete in depth understanding of the code yet. :( I'm mainly trying to fix my problems by taking from NetBSD. Joe --UnaWdueM1EBWVRzC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxjFHoACgkQXVIcjOaxUBYRcgCgtwLd0OsXPbxbwBQYKblFEWVD Db4AoIjORl8hdZuOF6YKiX0SwvThVwXC =9+QE -----END PGP SIGNATURE----- --UnaWdueM1EBWVRzC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 16: 3: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 95D6637B400; Thu, 7 Feb 2002 16:03:00 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g1802uV19724; Thu, 7 Feb 2002 16:02:56 -0800 (PST) Date: Thu, 7 Feb 2002 16:02:56 -0800 From: "Eugene M. Kim" To: Terry Lambert Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020207160256.A19270@alicia.nttmcl.com> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3C63133A.CF411A74@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 03:52:26PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > "Eugene M. Kim" wrote: > > > > This is a common problem of most umass devices that implements BBB > > protocol, and arises from the fact that those devices don't understand > > the 6-byte SCSI READ command. You can add a quirk entry to > > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. > > Could this be "auto-quirked"? > > It seems to me that you should be able to add the quirk flag > to the device instance after the first failure... > > Unfortunately, I don't have one of these toys, so he'll have > to do the code himself. 8-). The USB development team seems to have something similar to your idea in their mind; see the comment for rev 1.47 of: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/umass.c?f=u&only_with_tag=MAIN&logsort=date It mentions about `da(4) becoming more intelligent about this.' Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 16:42:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 9202137B41A; Thu, 7 Feb 2002 16:42:02 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Yz6u-00055G-00; Thu, 07 Feb 2002 16:41:53 -0800 Message-ID: <3C631E45.2EAAA4CF@mindspring.com> Date: Thu, 07 Feb 2002 16:39:33 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207235746.E46984@genius.tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Josef Karthauser wrote: > On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > IIRC this problem is being addressed at a more fundamental level on > > > -current, by adding a 6-byte-to-10-byte READ command translator > > > somewhere in the abstraction layer. > > > > Could this be "auto-quirked"? > > As in, try a 6 byte command, and if that fails try a 10 byte command > instead? As in, if it fails to reset, then sc->softc->minimum_cmd_size = 10; printf( "auto-quirking mumble foo\n"); It would let most of the existing quirks table go away, but would require additional retries. The cool thing is that it would all happen in the error path, so, other than increasing the number of retries to cause it to engage by itself without having to try the disklabel 3 times, which is also failure mode stuff, it adds no overhead to working devices, and makes non-working ones work with the overhead they have to have anyway. > Unfortunately although I'm maintaining USB in -current, I don't have a > complete in depth understanding of the code yet. :( I'm mainly trying > to fix my problems by taking from NetBSD. I took a look at the code. I have to say it's opaque. It makes a better door than a window. ;-). I haven't figured out how to turn a struct umass_softc * into a struct da_softc *, or I would have given you an ugly little patch against an older version of FreeBSD to try. 8-p. I think someone with one of these things, or with a quirky one with the DA_Q_NO_6_BYTE removed from the quirks table, is going to have to set CAM_DEBUG on big-time, and then see where the reset error falls out, add a static fail counter to that place in the code, and then if it fails and the fail counter >= 3 (for example), reset the minimum command size to 10. That should "just work". If the reset is retried enough times, you could get rid of the quirks entries that existed solely for this quirk; I think that a 6 byte commands not supported: changing to 10 byte commands message on the console is probably acceptable "noise" in trade for getting rid of it, and supporting future devices with the same problem, without needing to "quirk" them. I think DA_Q_NO_SYNC_CACHE might be handleable the same way, which would get rid of all the quirk entries, and maybe the need for a quirk table at all (it looks like the daclose/dadump/dashutdown sync code could be static'ed and shared, as well). Maybe this is a CAM-specific thing, and shouldn't be handled in the USB code at all (you won't know until you see a quirked device failure with the CAM debug, or you write the CAM code to tape and run it through your dental fillings or otherwise load it into your head). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 16:48:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 24EFF37B41E; Thu, 7 Feb 2002 16:48:36 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16YzDE-0006Ng-00; Thu, 07 Feb 2002 16:48:26 -0800 Message-ID: <3C631FD9.AABA00B4@mindspring.com> Date: Thu, 07 Feb 2002 16:46:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207160256.A19270@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene M. Kim" wrote: > The USB development team seems to have something similar to your idea in > their mind; see the comment for rev 1.47 of: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/umass.c?f=u&only_with_tag=MAIN&logsort=date > > It mentions about `da(4) becoming more intelligent about this.' See my other posting. It's definitely a CAM thing, not a USB thing, and the handling should be automatic, with no quirks table at all. The USB code, though, then has a responsibility to retry more times, so that the failure triggers the workaround, and the with the workaround in place, the operation then succeeds transparently. I don't think this is universal, though, since I can't see this approach working for a CD burner failure which might render something unrecoverable, but I have yet to see a place it would fail. I think the person with the problem needs to turn on the CAM debugging, or a CAM-head needs to become involved. The workaround works, for now, but it's frustrating, knowing that the next time anyone OEMs the same hardware and changes the ID, it will have to grow another quirk. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 17:55:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.cpl.net (luke.cpl.net [63.169.72.3]) by hub.freebsd.org (Postfix) with ESMTP id 14A5537B41A for ; Thu, 7 Feb 2002 17:55:41 -0800 (PST) Received: from shawn ([63.169.72.21]) by luke.cpl.net (8.11.3/8.11.3) with SMTP id g181vUt58293 for ; Thu, 7 Feb 2002 17:57:30 -0800 (PST) Message-ID: <007001c1b043$65612fd0$1548a93f@shawn> From: "Shawn Ramsey" To: References: <011f01c1aed7$3ff161b0$0202140a@shawn> Subject: crashing server / crash dump Date: Thu, 7 Feb 2002 17:53:25 -0800 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am resending this to hackers out of desparation... If I didn't send the right, or enough information I will gladly send whatever if it can help diagnose the problem. It is not the RAID controller, i've taken the RAID offline, though the controller is still in the server, but no drives are mounted. Nothing has changed on this server, other than OS upgrades, and RAID. (more or less) > Im not sure if this is the right place to send this sort of thing...but here > goes. We have a server crashing daily, and im not sure why. It seemed to > coincide with the addition of several SCSI disks connected to an ExtremeRAID > 1100. The server is running 4.5-STABLE as of about 3 days ago, but has > exhibited similar problems since version 4.3-RELEASE. > > Here is the output from gdb -k : > > Script started on Mon Feb 4 20:59:21 2002 > /usr/src/sys/compile/Luke {1}>gdb -k > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or 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. > This GDB was configured as "i386-unknown-freebsd". > (kgdb) symbol-file kernel.debug > Reading symbols from kernel.debug...done. > (kgdb) exec-file /var/crash/kernel.0 > (kgdb) core-file /var/crash/vmcore.0 > IdlePTD at phsyical address 0x00387000 > initial pcb at physical address 0x002eec80 > panicstr: ffs_vfree: freeing free inode > panic messages: > --- > panic: ffs_vfree: freeing free inode > > syncing disks... 130 126 121 118 112 107 107 95 89 80 77 74 72 66 65 63 60 > 60 50 48 47 45 41 41 34 30 29 28 26 23 20 18 16 15 14 12 9 7 5 4 2 2 2 2 2 2 > 2 2 2 2 2 2 2 2 2 2 2 2 2 2 > giving up on 2 buffers > Uptime: 1d1h53m57s > mlx0: flushing cache...done > mlxd0: detached > mlx1: flushing cache...done > mlxd1: detached > mlxd2: detached > mlxd3: detached > > dumping to dev #ad/0x20001, offset 589824 > dump ata0: resetting devices .. done > 512 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 > 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 > 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 > 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 437 > 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 418 > 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 > 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 > 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 > 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 > 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 > 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 > 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 > 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 > 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 > 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 > 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 > 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 > 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 > 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 > 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 > 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 > 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 > 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 > 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 > 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 > 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 > --- > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > 474 if (dumping++) { > (kgdb) backtrace > #0 dumpsys () at ../../kern/kern_shutdown.c:474 > #1 0xc015f8a7 in boot (howto=256) at ../../kern/kern_shutdown.c:313 > #2 0xc015fca1 in panic (fmt=0xc02acf71 "ffs_vfree: freeing free inode") > at ../../kern/kern_shutdown.c:582 > #3 0xc0221549 in ffs_freefile () > #4 0xc02213d2 in ffs_vfree () > #5 0xc022d7b1 in ufs_inactive (ap=0xd785ccbc) at > ../../ufs/ufs/ufs_inode.c:96 > #6 0xc0232c71 in ufs_vnoperatefifo (ap=0xd785ccbc) > at ../../ufs/ufs/ufs_vnops.c:2431 > #7 0xc018d6b0 in vput (vp=0xd854b600) at ../../kern/vfs_subr.c:1638 > #8 0xc0231863 in ufs_rename (ap=0xd785ce68) at > ../../ufs/ufs/ufs_vnops.c:1208 > #9 0xc0232c71 in ufs_vnoperatefifo (ap=0xd785ce68) > at ../../ufs/ufs/ufs_vnops.c:2431 > #10 0xc0192263 in rename () > #11 0xc0275749 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 75, tf_esi = 5241, tf_ebp = -1077939076, tf_isp = -679096364, > tf_ebx = 134864144, tf_edx = -1077939296, tf_ecx = -1077939296, > tf_eax = 128, tf_trapno = 0, tf_err = 2, tf_eip = 672126368, tf_cs = > 31, > tf_eflags = 518, tf_esp = -1077939432, tf_ss = 47}) > at ../../i386/i386/trap.c:1157 > #12 0xc0268e05 in Xint0x80_syscall () > #13 0x805faa9 in ?? () > #14 0x805f1c9 in ?? () > ---Type to continue, or q to quit--- > #15 0x805bde8 in ?? () > #16 0x805b641 in ?? () > #17 0x804a8d1 in ?? () > #18 0x8049565 in ?? () > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 18:45:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 74AFF37B419 for ; Thu, 7 Feb 2002 18:45:28 -0800 (PST) Received: (qmail 16168 invoked by uid 3001); 8 Feb 2002 02:45:24 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 8 Feb 2002 02:45:24 -0000 Received: (qmail 94612 invoked by uid 1001); 8 Feb 2002 02:45:24 -0000 Date: Thu, 7 Feb 2002 21:45:24 -0500 From: Brian Reichert To: "Vladislav V. Anikiev" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address Message-ID: <20020207214524.N2872@numachi.com> References: <200202072224.BAA19085@neo.spbnit.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202072224.BAA19085@neo.spbnit.ru>; from vladani@mail.spbnit.ru on Thu, Feb 07, 2002 at 10:45:01PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > Hello everyone, > > I'm writing some license management software. It needs to be node-locked. > I would like to use an ethernet MAC address. There are two addresses > (default hardware address and current physical address). I would prefer to > use the default hardware address, because it can't be changed by setting in > software. Depending on the NIC, the MAC address _can_ be changed. Unless I've completely misunderstood you... And, what if you have two NICs? > How can I take this default hardware address (I'm using FreeBSD 4.4 > curently)? The output from 'dmesg' seems to record the device's MAC address before it mght get changed via ifconfig. But, that's not preserved forever... > I've found out the way how it works in "ifconfig", but in this case I've > got the current physical address, I think (right?), which can be changed. > > Help me, please > > Vladislav -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 18:46: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 7E57637B427; Thu, 7 Feb 2002 18:45:42 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id B903B314; Fri, 8 Feb 2002 02:45:40 +0000 (GMT) Date: Fri, 8 Feb 2002 02:45:40 +0000 From: Josef Karthauser To: Terry Lambert Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020208024540.B50352@genius.tao.org.uk> References: <200202072046.g17KkSM05459@lurza.secnetix.de> <20020207125449.A9620@alicia.nttmcl.com> <3C63133A.CF411A74@mindspring.com> <20020207160256.A19270@alicia.nttmcl.com> <3C631FD9.AABA00B4@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C631FD9.AABA00B4@mindspring.com>; from tlambert2@mindspring.com on Thu, Feb 07, 2002 at 04:46:17PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --CdrF4e02JqNVZeln Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 07, 2002 at 04:46:17PM -0800, Terry Lambert wrote: > I think the person with the problem needs to turn on the > CAM debugging, or a CAM-head needs to become involved. The > workaround works, for now, but it's frustrating, knowing > that the next time anyone OEMs the same hardware and changes > the ID, it will have to grow another quirk. 8-(. It's also a pain to maintain. Joe --CdrF4e02JqNVZeln Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxjO9QACgkQXVIcjOaxUBZgMACfUM8XSVF94Q3IzlNc/fYVLuZD cVYAnj4FQXsfICv3CY3tB3Dd3QHWjmE2 =tShr -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 21:23: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 1882D37B41F; Thu, 7 Feb 2002 21:22:57 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g185UJh72111; Fri, 8 Feb 2002 10:30:19 +0500 (YEKT) Received: from wall.mmk.ru (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with ESMTP id g185MIb25091; Fri, 8 Feb 2002 10:22:18 +0500 (ESK) Received: from wall (fw.dim.ru [1.1.1.2]) by wall.mmk.ru (8.11.6/8.11.6) with SMTP id g185Jd107433; Fri, 8 Feb 2002 10:19:40 +0500 (YEKT) Message-ID: <012e01c1b061$514cd2b0$02010101@wall> From: "Dmitry A. Bondareff" To: Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207110319.A64437@dragon.nuxi.com> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Fri, 8 Feb 2002 10:27:35 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you lie me, I'll be back !! :)) ----- Original Message ----- From: "David O'Brien" To: "Dmitry A. Bondareff" Cc: Sent: Friday, February 08, 2002 12:03 AM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > Yesterday I've tried to update it teel 4.5-RELEASE. > ... > > P.S. Day before it I was upgrade from 4.4-RELEASE to 4.5-RELEASE easy. > > That means if you need to upgrade the box right now, you can upgrade your > 4.0 box to 4.4 and then to 4.5. (you might also need to upgrade to 4.1 > or 4.2 first). Or wait for ru. :) > > -- > -- David (obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 21:47: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 067CF37B421; Thu, 7 Feb 2002 21:46:54 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id HAA32528; Fri, 8 Feb 2002 07:46:49 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from h12.229.dialup.iptcom.net (h12.229.dialup.iptcom.net [212.9.229.12]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id HAA67834; Fri, 8 Feb 2002 07:46:45 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Subject: Linking libc before libc_r into application causes weird problems From: Maxim Sobolev To: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Content-Type: multipart/mixed; boundary="=-HwruOWPo7n3Nq8WN5HEs" Message-Id: <1013147180.73417.2.camel@notebook> Mime-Version: 1.0 X-Mailer: Evolution/1.0.2 Date: 08 Feb 2002 07:46:34 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-HwruOWPo7n3Nq8WN5HEs Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi, When working on updating port of Ximian Evolution to the latest released version I have stuck to the problem - the new version of application just hanged on startup on my 5-CURRENT box. After lot of digging and debugging I found that the source of the problem is that the resulting application had libc linked in before libc_r, which caused waitpid() in the ORBit library just hang forever, even though child process died almost instantly (I see zombie in the ps(1) output). When program was relinked with -pthread flag, which seemingly forcing "right" order of libc/libc_r (libc_r first) the problem disappeared. Based on the problematic code in the ORBit I had prepared short testcase illustrating the problem and attaching it with this message. The problem could be exposed by compiling the test.c using the following command: $ cc test.c -o test -lc -lc_r When either of -lc or -lc_r is omitted, or their order is reversed the problem disappears. The problem doesn't exist on 4-STABLE. Any ideas, comments and suggestions are welcome. Thanks! -Maxim --=-HwruOWPo7n3Nq8WN5HEs Content-Disposition: attachment; filename=test.c Content-Transfer-Encoding: quoted-printable Content-Type: text/x-c; charset=KOI8-R #include #include #include #include #include #include int main() { int childpid, exitstatus, itmp; sigset_t mask, omask; /* Block SIGCHLD so no one else can wait() on the child before we do. *= / sigemptyset(&mask); sigaddset(&mask, SIGCHLD); sigprocmask(SIG_BLOCK, &mask, &omask); childpid =3D fork(); if(!childpid) { int i; /* Do something useful */ sleep(1); _exit(0); } while ((itmp =3D waitpid(childpid, &exitstatus, 0)) =3D=3D -1 && errno = =3D=3D EINTR) continue; sigprocmask (SIG_SETMASK, &omask, NULL); exit(WEXITSTATUS(exitstatus)); } --=-HwruOWPo7n3Nq8WN5HEs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 22:34:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 9935337B41F; Thu, 7 Feb 2002 22:34:05 -0800 (PST) Received: from pool0339.cvx22-bradley.dialup.earthlink.net ([209.179.199.84] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Z4bj-0002m1-00; Thu, 07 Feb 2002 22:34:03 -0800 Message-ID: <3C637097.13B8C35A@mindspring.com> Date: Thu, 07 Feb 2002 22:30:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > $ cc test.c -o test -lc -lc_r > > When either of -lc or -lc_r is omitted, or their order is reversed the > problem disappears. The problem doesn't exist on 4-STABLE. > > Any ideas, comments and suggestions are welcome. Symbols are resolved from libraries in the order in which they are specified to the linker. So the fix is obvious: specify them in the right order. Linux doesn't see this because libc_r is just there for the reentrant calls, and their threading uses processes, instead of a user space ("quantum conservation") scheduler. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 22:47:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9BEA337B404; Thu, 7 Feb 2002 22:47:51 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g186lni25313; Thu, 7 Feb 2002 23:47:50 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g186lmL49701; Thu, 7 Feb 2002 23:47:49 -0700 (MST) (envelope-from imp@village.org) Date: Thu, 07 Feb 2002 23:47:21 -0700 (MST) Message-Id: <20020207.234721.71750312.imp@village.org> To: sobomax@FreeBSD.ORG Cc: jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weird problems From: "M. Warner Losh" In-Reply-To: <1013147180.73417.2.camel@notebook> References: <1013147180.73417.2.camel@notebook> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <1013147180.73417.2.camel@notebook> Maxim Sobolev writes: : Based on the problematic code in the ORBit I had prepared short testcase : illustrating the problem and attaching it with this message. The problem : could be exposed by compiling the test.c using the following command: : : $ cc test.c -o test -lc -lc_r cc test.c -o test -pthread If that doesn't work, test.c is broken :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 22:50:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3185F37B41F; Thu, 7 Feb 2002 22:50:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g186o8i25339; Thu, 7 Feb 2002 23:50:09 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g186o7L49723; Thu, 7 Feb 2002 23:50:07 -0700 (MST) (envelope-from imp@village.org) Date: Thu, 07 Feb 2002 23:49:39 -0700 (MST) Message-Id: <20020207.234939.69060047.imp@village.org> To: sobomax@FreeBSD.ORG Cc: jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weird problems From: "M. Warner Losh" In-Reply-To: <1013147180.73417.2.camel@notebook> References: <1013147180.73417.2.camel@notebook> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Confirmed. test.c appears to work properly when compiled: cc -o test test.c -pthread ./test Generally speaking, if you want to add -lc_r, you are doing things incorrectly. I've done way to much building... In FreeBSD 3.x you did need to do -lc_r, but that was changed to -pthread in 4.0. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 22:59:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from femail32.sdc1.sfba.home.com (femail32.sdc1.sfba.home.com [24.254.60.22]) by hub.freebsd.org (Postfix) with ESMTP id E8BC137B41F; Thu, 7 Feb 2002 22:59:37 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail32.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20020208065937.RAOW5531.femail32.sdc1.sfba.home.com@math.missouri.edu>; Thu, 7 Feb 2002 22:59:37 -0800 Message-ID: <3C63773A.8DBF36F6@math.missouri.edu> Date: Fri, 08 Feb 2002 00:59:06 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: "M. Warner Losh" Cc: sobomax@FreeBSD.ORG, jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weirdproblems References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "M. Warner Losh" wrote: > > Confirmed. test.c appears to work properly when compiled: > > cc -o test test.c -pthread > ./test > > Generally speaking, if you want to add -lc_r, you are doing things > incorrectly. I've done way to much building... In FreeBSD 3.x you > did need to do -lc_r, but that was changed to -pthread in 4.0. > > Warner > According to the man page for gcc, you are supposed to write cc -o test test.c -pthread -D_THREAD_SAFE or am I misunderstanding something? -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 23:32:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id C681E37B419; Thu, 7 Feb 2002 23:32:49 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g187Wmi25474; Fri, 8 Feb 2002 00:32:48 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g187WkL49991; Fri, 8 Feb 2002 00:32:46 -0700 (MST) (envelope-from imp@village.org) Date: Fri, 08 Feb 2002 00:32:23 -0700 (MST) Message-Id: <20020208.003223.29577858.imp@village.org> To: stephen@math.missouri.edu Cc: sobomax@FreeBSD.ORG, jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weirdproblems From: "M. Warner Losh" In-Reply-To: <3C63773A.8DBF36F6@math.missouri.edu> References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> <3C63773A.8DBF36F6@math.missouri.edu> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <3C63773A.8DBF36F6@math.missouri.edu> Stephen Montgomery-Smith writes: : cc -o test test.c -pthread -D_THREAD_SAFE : : or am I misunderstanding something? Ah, yes. -D_THREAD_SAFE is technically needed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 23:34:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (dsl081-058-209.sfo1.dsl.speakeasy.net [64.81.58.209]) by hub.freebsd.org (Postfix) with ESMTP id 3CFAE37B417; Thu, 7 Feb 2002 23:34:34 -0800 (PST) Received: by canonware.com (Postfix, from userid 1001) id 56318F5; Thu, 7 Feb 2002 23:42:33 -0800 (PST) Date: Thu, 7 Feb 2002 23:42:33 -0800 From: Jason Evans To: Maxim Sobolev Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020207234233.D23162@canonware.com> References: <1013147180.73417.2.camel@notebook> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1013147180.73417.2.camel@notebook>; from sobomax@FreeBSD.org on Fri, Feb 08, 2002 at 07:46:34AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 07:46:34AM +0200, Maxim Sobolev wrote: > Hi, > > When working on updating port of Ximian Evolution to the latest released > version I have stuck to the problem - the new version of application > just hanged on startup on my 5-CURRENT box. After lot of digging and > debugging I found that the source of the problem is that the resulting > application had libc linked in before libc_r, which caused waitpid() in > the ORBit library just hang forever, even though child process died > almost instantly (I see zombie in the ps(1) output). When program was > relinked with -pthread flag, which seemingly forcing "right" order of > libc/libc_r (libc_r first) the problem disappeared. > > Based on the problematic code in the ORBit I had prepared short testcase > illustrating the problem and attaching it with this message. The problem > could be exposed by compiling the test.c using the following command: > > $ cc test.c -o test -lc -lc_r > > When either of -lc or -lc_r is omitted, or their order is reversed the > problem disappears. The problem doesn't exist on 4-STABLE. > > Any ideas, comments and suggestions are welcome. IIRC, Dan changed things in -current about six months ago so that -lc_r would do the right thing. Previously (and still in -stable), -pthread was necessary in order to prevent libc from being implicitly linked in. There's some magic in the compiler front end that prevents libc from being implicitly linked in if libc_r is specified. It may re-order things as well, but I'd have to look at the code to verify that. In any case, don't manually specify both, or Bad Things will happen, as you've discovered. It's my hope that we'll be able to use -lpthread by the 5.0 release, which is what the standards say should work. We could have that right now, but we've been holding off, since threads may be KSE-based by the 5.0 release. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Feb 7 23:51:50 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.viasoft.com.cn (unknown [61.153.1.177]) by hub.freebsd.org (Postfix) with ESMTP id 59C4D37B400; Thu, 7 Feb 2002 23:51:38 -0800 (PST) Received: from viasoft.com.cn (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with ESMTP id QAA18037; Fri, 8 Feb 2002 16:00:50 +0800 Message-ID: <3C63840D.3060408@viasoft.com.cn> Date: Fri, 08 Feb 2002 15:53:49 +0800 From: David Xu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Jason Evans Cc: Maxim Sobolev , jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sound like cooool, I like the libpthread hook. hahaha. -- David Xu Jason Evans wrote: >On Fri, Feb 08, 2002 at 07:46:34AM +0200, Maxim Sobolev wrote: > >>Hi, >> >>When working on updating port of Ximian Evolution to the latest released >>version I have stuck to the problem - the new version of application >>just hanged on startup on my 5-CURRENT box. After lot of digging and >>debugging I found that the source of the problem is that the resulting >>application had libc linked in before libc_r, which caused waitpid() in >>the ORBit library just hang forever, even though child process died >>almost instantly (I see zombie in the ps(1) output). When program was >>relinked with -pthread flag, which seemingly forcing "right" order of >>libc/libc_r (libc_r first) the problem disappeared. >> >>Based on the problematic code in the ORBit I had prepared short testcase >>illustrating the problem and attaching it with this message. The problem >>could be exposed by compiling the test.c using the following command: >> >>$ cc test.c -o test -lc -lc_r >> >>When either of -lc or -lc_r is omitted, or their order is reversed the >>problem disappears. The problem doesn't exist on 4-STABLE. >> >>Any ideas, comments and suggestions are welcome. >> > >IIRC, Dan changed things in -current about six months ago so that -lc_r >would do the right thing. Previously (and still in -stable), -pthread was >necessary in order to prevent libc from being implicitly linked in. >There's some magic in the compiler front end that prevents libc from being >implicitly linked in if libc_r is specified. It may re-order things as >well, but I'd have to look at the code to verify that. In any case, don't >manually specify both, or Bad Things will happen, as you've discovered. > >It's my hope that we'll be able to use -lpthread by the 5.0 release, which >is what the standards say should work. We could have that right now, but >we've been holding off, since threads may be KSE-based by the 5.0 release. > >Jason > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 0:36:44 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f125.law4.hotmail.com [216.33.149.125]) by hub.freebsd.org (Postfix) with ESMTP id 8152F37B41A for ; Fri, 8 Feb 2002 00:36:36 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 8 Feb 2002 00:36:36 -0800 Received: from 195.147.239.234 by lw4fd.law4.hotmail.msn.com with HTTP; Fri, 08 Feb 2002 08:36:36 GMT X-Originating-IP: [195.147.239.234] From: "Francis little" To: freebsd-hackers@freebsd.org Subject: suggestion/patch for ftpd Date: Fri, 08 Feb 2002 08:36:36 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 08 Feb 2002 08:36:36.0450 (UTC) FILETIME=[B869EC20:01C1B07B] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello all, i have writen a patch for ftpd that alows it to limit the number of users that log in. it currently works in daemon mode only. the user limit can be set with the option "-C". (it will through up an error if you use this option from "inetd"). If the "/etc/ftpwelcome" message is used then it will display the current/maximum number of connections after this message. If the user limit is not set then ftpd behaves as normal. below is a patch against 4.5-RELEASE.... Hope this is of use to some one... -OGGY *** /usr/src/libexec/KEEP_ME/ftpd/ftpd.c Tue Dec 18 18:35:55 2001 --- /usr/src/libexec/ftpd/ftpd.c Thu Feb 7 22:16:12 2002 *************** *** 153,158 **** --- 153,162 ---- int noretr=0; /* RETR command is disabled. */ int noguestretr=0; /* RETR command is disabled for anon users. */ + /* Two variables used for connection limiting */ + int maxusers = 0; /* maximum number of connections */ + int users = 0; /*current number of connections */ + sig_atomic_t transflag; off_t file_size; off_t byte_count; *************** *** 302,308 **** #endif /* OLD_SETPROCTITLE */ ! while ((ch = getopt(argc, argv, "AdlDESURrt:T:u:vOoa:p:46")) != -1) { switch (ch) { case 'D': daemon_mode++; --- 306,312 ---- #endif /* OLD_SETPROCTITLE */ ! while ((ch = getopt(argc, argv, "AdlDESC:URrt:T:u:vOoa:p:46")) != -1) { switch (ch) { case 'D': daemon_mode++; *************** *** 332,337 **** --- 336,349 ---- stats++; break; + /* Set the user limit */ + case 'C': + if (daemon_mode == 0) { + warnx("User limiting doesn't work from a super-server"); + } + maxusers = atoi(optarg); + break; + case 'T': maxtimeout = atoi(optarg); if (timeout > maxtimeout) *************** *** 507,512 **** --- 519,530 ---- while (1) { addrlen = server_addr.su_len; fd = accept(ctl_sock, (struct sockaddr *)&his_addr, &addrlen); + + /* We have a connection...*/ + if (maxusers != 0) { + users++; + } + if (fork() == 0) { /* child */ (void) dup2(fd, 0); *************** *** 591,596 **** --- 609,621 ---- reply(530, "System not available."); exit(0); } + + /* Are there are toomany users....*/ + if (maxusers != 0 && daemon_mode != 0 && users > maxusers) { + reply(421, "There are toomany users logged in. The maximum is: %lu", maxusers); + dologout(0); + } + #ifdef VIRTUAL_HOSTING if ((fd = fopen(thishost->welcome, "r")) != NULL) { #else *************** *** 601,606 **** --- 626,636 ---- *cp = '\0'; lreply(220, "%s", line); } + /* Lets tell them how many people are on...*/ + if (maxusers != 0 && daemon_mode != 0){ + lreply(230, "There are %lu users out of %lu logged in.", users, maxusers); + } + (void) fflush(stdout); (void) fclose(fd); /* reply(220,) must follow */ *************** *** 2778,2783 **** --- 2808,2819 ---- int signo; { while (wait3(NULL, WNOHANG, NULL) > 0); + + /* We'd better update when someone has gone...*/ + if (users !=0) { + users--; + } + } #ifdef OLD_SETPROCTITLE _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1: 1: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ms22.hinet.net (ms22.hinet.net [168.95.4.22]) by hub.freebsd.org (Postfix) with ESMTP id E7B5A37B421; Fri, 8 Feb 2002 01:00:52 -0800 (PST) Received: from work-test (61-217-200-28.HINET-IP.hinet.net [61.217.200.28]) by ms22.hinet.net (8.8.8/8.8.8) with SMTP id QAA15389; Fri, 8 Feb 2002 16:59:59 +0800 (CST) Date: Fri, 8 Feb 2002 16:59:59 +0800 (CST) Message-Id: <200202080859.QAA15389@ms22.hinet.net> From: ¯uªº¥i¥HÁÈ¿ú@ms22.hinet.net To: ¤p¶®@ms22.hinet.net Subject: ³Ð·~­Ý¾ªº¨}¾÷ X-Mailer: b0OYzTJn5PD6KiNoE91tj2ZA Content-Type: text/plain; Content-Transfer-Encoding: Quoted-Printable X-Priority: 3 X-MSMail-Priority: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG =A5=A2=B1=D1=AA=BA=A4H=A7=E4=C2=C7=A4f=A1A =A6=A8=A5\=AA=BA=A4H=A7=E4=A4=E8=AAk=A1I =A6=DB=A4v=A4=A3=AA=A7=AE=F0=A1A=A6=D1=A4=D1=A4]=B5L=A9`=A1I =A6=DB=A4v=A6=B3=A7=D3=AE=F0=A1A=B8U=C3=F8=A5i=AC=F0=AF}=A1I http://free168.com/goodshop/ http://run.to/goodshop/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1:17:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 24DE637B494; Fri, 8 Feb 2002 01:17:11 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA65316; Fri, 8 Feb 2002 11:17:01 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h8.234.dialup.iptcom.net [212.9.234.8]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA50085; Fri, 8 Feb 2002 11:16:59 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g189FRd67801; Fri, 8 Feb 2002 11:15:27 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63973F.111CF6D1@FreeBSD.org> Date: Fri, 08 Feb 2002 11:15:43 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <3C637097.13B8C35A@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Maxim Sobolev wrote: > > $ cc test.c -o test -lc -lc_r > > > > When either of -lc or -lc_r is omitted, or their order is reversed the > > problem disappears. The problem doesn't exist on 4-STABLE. > > > > Any ideas, comments and suggestions are welcome. > > Symbols are resolved from libraries in the order in which > they are specified to the linker. > > So the fix is obvious: specify them in the right order. > > Linux doesn't see this because libc_r is just there for > the reentrant calls, and their threading uses processes, > instead of a user space ("quantum conservation") scheduler. All not as easy as it seems to be. -lc could come not from the command line, but from one of the other libraries the binary being linked with. Therefore, in real life resolving this problem could be a little more tricky, especially with large applications (e.g. Evolution), that uses code from 30+ shared libraries. I think that ld(1) should be smart enough to reorder libc/libc_r so that libc_r is always linked before libc. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1:19:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id BE6DE37B41D; Fri, 8 Feb 2002 01:19:26 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA67366; Fri, 8 Feb 2002 11:19:05 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h8.234.dialup.iptcom.net [212.9.234.8]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA51227; Fri, 8 Feb 2002 11:19:02 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g189IVd67826; Fri, 8 Feb 2002 11:18:31 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C6397F8.CC02F78C@FreeBSD.org> Date: Fri, 08 Feb 2002 11:18:48 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: "M. Warner Losh" Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weirdproblems References: <1013147180.73417.2.camel@notebook> <20020207.234721.71750312.imp@village.org> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "M. Warner Losh" wrote: > > In message: <1013147180.73417.2.camel@notebook> > Maxim Sobolev writes: > : Based on the problematic code in the ORBit I had prepared short testcase > : illustrating the problem and attaching it with this message. The problem > : could be exposed by compiling the test.c using the following command: > : > : $ cc test.c -o test -lc -lc_r > > cc test.c -o test -pthread > > If that doesn't work, test.c is broken :-) Hmm, as far as I understand in current -pthread is being slowly deorbited (replaced with just -lc_r), but this could lead to a problem when some of other libraries the binary being linked with contains explicit dependency to libc. I think that ld(1) should be smart enough to reorder libc/libc_r so that libc_r is always linked before libc. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1:20:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id CD6E237B404; Fri, 8 Feb 2002 01:20:06 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA68229; Fri, 8 Feb 2002 11:19:57 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h8.234.dialup.iptcom.net [212.9.234.8]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA51633; Fri, 8 Feb 2002 11:19:55 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g189JHd67830; Fri, 8 Feb 2002 11:19:17 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C639825.241BEB27@FreeBSD.org> Date: Fri, 08 Feb 2002 11:19:33 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: "M. Warner Losh" Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weirdproblems References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "M. Warner Losh" wrote: > > Confirmed. test.c appears to work properly when compiled: > > cc -o test test.c -pthread > ./test > > Generally speaking, if you want to add -lc_r, you are doing things > incorrectly. I've done way to much building... In FreeBSD 3.x you > did need to do -lc_r, but that was changed to -pthread in 4.0. And AFAIK then was changed back to -lc_r in 5.0... -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1:21:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 34A0D37B404; Fri, 8 Feb 2002 01:20:58 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA69047; Fri, 8 Feb 2002 11:20:38 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h8.234.dialup.iptcom.net [212.9.234.8]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA51966; Fri, 8 Feb 2002 11:20:36 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g189K4d67837; Fri, 8 Feb 2002 11:20:04 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C639855.DA710095@FreeBSD.org> Date: Fri, 08 Feb 2002 11:20:21 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Stephen Montgomery-Smith Cc: "M. Warner Losh" , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weirdproblems References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> <3C63773A.8DBF36F6@math.missouri.edu> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > "M. Warner Losh" wrote: > > > > Confirmed. test.c appears to work properly when compiled: > > > > cc -o test test.c -pthread > > ./test > > > > Generally speaking, if you want to add -lc_r, you are doing things > > incorrectly. I've done way to much building... In FreeBSD 3.x you > > did need to do -lc_r, but that was changed to -pthread in 4.0. > > > > Warner > > > > According to the man page for gcc, you are supposed to write > > cc -o test test.c -pthread -D_THREAD_SAFE > > or am I misunderstanding something? In 5.0-CURRENT -pthread was replaced by -lc_r. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 1:31:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 0982B37B423; Fri, 8 Feb 2002 01:31:28 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA79810; Fri, 8 Feb 2002 11:31:06 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h76.229.dialup.iptcom.net [212.9.229.76]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA57396; Fri, 8 Feb 2002 11:31:03 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g189TVd67864; Fri, 8 Feb 2002 11:29:31 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C639A8C.6D100326@FreeBSD.org> Date: Fri, 08 Feb 2002 11:29:48 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Jason Evans Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Evans wrote: > > On Fri, Feb 08, 2002 at 07:46:34AM +0200, Maxim Sobolev wrote: > > Hi, > > > > When working on updating port of Ximian Evolution to the latest released > > version I have stuck to the problem - the new version of application > > just hanged on startup on my 5-CURRENT box. After lot of digging and > > debugging I found that the source of the problem is that the resulting > > application had libc linked in before libc_r, which caused waitpid() in > > the ORBit library just hang forever, even though child process died > > almost instantly (I see zombie in the ps(1) output). When program was > > relinked with -pthread flag, which seemingly forcing "right" order of > > libc/libc_r (libc_r first) the problem disappeared. > > > > Based on the problematic code in the ORBit I had prepared short testcase > > illustrating the problem and attaching it with this message. The problem > > could be exposed by compiling the test.c using the following command: > > > > $ cc test.c -o test -lc -lc_r > > > > When either of -lc or -lc_r is omitted, or their order is reversed the > > problem disappears. The problem doesn't exist on 4-STABLE. > > > > Any ideas, comments and suggestions are welcome. > > IIRC, Dan changed things in -current about six months ago so that -lc_r > would do the right thing. Previously (and still in -stable), -pthread was > necessary in order to prevent libc from being implicitly linked in. > There's some magic in the compiler front end that prevents libc from being > implicitly linked in if libc_r is specified. It may re-order things as > well, but I'd have to look at the code to verify that. In any case, don't > manually specify both, or Bad Things will happen, as you've discovered. I don't (this was just a testcase). In real life it was really unclear where that libc came from, because there were no -lc in the command line and no of the shared libraries specified contained explicit libc dependency (at least according to ldd(1)). > It's my hope that we'll be able to use -lpthread by the 5.0 release, which > is what the standards say should work. We could have that right now, but > we've been holding off, since threads may be KSE-based by the 5.0 release. That would be nice, but we have a real problem at hand. As I said, I think that ld(1) should be smart enough to reorder libc/libc_r so that libc_r is always linked before libc. This is clearly not the case right now. Unfortunately there is no easy way to reproduce this, but if you have some spare CPU cycles try to remore explicit -pthread from ports/mail/evolution/Makefile, build the port on -current and do `ldd /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r was. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 2:18:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 6DFE137B416; Fri, 8 Feb 2002 02:18:06 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16Z86I-0007MW-00; Fri, 08 Feb 2002 02:17:55 -0800 Message-ID: <3C63A4C1.7C2CEEDF@mindspring.com> Date: Fri, 08 Feb 2002 02:13:21 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <3C637097.13B8C35A@mindspring.com> <3C63973F.111CF6D1@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: [...] > > Symbols are resolved from libraries in the order in which > > they are specified to the linker. > > > > So the fix is obvious: specify them in the right order. [...] > All not as easy as it seems to be. -lc could come not from the command > line, but from one of the other libraries the binary being linked > with. Therefore, in real life resolving this problem could be a little > more tricky, especially with large applications (e.g. Evolution), that > uses code from 30+ shared libraries. I think that ld(1) should be > smart enough to reorder libc/libc_r so that libc_r is always linked > before libc. Excuse me. Even assuming it were possible to order libraries so that certain libraries were considered "weak" and others were considered "strong" by their symbol tagging alone, you can *not* fix this wherne there are two libraries, or a mutual precedence order issue. How in the heck does it get the Xll libraries linked in the correct -lXt -lXext -lX11 order, if not by specifying them in the correct order? It's really, really stupid to make an assumption about libc_r that you can't even make on Linux with regards to X11/Xext/Xt, just because some software had the misfortune to be born on the wrong side of the autoconf tracks. Code protability is an attribute of the code, not of the environment where the code is linked. You might as well assume that you are going to reorder the dependency graph for template virtual base clases to their dependency order instead of their link order for something like ACAP (ACAP didn't used to compile with g++ until Jeremy Allison and I hacked it into submission, and away from bad assumptions, like that one, or certain spacing of underscores in declarations). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 2:23:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 1EFD637B422; Fri, 8 Feb 2002 02:23:25 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 16Z8Bb-0001wd-00; Fri, 08 Feb 2002 02:23:22 -0800 Message-ID: <3C63A62D.3E4A4FC4@mindspring.com> Date: Fri, 08 Feb 2002 02:19:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > That would be nice, but we have a real problem at hand. As I said, I > think that ld(1) should be smart enough to reorder libc/libc_r so that > libc_r is always linked before libc. This is clearly not the case > right now. Unfortunately there is no easy way to reproduce this, but > if you have some spare CPU cycles try to remore explicit -pthread from > ports/mail/evolution/Makefile, build the port on -current and do `ldd > /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes > libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r > was. You aren't including the linker lines for the libraries specified before the -lc_r (which may themselves be linked against libc.so instead of libc_r.so, which is wrong), and you aren't including the final link line. See the recent patch to ldd to make it work against .so libraries (unfortunately, it's only in -current, not yet in -stable). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 2:49:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id BA53237B419; Fri, 8 Feb 2002 02:49:14 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA56455; Fri, 8 Feb 2002 12:48:52 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h144.229.dialup.iptcom.net [212.9.229.144]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id MAA96276; Fri, 8 Feb 2002 12:48:49 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18AmId68076; Fri, 8 Feb 2002 12:48:18 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63AD02.79BA5AF5@FreeBSD.org> Date: Fri, 08 Feb 2002 12:48:34 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Maxim Sobolev wrote: > > That would be nice, but we have a real problem at hand. As I said, I > > think that ld(1) should be smart enough to reorder libc/libc_r so that > > libc_r is always linked before libc. This is clearly not the case > > right now. Unfortunately there is no easy way to reproduce this, but > > if you have some spare CPU cycles try to remore explicit -pthread from > > ports/mail/evolution/Makefile, build the port on -current and do `ldd > > /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes > > libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r > > was. > > You aren't including the linker lines for the libraries > specified before the -lc_r (which may themselves be linked > against libc.so instead of libc_r.so, which is wrong), > and you aren't including the final link line. > > See the recent patch to ldd to make it work against .so > libraries (unfortunately, it's only in -current, not yet > in -stable). Heh, actually I'm an author of that patch. :))) -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 3: 7:36 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 0F5F337B419; Fri, 8 Feb 2002 03:07:21 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA72063; Fri, 8 Feb 2002 13:07:11 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h144.229.dialup.iptcom.net [212.9.229.144]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id NAA04689; Fri, 8 Feb 2002 13:07:09 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18B6bd68109; Fri, 8 Feb 2002 13:06:37 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63B14E.516941C4@FreeBSD.org> Date: Fri, 08 Feb 2002 13:06:54 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <3C637097.13B8C35A@mindspring.com> <3C63973F.111CF6D1@FreeBSD.org> <3C63A4C1.7C2CEEDF@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Maxim Sobolev wrote: > [...] > > > Symbols are resolved from libraries in the order in which > > > they are specified to the linker. > > > > > > So the fix is obvious: specify them in the right order. > [...] > > All not as easy as it seems to be. -lc could come not from the command > > line, but from one of the other libraries the binary being linked > > with. Therefore, in real life resolving this problem could be a little > > more tricky, especially with large applications (e.g. Evolution), that > > uses code from 30+ shared libraries. I think that ld(1) should be > > smart enough to reorder libc/libc_r so that libc_r is always linked > > before libc. > > Excuse me. > > Even assuming it were possible to order libraries so that > certain libraries were considered "weak" and others were > considered "strong" by their symbol tagging alone, you can > *not* fix this wherne there are two libraries, or a mutual > precedence order issue. > > How in the heck does it get the Xll libraries linked in the > correct -lXt -lXext -lX11 order, if not by specifying them > in the correct order? When you are linking with shared libraries you do not need to specify them in the "correct" order, because AFAIK linker takes care of that using dependency information recorded within each shared library. Correct order only required for static libraries that do not have a way to record a dependency information. -Maxim > It's really, really stupid to make an assumption about libc_r > that you can't even make on Linux with regards to X11/Xext/Xt, > just because some software had the misfortune to be born on > the wrong side of the autoconf tracks. > > Code protability is an attribute of the code, not of the > environment where the code is linked. > > You might as well assume that you are going to reorder the > dependency graph for template virtual base clases to their > dependency order instead of their link order for something > like ACAP (ACAP didn't used to compile with g++ until > Jeremy Allison and I hacked it into submission, and away > from bad assumptions, like that one, or certain spacing of > underscores in declarations). > > -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 3:42:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 5EED637B404; Fri, 8 Feb 2002 03:42:33 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16Z9Q8-0001R4-00; Fri, 08 Feb 2002 03:42:24 -0800 Message-ID: <3C63B898.65E99472@mindspring.com> Date: Fri, 08 Feb 2002 03:38:00 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <3C637097.13B8C35A@mindspring.com> <3C63973F.111CF6D1@FreeBSD.org> <3C63A4C1.7C2CEEDF@mindspring.com> <3C63B14E.516941C4@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > When you are linking with shared libraries you do not need to specify > them in the "correct" order, because AFAIK linker takes care of that > using dependency information recorded within each shared library. > Correct order only required for static libraries that do not have a > way to record a dependency information. Libraries are not all int he same dependency space. It's possible to have a shared library that is linked against libc_r.so.3, and have the rest of the program linked against libc.so.4 (e.g. if there were a .init that started a thread in the library when the program was invoked, in order to service requests made via an IPC, also defined by the library). Likewise, it's possible for different interface versions to coexist in a program, so long as there are no relied upon interactions (e.g. a static buffer being blown by one thread for use by another). The relationship between libraries is not flat, it's hierarchical, or at least is supposed to be able to be, according to the ELF spec.. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 5:39:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by hub.freebsd.org (Postfix) with ESMTP id 55BAA37B419 for ; Fri, 8 Feb 2002 05:39:37 -0800 (PST) Received: from fwd11.sul.t-online.de by mailout11.sul.t-online.com with smtp id 16ZBFY-0001pR-00; Fri, 08 Feb 2002 14:39:36 +0100 Received: from mail.net (340061203289-0001@[217.227.56.181]) by fmrl11.sul.t-online.com with esmtp id 16ZBFU-0zukkKC; Fri, 8 Feb 2002 14:39:32 +0100 Received: from gateway.schuett-inhouse.de (localhost [127.0.0.1]) by mail.net (8.11.1/8.11.1) with ESMTP id g18DUv058284 for ; Fri, 8 Feb 2002 14:30:57 +0100 (CET) (envelope-from titus@schuett-inhouse.de) Received: from schuett-inhouse.de (kd.schuett-inhouse.de [192.168.3.3]) by gateway.schuett-inhouse.de (8.11.1/8.11.1) with ESMTP id g18DSE358230 for ; Fri, 8 Feb 2002 14:28:14 +0100 (CET) (envelope-from titus@schuett-inhouse.de) Message-ID: <3C63D6AD.475263AC@schuett-inhouse.de> Date: Fri, 08 Feb 2002 14:46:21 +0100 From: Titus von Boxberg X-Mailer: Mozilla 4.78 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: tcdrain won't work? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340061203289-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I tried to use tcdrain to make sure that all characters are sent via a COM port but it seems that it won't work in about 50% of the calls to it, i.e. tcdrain returns before all characters are sent via sio.c. Has anyone noticed that effect? I tried to understand how it works. Apparently tty.c operates in ttywait() and ttwwakeup() on the output queue size in tp->t_outq.c_cc and TS_BUSY in tp->t_state (?). I can't find any piece of code filling tp->t_outq.c_cc with other values than 0. And sio.c seems to not set TS_BUSY in tp if outq.c_cc is not 0. Is it simply unimplemented or have I missed the point? Thanks in advance! Titus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 5:56:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 37C6A37B41E; Fri, 8 Feb 2002 05:56:37 -0800 (PST) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g18Duaf8028675; Fri, 8 Feb 2002 08:56:36 -0500 (EST) Date: Fri, 8 Feb 2002 08:56:36 -0500 (EST) From: Daniel Eischen To: Maxim Sobolev Cc: Terry Lambert , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems In-Reply-To: <3C63973F.111CF6D1@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Feb 2002, Maxim Sobolev wrote: > Terry Lambert wrote: > > > > Maxim Sobolev wrote: > > > $ cc test.c -o test -lc -lc_r > > > > > > When either of -lc or -lc_r is omitted, or their order is reversed the > > > problem disappears. The problem doesn't exist on 4-STABLE. > > > > > > Any ideas, comments and suggestions are welcome. > > > > Symbols are resolved from libraries in the order in which > > they are specified to the linker. > > > > So the fix is obvious: specify them in the right order. > > > > Linux doesn't see this because libc_r is just there for > > the reentrant calls, and their threading uses processes, > > instead of a user space ("quantum conservation") scheduler. > > All not as easy as it seems to be. -lc could come not from the command > line, but from one of the other libraries the binary being linked > with. Therefore, in real life resolving this problem could be a little > more tricky, especially with large applications (e.g. Evolution), that > uses code from 30+ shared libraries. I think that ld(1) should be > smart enough to reorder libc/libc_r so that libc_r is always linked > before libc. As you've found out, you have to link libc_r first. You shouldn't even specify -lc because the linker will automatically pull that in correctly. I don't think we should even try to support linking libc before libc_r or libpthread. The linker is working the way it is suppose to. Get the Evolution guys to fix the way it is built... -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 6:34:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from artemis.drwilco.net (diana.drwilco.net [66.48.127.79]) by hub.freebsd.org (Postfix) with ESMTP id 71FFE37B405 for ; Fri, 8 Feb 2002 06:34:39 -0800 (PST) Received: from 208.133.128.5 (nobody@localhost [127.0.0.1]) by artemis.drwilco.net (8.11.6/8.11.6) with SMTP id g18EYTY90323; Fri, 8 Feb 2002 09:34:29 -0500 (EST) (envelope-from drwilco@drwilco.net) Message-ID: X-Mailer: BasiliX 1.1.0 -- http://basilix.org X-SenderIP: 208.133.128.5 Date: Fri, 08 Feb 2002 09:34:29 EST From: "Rogier R. Mulhuijzen" Reply-To: "Rogier R. Mulhuijzen" Subject: Re: Re[4]: natd UDP errors with PPP demand dial To: "Anikin" Cc: dwhite@resnet.uoregon.edu Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I think I have to stick with the conventional setup, and go back to > trying to answer my original questions: > > 1. Why is the machine trying to send packets to its own previous IP? > 2. How do I stop that? 1) Maybe the IP change isn't getting through to natd like it should. 2) Have ppp kill -9 natd on link down and start natd on linkup. Doc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 6:37:24 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from math.missouri.edu (math.missouri.edu [128.206.49.180]) by hub.freebsd.org (Postfix) with ESMTP id 3261B37B417; Fri, 8 Feb 2002 06:37:18 -0800 (PST) Received: from math.missouri.edu (cauchy.math.missouri.edu [128.206.49.166]) by math.missouri.edu (8.11.6/8.11.6) with ESMTP id g18EbGu59001; Fri, 8 Feb 2002 08:37:16 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <3C63E297.F90D5E82@math.missouri.edu> Date: Fri, 08 Feb 2002 08:37:11 -0600 From: Stephen Montgomery-Smith Organization: University of Missouri X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: "M. Warner Losh" Cc: sobomax@FreeBSD.ORG, jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causesweirdproblems References: <1013147180.73417.2.camel@notebook> <20020207.234939.69060047.imp@village.org> <3C63773A.8DBF36F6@math.missouri.edu> <20020208.003223.29577858.imp@village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "M. Warner Losh" wrote: > > In message: <3C63773A.8DBF36F6@math.missouri.edu> > Stephen Montgomery-Smith writes: > : cc -o test test.c -pthread -D_THREAD_SAFE > : > : or am I misunderstanding something? > > Ah, yes. -D_THREAD_SAFE is technically needed. > I am curious - what are the possible consequences if you forget to include -D_THREAD_SAFE? I have done many compilations having forgotten to include this flag, with no obvious problems. Did I just get lucky? -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 6:42:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 4B6D937B41A; Fri, 8 Feb 2002 06:41:47 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g18EfWp93830; Fri, 8 Feb 2002 16:41:32 +0200 (EET) (envelope-from ru) Date: Fri, 8 Feb 2002 16:41:32 +0200 From: Ruslan Ermilov To: Maxim Sobolev Cc: Terry Lambert , Jason Evans , jdp@FreeBSD.ORG, deischen@FreeBSD.ORG, jasone@FreeBSD.ORG, hackers@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020208164132.D78163@sunbay.com> References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C63AD02.79BA5AF5@FreeBSD.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 12:48:34PM +0200, Maxim Sobolev wrote: > Terry Lambert wrote: > > > > Maxim Sobolev wrote: > > > That would be nice, but we have a real problem at hand. As I said, I > > > think that ld(1) should be smart enough to reorder libc/libc_r so that > > > libc_r is always linked before libc. This is clearly not the case > > > right now. Unfortunately there is no easy way to reproduce this, but > > > if you have some spare CPU cycles try to remore explicit -pthread from > > > ports/mail/evolution/Makefile, build the port on -current and do `ldd > > > /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes > > > libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r > > > was. > > When you say ld(1), are you perhaps mean rtld-elf.so.1 (aka rtld(1))? ld(1) only _links_ when static linkage was requested (which is not the case here), or writes dynamic dependencies on shared objects. > > You aren't including the linker lines for the libraries > > specified before the -lc_r (which may themselves be linked > > against libc.so instead of libc_r.so, which is wrong), > > and you aren't including the final link line. > > > > See the recent patch to ldd to make it work against .so > > libraries (unfortunately, it's only in -current, not yet > > in -stable). > > Heh, actually I'm an author of that patch. :))) > *LOL* Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 6:51:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id C220C37B41E; Fri, 8 Feb 2002 06:51:25 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA85404; Fri, 8 Feb 2002 16:51:20 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h71.228.dialup.iptcom.net [212.9.228.71]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id QAA19646; Fri, 8 Feb 2002 16:51:14 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18Eogd69154; Fri, 8 Feb 2002 16:50:42 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63E5D1.1E423698@FreeBSD.org> Date: Fri, 08 Feb 2002 16:50:57 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Ruslan Ermilov Cc: Terry Lambert , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > On Fri, Feb 08, 2002 at 12:48:34PM +0200, Maxim Sobolev wrote: > > Terry Lambert wrote: > > > > > > Maxim Sobolev wrote: > > > > That would be nice, but we have a real problem at hand. As I said, I > > > > think that ld(1) should be smart enough to reorder libc/libc_r so that > > > > libc_r is always linked before libc. This is clearly not the case > > > > right now. Unfortunately there is no easy way to reproduce this, but > > > > if you have some spare CPU cycles try to remore explicit -pthread from > > > > ports/mail/evolution/Makefile, build the port on -current and do `ldd > > > > /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes > > > > libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r > > > > was. > > > > When you say ld(1), are you perhaps mean rtld-elf.so.1 (aka rtld(1))? > ld(1) only _links_ when static linkage was requested (which is not the > case here), or writes dynamic dependencies on shared objects. No, I meant ld(1). The problem here is that in the case when libc is recorded before libc_r in dynamic dependencies list the resulting executable may not work correctly (see my testcase). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:12:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 46A6637B41B; Fri, 8 Feb 2002 07:12:24 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZCh5-00006K-00; Fri, 08 Feb 2002 07:12:19 -0800 Message-ID: <3C63E961.45706408@mindspring.com> Date: Fri, 08 Feb 2002 07:06:09 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > No, I meant ld(1). The problem here is that in the case when libc is > recorded before libc_r in dynamic dependencies list the resulting > executable may not work correctly (see my testcase). Patient: "Doctor, it hurts when I record libc before libc_r in the dynamic dependencies list!" Doctor: [expected response] 8-). Seriously, the "Evolution" build process is seriously broken; it works on Linux because Linux has a simple threads implementation, rather than an efficient one. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:17: 3 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id D380437B423 for ; Fri, 8 Feb 2002 07:16:36 -0800 (PST) Received: (qmail 4456 invoked from network); 8 Feb 2002 15:16:35 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.155.67]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Feb 2002 15:16:35 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3C639855.DA710095@FreeBSD.org> Date: Fri, 08 Feb 2002 10:16:32 -0500 (EST) From: John Baldwin To: Maxim Sobolev Subject: Re: Linking libc before libc_r into application causes weirdprob Cc: jlemon@FreeBSD.org, hackers@FreeBSD.org, jasone@FreeBSD.org, deischen@FreeBSD.org, jdp@FreeBSD.org, "M. Warner Losh" , Stephen Montgomery-Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Feb-02 Maxim Sobolev wrote: > Stephen Montgomery-Smith wrote: >> >> "M. Warner Losh" wrote: >> > >> > Confirmed. test.c appears to work properly when compiled: >> > >> > cc -o test test.c -pthread >> > ./test >> > >> > Generally speaking, if you want to add -lc_r, you are doing things >> > incorrectly. I've done way to much building... In FreeBSD 3.x you >> > did need to do -lc_r, but that was changed to -pthread in 4.0. >> > >> > Warner >> > >> >> According to the man page for gcc, you are supposed to write >> >> cc -o test test.c -pthread -D_THREAD_SAFE >> >> or am I misunderstanding something? > > In 5.0-CURRENT -pthread was replaced by -lc_r. No, that's just how it is currently implemented. Ultimately it will be -lpthread. And when that happens, you will need to link -lpthread in before -lc just like you would need to now with -lc_r. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:23:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 1335537B402; Fri, 8 Feb 2002 07:22:55 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g18FMbJ01007; Fri, 8 Feb 2002 17:22:37 +0200 (EET) (envelope-from ru) Date: Fri, 8 Feb 2002 17:22:37 +0200 From: Ruslan Ermilov To: Maxim Sobolev Cc: Terry Lambert , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020208172237.G78163@sunbay.com> References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C63E5D1.1E423698@FreeBSD.org> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 04:50:57PM +0200, Maxim Sobolev wrote: > Ruslan Ermilov wrote: > > > > On Fri, Feb 08, 2002 at 12:48:34PM +0200, Maxim Sobolev wrote: > > > Terry Lambert wrote: > > > > > > > > Maxim Sobolev wrote: > > > > > That would be nice, but we have a real problem at hand. As I said, I > > > > > think that ld(1) should be smart enough to reorder libc/libc_r so that > > > > > libc_r is always linked before libc. This is clearly not the case > > > > > right now. Unfortunately there is no easy way to reproduce this, but > > > > > if you have some spare CPU cycles try to remore explicit -pthread from > > > > > ports/mail/evolution/Makefile, build the port on -current and do `ldd > > > > > /usr/X11R6/bin/evolution'. You will see that libc.so.X precedes > > > > > libc_r.so.X, even though -lc wasn't supplied to a linker, while -lc_r > > > > > was. > > > > > > When you say ld(1), are you perhaps mean rtld-elf.so.1 (aka rtld(1))? > > ld(1) only _links_ when static linkage was requested (which is not the > > case here), or writes dynamic dependencies on shared objects. > > No, I meant ld(1). The problem here is that in the case when libc is > recorded before libc_r in dynamic dependencies list the resulting > executable may not work correctly (see my testcase). > Sorry, but I don't get it. I can't reproduce it other than specifying -lc explicitly. For example, -lssh now depends on -lcrypto and -lz, in that order. Attempting to link a program with -lc_r -lssh gives, in that order: libc_r.so.5 => /usr/lib/libc_r.so.5 (0x28065000) libssh.so.2 => /usr/lib/libssh.so.2 (0x28083000) libc.so.5 => /usr/lib/libc.so.5 (0x280b2000) libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x28168000) libz.so.2 => /usr/lib/libz.so.2 (0x28223000) The primary dependecies come first, then secondaries. I can only imagine the situation where libc.so comes before libc_r.so if some library has a (bogus) explicit dependency on libc.so. How does ldd(1) output in question looks like, the full version? Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:26:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 46FD037B417; Fri, 8 Feb 2002 07:26:15 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g18FP3j01578; Fri, 8 Feb 2002 17:25:03 +0200 (EET) (envelope-from ru) Date: Fri, 8 Feb 2002 17:25:03 +0200 From: Ruslan Ermilov To: Terry Lambert Cc: Maxim Sobolev , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020208172503.H78163@sunbay.com> References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C63E961.45706408@mindspring.com> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 07:06:09AM -0800, Terry Lambert wrote: > Maxim Sobolev wrote: > > No, I meant ld(1). The problem here is that in the case when libc is > > recorded before libc_r in dynamic dependencies list the resulting > > executable may not work correctly (see my testcase). > > Patient: "Doctor, it hurts when I record libc before libc_r > in the dynamic dependencies list!" > > Doctor: [expected response] > > 8-). > > Seriously, the "Evolution" build process is seriously > broken; it works on Linux because Linux has a simple > threads implementation, rather than an efficient one. > Doctor's Assistant: "No library should ever have an explicit dependency on libc". Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:48:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2C42D37B41A; Fri, 8 Feb 2002 07:48:36 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g18FmYi27318; Fri, 8 Feb 2002 08:48:34 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g18FmXL52162; Fri, 8 Feb 2002 08:48:33 -0700 (MST) (envelope-from imp@village.org) Date: Fri, 08 Feb 2002 08:48:04 -0700 (MST) Message-Id: <20020208.084804.107944591.imp@village.org> To: sobomax@FreeBSD.org Cc: stephen@math.missouri.edu, jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weirdproblems From: "M. Warner Losh" In-Reply-To: <3C639855.DA710095@FreeBSD.org> References: <20020207.234939.69060047.imp@village.org> <3C63773A.8DBF36F6@math.missouri.edu> <3C639855.DA710095@FreeBSD.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <3C639855.DA710095@FreeBSD.org> Maxim Sobolev writes: : In 5.0-CURRENT -pthread was replaced by -lc_r. But in 5.0 -pthread still works :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:52:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id D672D37B428; Fri, 8 Feb 2002 07:51:53 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA40895; Fri, 8 Feb 2002 17:51:47 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h71.228.dialup.iptcom.net [212.9.228.71]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id RAA49684; Fri, 8 Feb 2002 17:51:42 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18FpBd69318; Fri, 8 Feb 2002 17:51:11 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63F3FE.D4E73334@FreeBSD.org> Date: Fri, 08 Feb 2002 17:51:26 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Ruslan Ermilov Cc: Terry Lambert , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> Content-Type: multipart/mixed; boundary="------------1016F4DCC774CCCF248737AF" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1016F4DCC774CCCF248737AF Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Ruslan Ermilov wrote: > > On Fri, Feb 08, 2002 at 07:06:09AM -0800, Terry Lambert wrote: > > Maxim Sobolev wrote: > > > No, I meant ld(1). The problem here is that in the case when libc is > > > recorded before libc_r in dynamic dependencies list the resulting > > > executable may not work correctly (see my testcase). > > > > Patient: "Doctor, it hurts when I record libc before libc_r > > in the dynamic dependencies list!" > > > > Doctor: [expected response] > > > > 8-). > > > > Seriously, the "Evolution" build process is seriously > > broken; it works on Linux because Linux has a simple > > threads implementation, rather than an efficient one. > > > Doctor's Assistant: "No library should ever have an explicit > dependency on libc". But no library has it here! libc comes out of blue just before libc_r - see attached script. Perhaps I'm missing something, but I can't figure out where it comes from, could you? -Maxim --------------1016F4DCC774CCCF248737AF Content-Type: text/plain; charset=x-user-defined; name="log" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="log" Script started on Fri Feb 8 17:41:11 2002 root@notebook# gmake Making all in glade gmake[1]: =F7=C8=CF=C4 =D7 =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/usr/port= s/mail/evolution/work/evolution-1.0.2/shell/glade' gmake[1]: =E3=C5=CC=D8 `all' =CE=C5 =D4=D2=C5=C2=D5=C5=D4 =D7=D9=D0=CF=CC= =CE=C5=CE=C9=D1 =CB=CF=CD=C1=CE=C4. gmake[1]: =F7=D9=C8=CF=C4 =C9=DA =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/us= r/ports/mail/evolution/work/evolution-1.0.2/shell/glade' Making all in importer gmake[1]: =F7=C8=CF=C4 =D7 =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/usr/port= s/mail/evolution/work/evolution-1.0.2/shell/importer' gmake[1]: =E3=C5=CC=D8 `all' =CE=C5 =D4=D2=C5=C2=D5=C5=D4 =D7=D9=D0=CF=CC= =CE=C5=CE=C9=D1 =CB=CF=CD=C1=CE=C4. gmake[1]: =F7=D9=C8=CF=C4 =C9=DA =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/us= r/ports/mail/evolution/work/evolution-1.0.2/shell/importer' gmake[1]: =F7=C8=CF=C4 =D7 =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/usr/port= s/mail/evolution/work/evolution-1.0.2/shell' /bin/sh ../libtool --mode=3Dlink cc -pipe -O -mpreferred-stack-boundary=3D= 2 -march=3Dpentium -I/usr/X11R6/include -Wall -Wunused -L/usr/X11R6/lib = -o evolution e-activity-handler.o e-component-registry.o e-corba-shortcu= ts.o e-corba-storage-registry.o e-corba-storage.o e-folder-type-registry.= o e-folder.o e-gray-bar.o e-local-folder.o e-local-storage.o e-setup.o e-= shell-about-box.o e-shell-folder-commands.o e-shell-folder-creation-dialo= g.o e-shell-folder-selection-dialog.o e-shell-folder-title-bar.o e-shell-= importer.o e-shell-offline-handler.o e-shell-startup-wizard.o e-shell-use= r-creatable-items-handler.o e-shell-utils.o e-shell-view-menu.o e-shell-v= iew.o e-shell.o e-shortcuts-view-model.o e-shortcuts-view.o e-shortcuts.o= e-splash.o e-storage-set-view.o e-storage-set.o e-storage.o e-summary-st= orage.o e-task-bar.o e-task-widget.o e-uri-schema-registry.o evolution-st= orage-set-view.o evolution-storage-set-view-factory.o main.o libeshell.la= importer/libevolution-importer.la ../widgets/e-timezone-dialog/= libetimezonedialog.a ../widgets/misc/libemiscwidgets.a ../e-util/libeu= til.la ../libical/src/libical/libical-evolution.la -Wl,-E -L/usr/X11R= 6/lib -L/usr/local/lib -lgal -lgnomeprint -lfreetype -lglade-gnome -lglad= e -lxml -lXpm -ljpeg -lgnomeui -lart_lgpl -lgdk_imlib -ltiff -lungif -lpn= g -lz -lSM -lICE -lgnome -lgnomesupport -lesd -laudiofile -lgdk_pixbuf -l= gtk12 -lgdk12 -lgmodule12 -lglib12 -lintl -lXext -lX11 -lm -lgnomecanvasp= ixbuf -lgiconv -lc_r -L/usr/local/lib -lgthread12 -lglib12 -lc_r -Wl= ,-E -L/usr/X11R6/lib -L/usr/local/lib -lgnomeprint -lXpm -ljpeg -lgnomeui= -lgdk_imlib -ltiff -lungif -lpng -lSM -lICE -lgnome -lgnomesupport -lesd= -laudiofile -lgdk_pixbuf -lgtk12 -lgdk12 -lgmodule12 -lglib12 -lintl -lX= ext -lX11 -lart_lgpl -lm -lxml -lz -lfreetype -Wl,-E -L/usr/X11R6/li= b -L/usr/local/lib -lgtkhtml -lgal -lgnomeprint -lfreetype -lglade-gnome = -lglade -lxml -lXpm -ljpeg -lgnomeui -lart_lgpl -lgdk_imlib -ltiff -lungi= f -lpng -lz -lSM -lICE -lgnome -lgnomesupport -lesd -laudiofile -lgdk_pix= buf -lgnomecanvaspixbuf -lgiconv -lgconf-gtk-1 -lgconf-1 -loaf -lORBitCos= Naming -lORBit -lIIOP -lORBitutil -lwrap -lgtk12 -lgdk12 -lgmodule12 -lgl= ib12 -lintl -lXext -lX11 -lm -Wl,-E -L/usr/X11R6/lib -L/usr/local/l= ib -lbonobo_conf -lbonobo -loaf -lORBitCosNaming -lORBit -lIIOP -lORBitut= il -lwrap -lbonobox -lXpm -ljpeg -lgnomeui -lart_lgpl -lgdk_imlib -ltiff = -lungif -lpng -lSM -lICE -lgdk_pixbuf -lgtk12 -lgdk12 -lgmodule12 -lXext = -lX11 -lxml -lz -lgnome -lgnomesupport -lintl -lesd -laudiofile -lm -lgli= b12 -Wl,-E -L/usr/X11R6/lib -L/usr/local/lib -lbonobo -loaf -lORBitC= osNaming -lORBit -lIIOP -lORBitutil -lwrap -lbonobox -lbonobo-print -lgno= meprint -lfreetype -lglade-gnome -lglade -lxml -lgdk_pixbuf -lgnomecanvas= pixbuf -lXpm -ljpeg -lgnomeui -lart_lgpl -lgdk_imlib -ltiff -lungif -lpng= -lz -lSM -lICE -lgtk12 -lgdk12 -lgmodule12 -lXext -lX11 -lgnome -lgnomes= upport -lintl -lesd -laudiofile -lm -lglib12 -lc_r -L/usr/local/lib cc -pipe -O -mpreferred-stack-boundary=3D2 -march=3Dpentium -I/usr/X11R6/= include -Wall -Wunused -o .libs/evolution e-activity-handler.o e-componen= t-registry.o e-corba-shortcuts.o e-corba-storage-registry.o e-corba-stora= ge.o e-folder-type-registry.o e-folder.o e-gray-bar.o e-local-folder.o e-= local-storage.o e-setup.o e-shell-about-box.o e-shell-folder-commands.o e= -shell-folder-creation-dialog.o e-shell-folder-selection-dialog.o e-shell= -folder-title-bar.o e-shell-importer.o e-shell-offline-handler.o e-shell-= startup-wizard.o e-shell-user-creatable-items-handler.o e-shell-utils.o e= -shell-view-menu.o e-shell-view.o e-shell.o e-shortcuts-view-model.o e-sh= ortcuts-view.o e-shortcuts.o e-splash.o e-storage-set-view.o e-storage-se= t.o e-storage.o e-summary-storage.o e-task-bar.o e-task-widget.o e-uri-sc= hema-registry.o evolution-storage-set-view.o evolution-storage-set-view-f= actory.o main.o -Wl,-E -Wl,-E -Wl,-E -Wl,-E -Wl,-E -L/usr/X11R6/lib ./.l= ibs/libeshell.so -L/usr/local/lib importer/.libs/libevolution-importer.so= ../widgets/e-timezone-dialog/libetimezonedialog.a ../widgets/misc/libemi= scwidgets.a ../e-util/.libs/libeutil.al ../libical/src/libical/.libs/libi= cal-evolution.so -lgthread12 -lgtkhtml -lgal -lgiconv -lgconf-gtk-1 -lgco= nf-1 -lbonobo_conf -lbonobo -loaf -lORBitCosNaming -lORBit -lIIOP -lORBit= util -lwrap -lbonobox -lbonobo-print -lgnomeprint -lfreetype -lglade-gnom= e -lglade -lxml -lgdk_pixbuf -lgnomecanvaspixbuf -lXpm -ljpeg -lgnomeui -= lart_lgpl -lgdk_imlib -ltiff -lungif -lpng -lz -lSM -lICE -lgtk12 -lgdk12= -lgmodule12 -lXext -lX11 -lgnome -lgnomesupport -lintl -lesd -laudiofile= -lm -lglib12 -Wl,--rpath -Wl,/usr/X11R6/lib importer/.libs/libevolution-importer.so: warning: mktemp() possibly used = unsafely; consider using mkstemp() creating evolution gmake[1]: =F7=D9=C8=CF=C4 =C9=DA =CB=C1=D4=C1=CC=CF=C7 `/tmp/portbuild/us= r/ports/mail/evolution/work/evolution-1.0.2/shell' root@notebook# ldd .libs/evolution =2Elibs/evolution: libeshell.so.0 =3D> /usr/X11R6/lib/libeshell.so.0 (0x280ab000) libevolution-importer.so.0 =3D> /usr/X11R6/lib/libevolution-importer.so.= 0 (0x280e0000) libical-evolution.so.0 =3D> /usr/X11R6/lib/libical-evolution.so.0 (0x280= fd000) libgthread12.so.3 =3D> /usr/local/lib/libgthread12.so.3 (0x2814e000) libgtkhtml.so.21 =3D> /usr/X11R6/lib/libgtkhtml.so.21 (0x28151000) libgal.so.19 =3D> /usr/X11R6/lib/libgal.so.19 (0x281c5000) libgiconv.so.2 =3D> /usr/local/lib/libgiconv.so.2 (0x282ab000) libgconf-gtk-1.so.1 =3D> /usr/X11R6/lib/libgconf-gtk-1.so.1 (0x28380000)= libgconf-1.so.1 =3D> /usr/X11R6/lib/libgconf-1.so.1 (0x28386000) libbonobo_conf.so.0 =3D> /usr/X11R6/lib/libbonobo_conf.so.0 (0x283bd000)= libbonobo.so.2 =3D> /usr/X11R6/lib/libbonobo.so.2 (0x283df000) liboaf.so.0 =3D> /usr/X11R6/lib/liboaf.so.0 (0x2843b000) libORBitCosNaming.so.2 =3D> /usr/local/lib/libORBitCosNaming.so.2 (0x284= 53000) libORBit.so.2 =3D> /usr/local/lib/libORBit.so.2 (0x2845b000) libIIOP.so.2 =3D> /usr/local/lib/libIIOP.so.2 (0x284a3000) libORBitutil.so.2 =3D> /usr/local/lib/libORBitutil.so.2 (0x284ab000) libwrap.so.3 =3D> /usr/lib/libwrap.so.3 (0x284ad000) libbonobox.so.2 =3D> /usr/X11R6/lib/libbonobox.so.2 (0x284b4000) libbonobo-print.so.2 =3D> /usr/X11R6/lib/libbonobo-print.so.2 (0x2850900= 0) libgnomeprint.so.16 =3D> /usr/X11R6/lib/libgnomeprint.so.16 (0x2850d000)= libfreetype.so.8 =3D> /usr/X11R6/lib/libfreetype.so.8 (0x28966000) libglade-gnome.so.4 =3D> /usr/X11R6/lib/libglade-gnome.so.4 (0x2899f000)= libglade.so.4 =3D> /usr/X11R6/lib/libglade.so.4 (0x289ad000) libxml.so.5 =3D> /usr/local/lib/libxml.so.5 (0x289c3000) libgdk_pixbuf.so.2 =3D> /usr/X11R6/lib/libgdk_pixbuf.so.2 (0x28a31000) libgnomecanvaspixbuf.so.1 =3D> /usr/X11R6/lib/libgnomecanvaspixbuf.so.1 = (0x28a45000) libXpm.so.4 =3D> /usr/X11R6/lib/libXpm.so.4 (0x28a49000) libjpeg.so.9 =3D> /usr/local/lib/libjpeg.so.9 (0x28a56000) libgnomeui.so.5 =3D> /usr/X11R6/lib/libgnomeui.so.5 (0x28a73000) libart_lgpl.so.5 =3D> /usr/X11R6/lib/libart_lgpl.so.5 (0x28b39000) libgdk_imlib.so.5 =3D> /usr/X11R6/lib/libgdk_imlib.so.5 (0x28b46000) libtiff.so.4 =3D> /usr/local/lib/libtiff.so.4 (0x28b6f000) libungif.so.5 =3D> /usr/local/lib/libungif.so.5 (0x28bb2000) libpng.so.5 =3D> /usr/local/lib/libpng.so.5 (0x28bba000) libz.so.2 =3D> /usr/lib/libz.so.2 (0x28bdb000) libSM.so.6 =3D> /usr/X11R6/lib/libSM.so.6 (0x28be8000) libICE.so.6 =3D> /usr/X11R6/lib/libICE.so.6 (0x28bf1000) libgtk12.so.2 =3D> /usr/X11R6/lib/libgtk12.so.2 (0x28c06000) libgdk12.so.2 =3D> /usr/X11R6/lib/libgdk12.so.2 (0x28d24000) libgmodule12.so.3 =3D> /usr/local/lib/libgmodule12.so.3 (0x28d55000) libXext.so.6 =3D> /usr/X11R6/lib/libXext.so.6 (0x28d58000) libX11.so.6 =3D> /usr/X11R6/lib/libX11.so.6 (0x28d65000) libgnome.so.5 =3D> /usr/X11R6/lib/libgnome.so.5 (0x28e1e000) libgnomesupport.so.5 =3D> /usr/X11R6/lib/libgnomesupport.so.5 (0x28e3400= 0) libintl.so.1 =3D> /usr/local/lib/libintl.so.1 (0x28e3b000) libesd.so.2 =3D> /usr/local/lib/libesd.so.2 (0x28e40000) libaudiofile.so.0 =3D> /usr/local/lib/libaudiofile.so.0 (0x28e47000) libm.so.2 =3D> /usr/lib/libm.so.2 (0x28e67000) libglib12.so.3 =3D> /usr/local/lib/libglib12.so.3 (0x28e8b000) libc.so.5 =3D> /usr/lib/libc.so.5 (0x28eac000) libc_r.so.5 =3D> /usr/lib/libc_r.so.5 (0x28f5d000) libpopt.so.0 =3D> /usr/local/lib/libpopt.so.0 (0x28f7b000) libXThrStub.so.6 =3D> /usr/X11R6/lib/libXThrStub.so.6 (0x28f81000) root@notebook# ldd .libs/evolution | awk '{print $3}' /usr/X11R6/lib/libeshell.so.0 /usr/X11R6/lib/libevolution-importer.so.0 /usr/X11R6/lib/libical-evolution.so.0 /usr/local/lib/libgthread12.so.3 /usr/X11R6/lib/libgtkhtml.so.21 /usr/X11R6/lib/libgal.so.19 /usr/local/lib/libgiconv.so.2 /usr/X11R6/lib/libgconf-gtk-1.so.1 /usr/X11R6/lib/libgconf-1.so.1 /usr/X11R6/lib/libbonobo_conf.so.0 /usr/X11R6/lib/libbonobo.so.2 /usr/X11R6/lib/liboaf.so.0 /usr/local/lib/libORBitCosNaming.so.2 /usr/local/lib/libORBit.so.2 /usr/local/lib/libIIOP.so.2 /usr/local/lib/libORBitutil.so.2 /usr/lib/libwrap.so.3 /usr/X11R6/lib/libbonobox.so.2 /usr/X11R6/lib/libbonobo-print.so.2 /usr/X11R6/lib/libgnomeprint.so.16 /usr/X11R6/lib/libfreetype.so.8 /usr/X11R6/lib/libglade-gnome.so.4 /usr/X11R6/lib/libglade.so.4 /usr/local/lib/libxml.so.5 /usr/X11R6/lib/libgdk_pixbuf.so.2 /usr/X11R6/lib/libgnomecanvaspixbuf.so.1 /usr/X11R6/lib/libXpm.so.4 /usr/local/lib/libjpeg.so.9 /usr/X11R6/lib/libgnomeui.so.5 /usr/X11R6/lib/libart_lgpl.so.5 /usr/X11R6/lib/libgdk_imlib.so.5 /usr/local/lib/libtiff.so.4 /usr/local/lib/libungif.so.5 /usr/local/lib/libpng.so.5 /usr/lib/libz.so.2 /usr/X11R6/lib/libSM.so.6 /usr/X11R6/lib/libICE.so.6 /usr/X11R6/lib/libgtk12.so.2 /usr/X11R6/lib/libgdk12.so.2 /usr/local/lib/libgmodule12.so.3 /usr/X11R6/lib/libXext.so.6 /usr/X11R6/lib/libX11.so.6 /usr/X11R6/lib/libgnome.so.5 /usr/X11R6/lib/libgnomesupport.so.5 /usr/local/lib/libintl.so.1 /usr/local/lib/libesd.so.2 /usr/local/lib/libaudiofile.so.0 /usr/lib/libm.so.2 /usr/local/lib/libglib12.so.3 /usr/lib/libc.so.5 /usr/lib/libc_r.so.5 /usr/local/lib/libpopt.so.0 /usr/X11R6/lib/libXThrStub.so.6 root@notebook# ldd .libs/evolution | awk '{print $3}' | grep -v /usr/lib/= libc.so | xargs ldd | grep libc.so root@notebook# exit Script done on Fri Feb 8 17:43:04 2002 --------------1016F4DCC774CCCF248737AF-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 7:55:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id 7179F37B416; Fri, 8 Feb 2002 07:55:08 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id 79A819B73; Fri, 8 Feb 2002 10:54:25 -0500 (EST) Date: Fri, 8 Feb 2002 10:54:25 -0500 From: Will Andrews To: Maxim Sobolev Cc: hackers@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020208155425.GA82640@squall.waterspout.com> References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C63F3FE.D4E73334@FreeBSD.org> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ cc:-list from hell snipped ] On Fri, Feb 08, 2002 at 05:51:26PM +0200, Maxim Sobolev wrote: > But no library has it here! libc comes out of blue just before libc_r > - see attached script. Perhaps I'm missing something, but I can't > figure out where it comes from, could you? It is added automatically by ld(1) if -nostdlib is not specified. Regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 8: 1:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 5114E37B421 for ; Fri, 8 Feb 2002 08:01:41 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA48793; Fri, 8 Feb 2002 18:01:25 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h71.228.dialup.iptcom.net [212.9.228.71]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id SAA53700; Fri, 8 Feb 2002 18:01:14 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18G0hd69357; Fri, 8 Feb 2002 18:00:43 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C63F639.FBE067CF@FreeBSD.org> Date: Fri, 08 Feb 2002 18:00:57 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Will Andrews Cc: hackers@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> <20020208155425.GA82640@squall.waterspout.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Will Andrews wrote: > > [ cc:-list from hell snipped ] > > On Fri, Feb 08, 2002 at 05:51:26PM +0200, Maxim Sobolev wrote: > > But no library has it here! libc comes out of blue just before libc_r > > - see attached script. Perhaps I'm missing something, but I can't > > figure out where it comes from, could you? > > It is added automatically by ld(1) if -nostdlib is not specified. BZZZT! Wrong! It should come *after* libc_r, not before it. Please read the whole thread. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 8: 4:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id 380C637B417; Fri, 8 Feb 2002 08:04:33 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id 4F51A9B08; Fri, 8 Feb 2002 11:03:51 -0500 (EST) Date: Fri, 8 Feb 2002 11:03:51 -0500 From: Will Andrews To: Maxim Sobolev Cc: Will Andrews , hackers@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems Message-ID: <20020208160351.GC82640@squall.waterspout.com> References: <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> <20020208155425.GA82640@squall.waterspout.com> <3C63F639.FBE067CF@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C63F639.FBE067CF@FreeBSD.org> User-Agent: Mutt/1.3.26i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 06:00:57PM +0200, Maxim Sobolev wrote: > > On Fri, Feb 08, 2002 at 05:51:26PM +0200, Maxim Sobolev wrote: > > > But no library has it here! libc comes out of blue just before libc_r > > > - see attached script. Perhaps I'm missing something, but I can't > > > figure out where it comes from, could you? > > > > It is added automatically by ld(1) if -nostdlib is not specified. > > BZZZT! Wrong! It should come *after* libc_r, not before it. Please > read the whole thread. I did. If you'll actually read my reply, I said nothing about the order, just where it came from. REgards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 8:22:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id 45E4A37B422 for ; Fri, 8 Feb 2002 08:22:37 -0800 (PST) Received: from localhost ([127.0.0.1]) by vbook.express.ru with esmtp (Exim 3.33 #1) id 16ZDnJ-0001Ls-00 for hackers@freebsd.org; Fri, 08 Feb 2002 19:22:37 +0300 Subject: set uf UNIX utilites written on asm From: "Vladimir B. " Grebenschikov To: hackers@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 08 Feb 2002 19:22:37 +0300 Message-Id: <1013185357.5139.1.camel@vbook.express.ru> Mime-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi May it will be interesting for createing small setup like picobsd: http://linuxassembly.org/asmutils.html -- SW Soft, Moscow Vladimir B. Grebenschikov, vova@sw.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:21:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from www.example.org (ANice-103-1-3-124.abo.wanadoo.fr [80.11.189.124]) by hub.freebsd.org (Postfix) with SMTP id 790AF37B426 for ; Fri, 8 Feb 2002 09:21:00 -0800 (PST) Received: (qmail 48041 invoked by uid 1000); 8 Feb 2002 17:15:05 -0000 Date: Fri, 8 Feb 2002 18:15:05 +0100 From: Marco Molteni To: freebsd-hackers@freebsd.org Subject: upgrading to the new version of libpcap? Message-ID: <20020208181505.A46981@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, FreeBSD -current and -stable have libpcap 0.6.2, imported 10 months ago. The current libpcap from www.tcpdump.org is 0.7.1 (and has features I am interested in, namely the parsing of 802.11 frames). Is there a rule on how/when to update to a newer version? thanks Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:25: 8 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id D2F4237B41F; Fri, 8 Feb 2002 09:24:57 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g18HOlZ40937; Fri, 8 Feb 2002 18:24:47 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202081724.g18HOlZ40937@lurza.secnetix.de> Subject: Re: USB "Memorybird" quirks To: tlambert2@mindspring.com (Terry Lambert) Date: Fri, 8 Feb 2002 18:24:47 +0100 (CET) Cc: gene@nttmcl.com (Eugene M. Kim), olli@secnetix.de (Oliver Fromme), hardware@freebsd.org (FreeBSD Hardware Mailing List), hackers@freebsd.org (FreeBSD Hackers Mailing List) In-Reply-To: <3C63133A.CF411A74@mindspring.com> from "Terry Lambert" at Feb 07, 2002 03:52:26 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > "Eugene M. Kim" wrote: > > This is a common problem of most umass devices that implements BBB > > protocol, and arises from the fact that those devices don't understand > > the 6-byte SCSI READ command. You can add a quirk entry to > > src/sys/cam/scsi_da.c (refer to quirk entries that have DA_Q_NO_6_BYTE). > > > > IIRC this problem is being addressed at a more fundamental level on > > -current, by adding a 6-byte-to-10-byte READ command translator > > somewhere in the abstraction layer. > > Could this be "auto-quirked"? > > It seems to me that you should be able to add the quirk flag > to the device instance after the first failure... That's what I thought, too. It seems to me that umass_scsi_transform() in umass.c is the place intended for this kind of things. After the first failure (which is detected in umass_bbb_state()), a flag (quirk) should be set in the softc, and afterwards umass_scsi_transform should translate 6-byte commands to 10-byte commands. Doesn't sound too complicated to me. Or am I totally wrong? Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:33:42 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from www.example.org (ANice-103-1-3-124.abo.wanadoo.fr [80.11.189.124]) by hub.freebsd.org (Postfix) with SMTP id 8C05537B400 for ; Fri, 8 Feb 2002 09:33:38 -0800 (PST) Received: (qmail 50157 invoked by uid 1000); 8 Feb 2002 17:34:24 -0000 Date: Fri, 8 Feb 2002 18:34:24 +0100 From: Marco Molteni To: freebsd-hackers@freebsd.org Subject: Re: upgrading to the new version of libpcap? Message-ID: <20020208183424.A50136@cobweb.example.org> References: <20020208181505.A46981@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020208181505.A46981@cobweb.example.org>; from molter@tin.it on Fri, Feb 08, 2002 at 06:15:05PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Please find included a small patch to src/contrib/libpcap/FREEBSD-upgrade marco --- FREEBSD-upgrade Tue May 27 02:05:19 1997 +++ /home/molter/FREEBSD-upgrade Fri Feb 8 18:31:19 2002 @@ -28,7 +28,7 @@ To make local changes to libpcap, simply patch and commit to the main branch (aka HEAD). Never make local changes on the LBL branch. -All local changes should be submitted to "libpcap@ee.lbl.gov" for +All local changes should be submitted to "tcpdump-workers@tcpdump.org" for inclusion in the next vendor release of tcpdump and libpcap. pst@freebsd.org - 19 Aug 1996 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:36:14 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from www.example.org (ANice-103-1-3-124.abo.wanadoo.fr [80.11.189.124]) by hub.freebsd.org (Postfix) with SMTP id 3F96137B41A for ; Fri, 8 Feb 2002 09:36:11 -0800 (PST) Received: (qmail 39733 invoked by uid 1000); 8 Feb 2002 17:10:16 -0000 Date: Fri, 8 Feb 2002 18:10:16 +0100 From: Marco Molteni To: freebsd-hackers@freebsd.org Subject: upgrading to the new version of libpcap? Message-ID: <20020208181016.A39670@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, FreeBSD -current and -stable have libpcap 0.6.2, imported 10 months ago. The current libpcap from www.tcpdump.org is 0.7.1 (and has features I am interested in, namely the parsing of 802.11 frames). Is there a rule on how/when to update to a newer version? thanks Marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:48:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id B406F37B41A; Fri, 8 Feb 2002 09:48:31 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZF8L-0001lw-00; Fri, 08 Feb 2002 09:48:27 -0800 Message-ID: <3C640DDE.78417F5C@mindspring.com> Date: Fri, 08 Feb 2002 09:41:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: Maxim Sobolev , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <20020208172237.G78163@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > Sorry, but I don't get it. I can't reproduce it other than specifying > -lc explicitly. For example, -lssh now depends on -lcrypto and -lz, in > that order. Attempting to link a program with -lc_r -lssh gives, in > that order: > > libc_r.so.5 => /usr/lib/libc_r.so.5 (0x28065000) > libssh.so.2 => /usr/lib/libssh.so.2 (0x28083000) > libc.so.5 => /usr/lib/libc.so.5 (0x280b2000) > libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x28168000) > libz.so.2 => /usr/lib/libz.so.2 (0x28223000) > > The primary dependecies come first, then secondaries. I can only > imagine the situation where libc.so comes before libc_r.so if some > library has a (bogus) explicit dependency on libc.so. Yes, this is exactly the case: the shared library is linked against libc.so. THis is actually legal, and, in some cases, desirable. In the "Evolution" case, though, it's bogus. > How does ldd(1) output in question looks like, the full version? Heh. Same question I asked, with ldd information for the .so's, too. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:53:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 5A5C337B404; Fri, 8 Feb 2002 09:53:15 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFCq-0001DG-00; Fri, 08 Feb 2002 09:53:09 -0800 Message-ID: <3C640F07.9E2E3525@mindspring.com> Date: Fri, 08 Feb 2002 09:46:47 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: Maxim Sobolev , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ruslan Ermilov wrote: > > Seriously, the "Evolution" build process is seriously > > broken; it works on Linux because Linux has a simple > > threads implementation, rather than an efficient one. > > Doctor's Assistant: "No library should ever have an explicit > dependency on libc". One case that springs to mind is the mount system call interface change. A librarr that wrapped mount expecting the old version of the interface should be linked against the shared object that exports the interface on which it depends (in this case, that's libc.so.). There are some cases where this is true, but it's incredibly rare. In this case, though, we have a threaded program that doesn't link libc_r first, which it's *required* to do, even if it *happens* to work on Linux, it *won't* on a lot of other UNIX systems. It's questionable whether it's also erroneous to link the .so's that link gainst libc.so with libc.so instead of libc_r.so, if they are threaded, anyway. Oh... another libc.so linked to a shared object example that's valid: libc_r.so should be linked against libc.so. Duh! Nearly missed that one! 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 9:53:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id D2AD537B423 for ; Fri, 8 Feb 2002 09:53:28 -0800 (PST) Received: from isi.edu (szvmsqen5df4d2xn@hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g18HrSQ20321 for ; Fri, 8 Feb 2002 09:53:28 -0800 (PST) Message-ID: <3C641095.50801@isi.edu> Date: Fri, 08 Feb 2002 09:53:25 -0800 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020115 X-Accept-Language: en, de MIME-Version: 1.0 To: hackers@freebsd.org Subject: which irqs are generally good for rndcontrol? Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050801000700070609040308" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms050801000700070609040308 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, quick question: Are there any irqs that are generally a good source of entropy, for use with rndcontrol? I need a single setting that works well on a number of different machines (for our default configuration). Are there any drawbacks to specifying many irqs here (in the hope that some have good entropy on some machines, and others on other)? Thanks, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms050801000700070609040308 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIInzCC ArUwggIeoAMCAQICAwWBRzANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNV BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUx HTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVl bWFpbCBSU0EgMjAwMC44LjMwMB4XDTAxMDgyNDE2NDAwMFoXDTAyMDgyNDE2NDAwMFowVDEP MA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2VydDEc MBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC gYEA0AvLBsD78nxcUHeHkaMgl3b4qYPnfgbf8Lh+HQP8RgGMRG/Yb+vTpkGezlwt9pkJxiD1 1uZDy4CNNJUu3gKxKSb+zRV70O+lkwwftuHoLHoH4xwo3LcQ2LGDpd+I95tUN4dfJ3TmeEcU SF50dC/SuUI4w8AlhXQ8IxrhgdayTpECAwEAAaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIB BAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1Ud EwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAheZhn0pQA8zI7U2K1ZIAl11j0a1DKxnp3GtT vOUrGRB3WvYxidvdZ1kizhEsWeXU81TkNDH0DaRqtOEeu6Q2OhB+jeKEqY7IDAJE4/fI0e+d 6PnG1hd+vEvYmsKHkmzBhPc94XUOKNWO+qVNP2NGyNI3QIDy5wX4fdcOo1S34r4wggK1MIIC HqADAgECAgMFgUcwDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxX ZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYD VQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwg UlNBIDIwMDAuOC4zMDAeFw0wMTA4MjQxNjQwMDBaFw0wMjA4MjQxNjQwMDBaMFQxDzANBgNV BAQTBkVnZ2VydDENMAsGA1UEKhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxHDAaBgkq hkiG9w0BCQEWDWxhcnNlQGlzaS5lZHUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANAL ywbA+/J8XFB3h5GjIJd2+KmD534G3/C4fh0D/EYBjERv2G/r06ZBns5cLfaZCcYg9dbmQ8uA jTSVLt4CsSkm/s0Ve9DvpZMMH7bh6Cx6B+McKNy3ENixg6XfiPebVDeHXyd05nhHFEhedHQv 0rlCOMPAJYV0PCMa4YHWsk6RAgMBAAGjVjBUMCoGBStlAQQBBCEwHwIBADAaMBgCAQQEE0wy dU15ZmZCTlViTkpKY2RaMnMwGAYDVR0RBBEwD4ENbGFyc2VAaXNpLmVkdTAMBgNVHRMBAf8E AjAAMA0GCSqGSIb3DQEBAgUAA4GBAIXmYZ9KUAPMyO1NitWSAJddY9GtQysZ6dxrU7zlKxkQ d1r2MYnb3WdZIs4RLFnl1PNU5DQx9A2karThHrukNjoQfo3ihKmOyAwCROP3yNHvnej5xtYX frxL2JrCh5JswYT3PeF1DijVjvqlTT9jRsjSN0CA8ucF+H3XDqNUt+K+MIIDKTCCApKgAwIB AgIBDDANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4g Q2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEo MCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVl bWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTAyMDgyOTIzNTk1OVowgZIxCzAJ BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEP MA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UE AxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/ +TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENC UFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0P BAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBAHMbbyZli/8VNEtZYortRL5Jx+gNu4+5DWomKmKE H7iHY3QcbbfPGlORS+HN5jjZ7VD0Omw0kqzmkpxuwSMBwgmn70uuct0GZ/VQby5YuLYLwVBX tewc1+8XttWIm7eiiBrtOVs5fTT8tpYYJU1q9J3Fw5EvqZa4BTxS/N3pYgNIMYICpjCCAqIC AQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT CUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2 aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBYFHMAkG BSsOAwIaBQCgggFhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTAyMDIwODE3NTMyNVowIwYJKoZIhvcNAQkEMRYEFIa71CYWtwh8CcgHV8nGyOnvQt3SMFIG CSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGtBgsqhkiG9w0BCRACCzGBnaCBmjCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMFgUcwDQYJKoZIhvcNAQEB BQAEgYBJ8PjbYxTEnhO5loTJcagPBMUAPuSB7ylraoLoBbSjthwxc9zqtkf3NPYd4wd16dXb Qfl2q4mtHb5rLMND8dgKK0uKmJhNSE26b6HBOaYAidbgYSNvqCPZ9EWdEwwT8Tk0jxXqcDXm PYfeJktKjlnn0N4PyG4PszX6mNCO+VL75QAAAAAAAA== --------------ms050801000700070609040308-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 0:31 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id B48C237B41F; Fri, 8 Feb 2002 10:00:18 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFJh-0003kZ-00; Fri, 08 Feb 2002 10:00:13 -0800 Message-ID: <3C6410A6.495CFD3A@mindspring.com> Date: Fri, 08 Feb 2002 09:53:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > But no library has it here! libc comes out of blue just before libc_r > - see attached script. Perhaps I'm missing something, but I can't > figure out where it comes from, could you? What does your patched ldd say about each and every one of those .so's you are linking in perhaps being linked against libc.so, or linked against something linked against something ... linked against something linked against libc.so? Are *any* of the object files created with "ld -r"? Which binutils are you using? Who cut your hair? ;^). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 1:15 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 3812437B41A; Fri, 8 Feb 2002 10:00:45 -0800 (PST) Received: from [192.168.1.129] (212.129.11.210) by mail.libertysurf.net (5.1.053) id 3C633FD40002C6AB; Fri, 8 Feb 2002 19:00:20 +0100 Date: Thu, 7 Feb 2002 20:00:24 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Josef Karthauser Cc: Terry Lambert , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks In-Reply-To: <20020207235746.E46984@genius.tao.org.uk> Message-ID: <20020207193911.U1513-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Feb 2002, Josef Karthauser wrote: > On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: > > > > > > IIRC this problem is being addressed at a more fundamental level on > > > -current, by adding a 6-byte-to-10-byte READ command translator > > > somewhere in the abstraction layer. > > > > Could this be "auto-quirked"? > > > > As in, try a 6 byte command, and if that fails try a 10 byte command > instead? > > Unfortunately although I'm maintaining USB in -current, I don't have a > complete in depth understanding of the code yet. :( I'm mainly trying > to fix my problems by taking from NetBSD. A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block devices in order to accomodate softwares as boot software for example that may not be upgradable on systems still in use. Softwares that are maintained should no longer use 6 byte commands, but use the 10 byte commands replacement (for years...). So, unless we want to accomodate applications that still may send 6 byte commands through passthrough driver, no translator should be needed. Just make class drivers use 10 byte commands instead. I donnot know about USB in details. But since USB is a recent technology USB devices should not be required to support READ/WRITE 6 byte commands. OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever want to implemement kind of trustable disk write caching support since they do not allow to selectively force media access (this is achieved by the FUA bit in >=3D 10 byte READ/WRITE command). As a result, no device should be quirked nowadays as failing READ/WRITE 6 byte commands. Just maintained softwares should get rid of those commands asap. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 1:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from host213-123-132-86.in-addr.btopenworld.com (host213-123-132-86.in-addr.btopenworld.com [213.123.132.86]) by hub.freebsd.org (Postfix) with ESMTP id 0A09837B41C for ; Fri, 8 Feb 2002 10:01:38 -0800 (PST) Received: by host213-123-132-86.in-addr.btopenworld.com (Postfix, from userid 1001) id CD0BF418; Fri, 8 Feb 2002 18:01:49 +0000 (GMT) Date: Fri, 8 Feb 2002 18:01:49 +0000 From: Dominic Marks To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: which irqs are generally good for rndcontrol? Message-ID: <20020208180149.A42549@host213-123-132-86.in-addr.btop> References: <3C641095.50801@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3C641095.50801@isi.edu>; from larse@ISI.EDU on Fri, Feb 08, 2002 at 09:53:25AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, On Fri, Feb 08, 2002 at 09:53:25AM -0800, Lars Eggert wrote: > Hi, > > quick question: Are there any irqs that are generally a good source of > entropy, for use with rndcontrol? I need a single setting that works > well on a number of different machines (for our default configuration). > Are there any drawbacks to specifying many irqs here (in the hope that > some have good entropy on some machines, and others on other)? > > Thanks, > Lars > -- > Lars Eggert Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California I think this was debated before, and I seem to remember Mike Silbersack was the original poster. You might like to search the archives and see. Or my memory could be in a twist (?). -- Dominic ==> Blatant EMail Abuse Start {I'm looking for a summer job. If your based in or around London and need some skivvy work doing by an impoverished student :) please mail me privately, I can code (best to ask if you need specifics) and Admin, ... and make tea, use a photocopier, Thanks} <== Blatant EMail Abuse Stop To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 4:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 47DEB37B436; Fri, 8 Feb 2002 10:03:53 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA36078; Fri, 8 Feb 2002 20:03:42 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h54.229.dialup.iptcom.net [212.9.229.54]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id UAA99449; Fri, 8 Feb 2002 20:03:40 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18I38d69646; Fri, 8 Feb 2002 20:03:08 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C6412EA.2605CDB@FreeBSD.org> Date: Fri, 08 Feb 2002 20:03:22 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <20020208172237.G78163@sunbay.com> <3C640DDE.78417F5C@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Ruslan Ermilov wrote: > > Sorry, but I don't get it. I can't reproduce it other than specifying > > -lc explicitly. For example, -lssh now depends on -lcrypto and -lz, in > > that order. Attempting to link a program with -lc_r -lssh gives, in > > that order: > > > > libc_r.so.5 => /usr/lib/libc_r.so.5 (0x28065000) > > libssh.so.2 => /usr/lib/libssh.so.2 (0x28083000) > > libc.so.5 => /usr/lib/libc.so.5 (0x280b2000) > > libcrypto.so.2 => /usr/lib/libcrypto.so.2 (0x28168000) > > libz.so.2 => /usr/lib/libz.so.2 (0x28223000) > > > > The primary dependecies come first, then secondaries. I can only > > imagine the situation where libc.so comes before libc_r.so if some > > library has a (bogus) explicit dependency on libc.so. > > Yes, this is exactly the case: the shared library is linked > against libc.so. THis is actually legal, and, in some cases, > desirable. > > In the "Evolution" case, though, it's bogus. As you can see from my log there was no library explicitly linked with libc and no -lc command line option, but resulting executable ended up with libc recorded right before libc_r. Any clues? -Maxim > > > How does ldd(1) output in question looks like, the full version? > > Heh. Same question I asked, with ldd information for the > .so's, too. 8-). > > -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 8: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 4D48F37B404 for ; Fri, 8 Feb 2002 10:07:52 -0800 (PST) Received: from isi.edu (oeb3nv3koaqekna4@hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g18I7nQ27235; Fri, 8 Feb 2002 10:07:49 -0800 (PST) Message-ID: <3C6413F1.6010401@isi.edu> Date: Fri, 08 Feb 2002 10:07:45 -0800 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20020115 X-Accept-Language: en, de MIME-Version: 1.0 To: Dominic Marks Cc: hackers@freebsd.org Subject: Re: which irqs are generally good for rndcontrol? References: <3C641095.50801@isi.edu> <20020208180149.A42549@host213-123-132-86.in-addr.btop> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070601000700030201040308" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms070601000700030201040308 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dominic Marks wrote: >>quick question: Are there any irqs that are generally a good source of >>entropy, for use with rndcontrol? I need a single setting that works >>well on a number of different machines (for our default configuration). >>Are there any drawbacks to specifying many irqs here (in the hope that >>some have good entropy on some machines, and others on other)? >> > > I think this was debated before, and I seem to remember Mike > Silbersack was the original poster. You might like to search the > archives and see. > > Or my memory could be in a twist (?). All I found in the archives was a related discussion if using CPU temperature and fan speed would be good sources of entropy. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms070601000700030201040308 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIInzCC ArUwggIeoAMCAQICAwWBRzANBgkqhkiG9w0BAQIFADCBkjELMAkGA1UEBhMCWkExFTATBgNV BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUx HTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVl bWFpbCBSU0EgMjAwMC44LjMwMB4XDTAxMDgyNDE2NDAwMFoXDTAyMDgyNDE2NDAwMFowVDEP MA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2VydDEc MBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkC gYEA0AvLBsD78nxcUHeHkaMgl3b4qYPnfgbf8Lh+HQP8RgGMRG/Yb+vTpkGezlwt9pkJxiD1 1uZDy4CNNJUu3gKxKSb+zRV70O+lkwwftuHoLHoH4xwo3LcQ2LGDpd+I95tUN4dfJ3TmeEcU SF50dC/SuUI4w8AlhXQ8IxrhgdayTpECAwEAAaNWMFQwKgYFK2UBBAEEITAfAgEAMBowGAIB BAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1MAwGA1Ud EwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAheZhn0pQA8zI7U2K1ZIAl11j0a1DKxnp3GtT vOUrGRB3WvYxidvdZ1kizhEsWeXU81TkNDH0DaRqtOEeu6Q2OhB+jeKEqY7IDAJE4/fI0e+d 6PnG1hd+vEvYmsKHkmzBhPc94XUOKNWO+qVNP2NGyNI3QIDy5wX4fdcOo1S34r4wggK1MIIC HqADAgECAgMFgUcwDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxX ZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYD VQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwg UlNBIDIwMDAuOC4zMDAeFw0wMTA4MjQxNjQwMDBaFw0wMjA4MjQxNjQwMDBaMFQxDzANBgNV BAQTBkVnZ2VydDENMAsGA1UEKhMETGFyczEUMBIGA1UEAxMLTGFycyBFZ2dlcnQxHDAaBgkq hkiG9w0BCQEWDWxhcnNlQGlzaS5lZHUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANAL ywbA+/J8XFB3h5GjIJd2+KmD534G3/C4fh0D/EYBjERv2G/r06ZBns5cLfaZCcYg9dbmQ8uA jTSVLt4CsSkm/s0Ve9DvpZMMH7bh6Cx6B+McKNy3ENixg6XfiPebVDeHXyd05nhHFEhedHQv 0rlCOMPAJYV0PCMa4YHWsk6RAgMBAAGjVjBUMCoGBStlAQQBBCEwHwIBADAaMBgCAQQEE0wy dU15ZmZCTlViTkpKY2RaMnMwGAYDVR0RBBEwD4ENbGFyc2VAaXNpLmVkdTAMBgNVHRMBAf8E AjAAMA0GCSqGSIb3DQEBAgUAA4GBAIXmYZ9KUAPMyO1NitWSAJddY9GtQysZ6dxrU7zlKxkQ d1r2MYnb3WdZIs4RLFnl1PNU5DQx9A2karThHrukNjoQfo3ihKmOyAwCROP3yNHvnej5xtYX frxL2JrCh5JswYT3PeF1DijVjvqlTT9jRsjSN0CA8ucF+H3XDqNUt+K+MIIDKTCCApKgAwIB AgIBDDANBgkqhkiG9w0BAQQFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4g Q2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEo MCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVl bWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAwMDAwMFoXDTAyMDgyOTIzNTk1OVowgZIxCzAJ BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEP MA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UE AxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXaiBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/ +TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENC UFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvpoWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0P BAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBAHMbbyZli/8VNEtZYortRL5Jx+gNu4+5DWomKmKE H7iHY3QcbbfPGlORS+HN5jjZ7VD0Omw0kqzmkpxuwSMBwgmn70uuct0GZ/VQby5YuLYLwVBX tewc1+8XttWIm7eiiBrtOVs5fTT8tpYYJU1q9J3Fw5EvqZa4BTxS/N3pYgNIMYICpjCCAqIC AQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT CUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2 aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMAIDBYFHMAkG BSsOAwIaBQCgggFhMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTAyMDIwODE4MDc0NVowIwYJKoZIhvcNAQkEMRYEFDan2CUoitcEz6bzO0qfgTYYH8riMFIG CSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGtBgsqhkiG9w0BCRACCzGBnaCBmjCBkjEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYD VQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwAgMFgUcwDQYJKoZIhvcNAQEB BQAEgYBN6ZyLGXLS6pC8g5UvEX/i0fCT79KWnFXwzIA29WwsHQL+K9N272ZFQ5KdTDaKK+kZ VkRjoyI3ZCcJ6oB2PRgK0mKSCSQzA2LxUN3feTC6aW+bfBQWluYYXccoKV27v4UPHhhpC2o7 ZM1hYrD+c4BYPVD5HhN0SU+Sab0iUpQ2zgAAAAAAAA== --------------ms070601000700030201040308-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10: 8:55 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from host213-123-132-86.in-addr.btopenworld.com (host213-123-132-86.in-addr.btopenworld.com [213.123.132.86]) by hub.freebsd.org (Postfix) with ESMTP id 164D237B423 for ; Fri, 8 Feb 2002 10:08:33 -0800 (PST) Received: by host213-123-132-86.in-addr.btopenworld.com (Postfix, from userid 1001) id 40441418; Fri, 8 Feb 2002 18:08:46 +0000 (GMT) Date: Fri, 8 Feb 2002 18:08:46 +0000 From: Dominic Marks To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: which irqs are generally good for rndcontrol? Message-ID: <20020208180846.B42549@host213-123-132-86.in-addr.btop> References: <3C641095.50801@isi.edu> <20020208180149.A42549@host213-123-132-86.in-addr.btop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020208180149.A42549@host213-123-132-86.in-addr.btop>; from dominic_marks@btinternet.com on Fri, Feb 08, 2002 at 06:01:49PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, On Fri, Feb 08, 2002 at 06:01:49PM +0000, Dominic Marks wrote: > Hey, > > On Fri, Feb 08, 2002 at 09:53:25AM -0800, Lars Eggert wrote: > > Hi, > > > > quick question: Are there any irqs that are generally a good source of > > entropy, for use with rndcontrol? I need a single setting that works > > well on a number of different machines (for our default configuration). > > Are there any drawbacks to specifying many irqs here (in the hope that > > some have good entropy on some machines, and others on other)? > > > > Thanks, > > Lars > > -- > > Lars Eggert Information Sciences Institute > > http://www.isi.edu/larse/ University of Southern California > > I think this was debated before, and I seem to remember Mike > Silbersack was the original poster. You might like to search the > archives and see. > > Or my memory could be in a twist (?). Twisted Indeed: http://www.FreeBSD.org/cgi/getmsg.cgi? * fetch=530673+532567+/usr/local/www/db/text/2001/ * freebsd-hackers/20011111.freebsd-hackers Similar, but different. -- Dominic ==> Blatant EMail Abuse Start {I'm looking for a summer job. If your based in or around London and need some skivvy work doing by an impoverished student :) please mail me privately, I can code (best to ask if you need specifics) and Admin, ... and make tea, use a photocopier, Thanks} <== Blatant EMail Abuse Stop To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:11:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 9647437B404; Fri, 8 Feb 2002 10:11:39 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFUb-0002PY-00; Fri, 08 Feb 2002 10:11:28 -0800 Message-ID: <3C641347.ADE06FAD@mindspring.com> Date: Fri, 08 Feb 2002 10:04:55 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Fromme Cc: "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <200202081724.g18HOlZ40937@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oliver Fromme wrote: > > Could this be "auto-quirked"? [ ... ] > It seems to me that umass_scsi_transform() in umass.c is > the place intended for this kind of things. After the > first failure (which is detected in umass_bbb_state()), > a flag (quirk) should be set in the softc, and afterwards > umass_scsi_transform should translate 6-byte commands to > 10-byte commands. Doesn't sound too complicated to me. After looking at the code in more detail, then puzzling and puzzling 'til mu puzzler was sore, then sitting back down, and puzzling some more... It very obviously needs to be generic in the CAM layer in the da handler, since it's applicable to all devices in the quirks table, not just the USB devices. It still needs a failuter trace from the CAM_DEBUG stuff. Strange as it may seem, I look through quirks lists before I buy hardware, and if it has a quirk, I don't buy it. So I'm not in a position to run the test, or test a fix. The USB stuff still needs to retry more than it does, though, if those logs were an accurate retry count, or the fix of automatically moving from 6->10 byte commands won't work transparently, and you'll end up having to do the disklabel a couple of times before it sticks. This is pretty unacceptable behaviour (it violates POLA all to heck). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:18:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 40B5237B421 for ; Fri, 8 Feb 2002 10:18:03 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFar-00040J-00; Fri, 08 Feb 2002 10:17:58 -0800 Message-ID: <3C6414D9.781B3676@mindspring.com> Date: Fri, 08 Feb 2002 10:11:37 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: hackers@freebsd.org Subject: Re: which irqs are generally good for rndcontrol? References: <3C641095.50801@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lars Eggert wrote: > quick question: Are there any irqs that are generally a good source of > entropy, for use with rndcontrol? I need a single setting that works > well on a number of different machines (for our default configuration). > Are there any drawbacks to specifying many irqs here (in the hope that > some have good entropy on some machines, and others on other)? Everywhere I've ever worked, they've picked IRQs that were right in the performance path, so it screws up your performance. They've also picked IRQs that can't really provide any "entropy" until after the system is up, and the weenie thing hangs in the salting while it's "harvesting entropy". This was true, even when the system had perfectly good crypto hardware that could be used to generate random numbers without relying on the "entropy" stuff (the "entropy" stuff is pretty much done with no respect for large number theory; multiplying two random numbers together makes them *less* random, not *more*). My preference is for pre-baked "entropy" from the entropy store: jam the old state back in after each boot, and start life with something like a hashed copy of the install time, the install kernel, the /etc/ttys file, or whatever. As long as you save it and restore it each time and futz in the boot time in case it didn't save on the last panic, I think it's fine. For those who will inevitably jump in and claim "It's not random! The sky is falling!"... prove it by writing an exploit, K PLZ THX. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:33:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from patrocles.silby.com (d27.as7.nwbl0.wi.voyager.net [169.207.128.155]) by hub.freebsd.org (Postfix) with ESMTP id 2BDD937B416 for ; Fri, 8 Feb 2002 10:33:38 -0800 (PST) Received: from localhost (silby@localhost) by patrocles.silby.com (8.11.6/8.11.6) with ESMTP id g18CbIW08260; Fri, 8 Feb 2002 12:37:19 GMT (envelope-from silby@silby.com) X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs Date: Fri, 8 Feb 2002 12:37:17 +0000 (GMT) From: Mike Silbersack To: Dominic Marks Cc: Lars Eggert , Subject: Re: which irqs are generally good for rndcontrol? In-Reply-To: <20020208180149.A42549@host213-123-132-86.in-addr.btop> Message-ID: <20020208123615.G8081-100000@patrocles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Feb 2002, Dominic Marks wrote: > I think this was debated before, and I seem to remember Mike > Silbersack was the original poster. You might like to search the > archives and see. > > Or my memory could be in a twist (?). > > -- > Dominic I'm far from an entropy expert, and you should probably discount my "fan speed and cpu temp" theory. :) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:38:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 1489637B419; Fri, 8 Feb 2002 10:38:05 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFu6-0005UD-00; Fri, 08 Feb 2002 10:37:48 -0800 Message-ID: <3C64196C.CC0318FD@mindspring.com> Date: Fri, 08 Feb 2002 10:31:08 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?G=E9rard?= Roudier Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <20020207193911.U1513-100000@gerard> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG G=E9rard Roudier wrote: > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI blo= ck > devices in order to accomodate softwares as boot software for example t= hat > may not be upgradable on systems still in use. Not a real problem, since if the device doesn't support the 5 byte commands, it's not booting with the legacy system software anyway, since you can't boot legacy stuff on it. > Softwares that are > maintained should no longer use 6 byte commands, but use the 10 byte > commands replacement (for years...). This I don't understand. FreeBSD appears to have a preference for the 6 byte commands in the drivers, which are only used after boot. Further, it makes sense that you'd prefer 6 byte if you could, since it makes your commands 60% smaller, which should make them faster. > So, unless we want to accomodate applications that still may send 6 byt= e > commands through passthrough driver, no translator should be needed. Ju= st > make class drivers use 10 byte commands instead. There has to be a reason that FreeBSD has a preference for 6 bytes in the CAM code... ?!? > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever w= ant > to implemement kind of trustable disk write caching support since they = do > not allow to selectively force media access (this is achieved by the FU= A > bit in >=3D 10 byte READ/WRITE command). > = > As a result, no device should be quirked nowadays as failing READ/WRITE= 6 > byte commands. Just maintained softwares should get rid of those comman= ds > asap. It sounds like devices that only support 6 byte commands are the ones that need quirked? In other words, you're just reversing the default and the fallback positions. I think auto-detecting the quirk is still a good bet, even in the 6 byte only case, just as it would have been in the 10 byte only case. Thanks for the info on what's supposed to be done going forward, though. If there's no performance issue with 10 byte commands, inverting the default and the quirk handling in the failure case seems to be the right thing to do. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:43: 0 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 3DEBD37B426; Fri, 8 Feb 2002 10:42:54 -0800 (PST) Received: from pool0031.cvx22-bradley.dialup.earthlink.net ([209.179.198.31] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZFz2-0003zT-00; Fri, 08 Feb 2002 10:42:53 -0800 Message-ID: <3C641A7E.B1A5B6F8@mindspring.com> Date: Fri, 08 Feb 2002 10:35:42 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <20020208172237.G78163@sunbay.com> <3C640DDE.78417F5C@mindspring.com> <3C6412EA.2605CDB@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > Yes, this is exactly the case: the shared library is linked > > against libc.so. THis is actually legal, and, in some cases, > > desirable. > > > > In the "Evolution" case, though, it's bogus. > > As you can see from my log there was no library explicitly linked with > libc and no -lc command line option, but resulting executable ended up > with libc recorded right before libc_r. Any clues? Answer my other questions. In the course of obtaining the answers, you will be presented with all the necessary clues to resolve your mystery. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:45:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from glatton.cnchost.com (glatton.cnchost.com [207.155.248.47]) by hub.freebsd.org (Postfix) with ESMTP id 360F537B428; Fri, 8 Feb 2002 10:45:24 -0800 (PST) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by glatton.cnchost.com id NAA13569; Fri, 8 Feb 2002 13:45:23 -0500 (EST) [ConcentricHost SMTP Relay 1.14] Message-ID: <200202081845.NAA13569@glatton.cnchost.com> To: Maxim Sobolev Cc: Terry Lambert , Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems In-reply-to: Your message of "Fri, 08 Feb 2002 20:03:22 +0200." <3C6412EA.2605CDB@FreeBSD.org> Date: Fri, 08 Feb 2002 10:45:23 -0800 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > As you can see from my log there was no library explicitly linked with > libc and no -lc command line option, but resulting executable ended up > with libc recorded right before libc_r. Any clues? I don't get this ordering problem with your test.c file on a very recent -current. What do you get when you use the -v flag (not for the test case but the program (ximian) that hangs)? By using the -v flag as in $ cc -v test.c -o test -lc -lc_r reveals (after snipping uninteresting stuff) /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -o test /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/cc6O0HGi.o -lc -lc_r -lgcc -lc -lgcc /usr/lib/crtend.o /usr/lib/crtn.o $ ldd test test: libc.so.5 => /usr/lib/libc.so.5 (0x18068000) libc_r.so.5 => /usr/lib/libc_r.so.5 (0x1811b000) Here ./test hangs. Based on the follow But $ cc -v test.c -o test -lc_r -lc reveals /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -o test /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/ccrxO4nI.o -lc_r -lc -lgcc -lc -lgcc /usr/lib/crtend.o /usr/lib/crtn.o $ ldd test test: libc_r.so.5 => /usr/lib/libc_r.so.5 (0x18068000) libc.so.5 => /usr/lib/libc.so.5 (0x18086000) Here ./test does not hang. So it is clear that the cc frontend sticks on -lc at the end. To prove it: $ cc -v test.c -o test -lc_r reveals /usr/libexec/elf/ld -m elf_i386 -dynamic-linker /usr/libexec/ld-elf.so.1 -o test /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtbegin.o -L/usr/libexec/elf -L/usr/libexec -L/usr/lib /tmp/ccxNFUZi.o -lc_r -lgcc -lc -lgcc /usr/lib/crtend.o /usr/lib/crtn.o ldd test test: libc_r.so.5 => /usr/lib/libc_r.so.5 (0x18068000) libc.so.5 => /usr/lib/libc.so.5 (0x18086000) and ./test works. Also note that on 4.5-RELEASE, ./test core dumps where it hangs on -CURRENT so there too it misbehaves but differently. Elsewhere you said > I think that ld(1) should be smart enough to reorder libc/libc_r so that > libc_r is always linked before libc. I don't believe this would be wise. ld should do exactly what it is told and link against libraries in the order specified. It is the frontend's (cc's) repsonsibility to specify libraries in the right order. I do think that explicitly specifying libc or libc_r to cc is asking for trouble (though I understand your doing it in a test case to illustrate the problem). -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:55:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (Postfix) with ESMTP id BD94437B400 for ; Fri, 8 Feb 2002 10:55:50 -0800 (PST) Received: (from alex@localhost) by androcles.com (8.11.6/8.11.3) id g18ItgK66957; Fri, 8 Feb 2002 10:55:42 -0800 (PST) (envelope-from alex) Message-Id: <200202081855.g18ItgK66957@androcles.com> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020207185052.A87994@Space.Net> Date: Fri, 08 Feb 2002 10:55:42 -0800 (PST) From: "Duane H. Hesser" To: Markus Stumpf Subject: RE: dump(8) race conditions? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Feb-02 Markus Stumpf wrote: > We use amanda and dump for backups. Some hosts have rather busy disks > even during non prime time hours when backup is run. > > From time to time amanda reports dump(8) errors like the following: > > sendbackup: info end >| DUMP: Date of this level 5 dump: Wed Feb 6 01:53:12 2002 >| DUMP: Date of last level 4 dump: Mon Feb 4 02:31:40 2002 >| DUMP: Dumping /dev/rda4s1e (/share/turing/disk07) to standard output >| DUMP: mapping (Pass I) [regular files] >| DUMP: mapping (Pass II) [directories] >| DUMP: estimated 2423080 tape blocks. >| DUMP: dumping (Pass III) [directories] >| DUMP: dumping (Pass IV) [regular files] >| DUMP: 14.72% done, finished in 0:28 >| DUMP: 33.78% done, finished in 0:19 >| DUMP: 52.84% done, finished in 0:13 >| DUMP: 71.65% done, finished in 0:07 > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921522]: count=3072 > ? DUMP: DUMP: read error from /dev/rda4s1e: Invalid argument: [sector -410921522]: count=512 > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -410921532]: count=5120 > ? DUMP: read error from /dev/rda4s1e: Invalid argument: [block -1001057530]: count=1024 > [ ... ] > > First time we saw this we took down the machine to single user, unmounted > the disk and fsck'd it. No errors where found and the next backups (even > level 0) made it without errors. > > As we where still suspicious as to what might be the reason for this really > sporadic error messages from different machines and different disks I > look through the source of dump. > > If I do interpret the code correctly dump caches directory inode lists. > Now, if during a dump and after caching the inode infos files get > removed/shrunk dump has a "dirty" cache and tries to access blocks > that are not/no longer allocated and the result are the above errors. > > Am I right with my interpretation or are this really hardware errors? > You are essentially correct, and your message is probably a good reminder for those of us who routinely use dump on active filesystems. Dump is a two pass system, and any activity which modifies inodes between the first pass and the second is likely to cause problems, either for dump or for restore. It has always been thus, even as far back as V7 (and probably v6). Dumps which report errors such as the ones you mention are likely to cause difficulities on restore. Sometimes they will be completely unreadable; sometimes partial or interactive restores will succeed (for some files). It is even possible that the dump may be completely restorable, but with corrupted files. On the other hand, dumps which *don't* report errors can still be subtly corrupted. Elizabeth Zwicky, in a ten year old paper entitled "Torture Testing Backup and Archive Programs', discusses a couple of situations where this can occur. It is operationally (and sometimes "politically") difficult to dump on unmounted filesystems, so most of us (I think) "bite the bullet" and try to dump at times when the subject filesystem is likely to be quiescent. It may also be smart to dump more frequently than otherwise called for, just to increase the odds. Your message reminds us of the risks we take. It is worth noting that "activity" can be occurring on a filestystem and dump will succeed if there is no activity which alters inodes significantly between passes. -------------- Duane H. Hesser dhh@androcles.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 10:59:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 6000E37B400; Fri, 8 Feb 2002 10:59:40 -0800 (PST) Received: (from gene@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g18Ix7M07563; Fri, 8 Feb 2002 10:59:07 -0800 (PST) Date: Fri, 8 Feb 2002 10:59:07 -0800 From: "Eugene M. Kim" To: Terry Lambert Cc: G?rard Roudier , Josef Karthauser , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks Message-ID: <20020208105907.A20197@alicia.nttmcl.com> References: <20020207193911.U1513-100000@gerard> <3C64196C.CC0318FD@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <3C64196C.CC0318FD@mindspring.com>; from tlambert2@mindspring.com on Fri, Feb 08, 2002 at 10:31:08AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG There is hardly a performance issue about 10-byte READ, considering the size of a whole transaction (command + transfer) is at least as large as a disk sector (512 bytes on most modern drives); a four-byte difference is almost nothing here. IMHO the best way is to `try a 10-byte READ first, and if it fails then fallback to a 6-byte READ.' Eugene On Fri, Feb 08, 2002 at 10:31:08AM -0800, Terry Lambert wrote: > > > Gérard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > > devices in order to accomodate softwares as boot software for example that > > may not be upgradable on systems still in use. > > Not a real problem, since if the device doesn't support > the 5 byte commands, it's not booting with the legacy > system software anyway, since you can't boot legacy stuff > on it. > > > > Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > This I don't understand. FreeBSD appears to have a > preference for the 6 byte commands in the drivers, > which are only used after boot. > > Further, it makes sense that you'd prefer 6 byte if > you could, since it makes your commands 60% smaller, > which should make them faster. > > > > So, unless we want to accomodate applications that still may send 6 byte > > commands through passthrough driver, no translator should be needed. Just > > make class drivers use 10 byte commands instead. > > There has to be a reason that FreeBSD has a preference > for 6 bytes in the CAM code... ?!? > > > > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever want > > to implemement kind of trustable disk write caching support since they do > > not allow to selectively force media access (this is achieved by the FUA > > bit in >= 10 byte READ/WRITE command). > > > > As a result, no device should be quirked nowadays as failing READ/WRITE 6 > > byte commands. Just maintained softwares should get rid of those commands > > asap. > > It sounds like devices that only support 6 byte commands > are the ones that need quirked? > > In other words, you're just reversing the default and > the fallback positions. > > I think auto-detecting the quirk is still a good bet, > even in the 6 byte only case, just as it would have > been in the 10 byte only case. > > Thanks for the info on what's supposed to be done going > forward, though. If there's no performance issue with > 10 byte commands, inverting the default and the quirk > handling in the failure case seems to be the right thing > to do. > > -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11: 6:37 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (Postfix) with ESMTP id 50F0437B400 for ; Fri, 8 Feb 2002 11:06:27 -0800 (PST) Received: (from alex@localhost) by androcles.com (8.11.6/8.11.3) id g18J6Lw67038; Fri, 8 Feb 2002 11:06:21 -0800 (PST) (envelope-from alex) Message-Id: <200202081906.g18J6Lw67038@androcles.com> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020207152736.T45642@seven.alameda.net> Date: Fri, 08 Feb 2002 11:06:21 -0800 (PST) From: "Duane H. Hesser" To: Ulf Zimmermann Subject: Re: USB UHCI speed issue ? Cc: hackers@FreeBSD.ORG, Josef Karthauser Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Feb-02 Ulf Zimmermann wrote: > On Sun, Jan 20, 2002 at 11:23:49AM +0000, Josef Karthauser wrote: >> On Sat, Jan 19, 2002 at 05:39:56PM -0800, Duane H. Hesser wrote: >> > >> > I can confirm the problem, and point you to a message in the "current" >> > archives (Dec 15) which contains a simple 3 or 4 line patch to uhui.c. >> > The message, authored by Andrew Gordon, may be found at >> > >> > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=775757+780830+/usr/local/www/db/text/2001/freebsd-current/20011216.freebsd-c >> > urren >> > t >> >> Hmm. :) Looking at the NetBSD code, they made a major commit to fix the >> same issue: >> >> uhci.c revision 1.123 >> date: 2000/08/13 16:18:09; author: augustss; state: Exp; lines: +136 -31 >> Implement what in Intel-speech is known as "bandwidth reclamation". >> It means that we continously poll USB devices that have a pending transfer >> instead of polling just once every ms. This speeds up some transfers >> at the expense of using more PCI bandwidth. >> >> I'm looking at what is necessary to port that change over. >> >> Joe > > I was wondering if this has been ported over and if so, how about a -stable > version. > > -- > Regards, Ulf. > Josef Karthauser has reported that the NetBSD changes to address this problem are much more complex than the patch above; he is working on importing them to -current, but it may be a while before they reach -stable. In the meantime, the Gordon patch is working well for me (although I have not monitored increases in cpu time during transfers), with about a four-fold increase in tranfer rate. It's a simple change, and I plan to move it forward to 4.5 when I upgrade. -------------- Duane H. Hesser dhh@androcles.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11:20:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id E9D8537B41D for ; Fri, 8 Feb 2002 11:20:15 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020208192010.HCGU1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Fri, 8 Feb 2002 19:20:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA02957; Fri, 8 Feb 2002 11:01:19 -0800 (PST) Date: Fri, 8 Feb 2002 11:01:17 -0800 (PST) From: Julian Elischer To: "Duane H. Hesser" Cc: Markus Stumpf , freebsd-hackers@FreeBSD.ORG Subject: RE: dump(8) race conditions? In-Reply-To: <200202081855.g18ItgK66957@androcles.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Feb 2002, Duane H. Hesser wrote: > > Dump is a two pass system, and any activity which modifies inodes > between the first pass and the second is likely to cause problems, > either for dump or for restore. It has always been thus, even as > far back as V7 (and probably v6). This is why you shouild use Kirk's new "snapshot" technology. it makes a frozen image of the filesystem that can be dumped. the snapshot file contains only metadata and data that id different between the current fs and as it was at snapshot time, so as the current filesystem changes, the snapshot file gets more and more 'diff' data put into it by the filesystem. > [...] > > It is operationally (and sometimes "politically") difficult to dump > on unmounted filesystems, so most of us (I think) "bite the bullet" > and try to dump at times when the subject filesystem is likely to > be quiescent. It may also be smart to dump more frequently than > otherwise called for, just to increase the odds. [find out about snapshots] it IS conceivable that snapshots might be retrofitted to 4.x, unlike some other 5.x features, because they depend on teh soft updates code which is already present. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11:36:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 730EC37B41C; Fri, 8 Feb 2002 11:36:30 -0800 (PST) Received: from [192.168.1.129] (212.129.11.210) by mail.libertysurf.net (5.1.053) id 3C633EE70002F95C; Fri, 8 Feb 2002 20:36:07 +0100 Date: Thu, 7 Feb 2002 21:36:11 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Terry Lambert Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks In-Reply-To: <3C64196C.CC0318FD@mindspring.com> Message-ID: <20020207205736.W1763-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 8 Feb 2002, Terry Lambert wrote: > G=E9rard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI blo= ck > > devices in order to accomodate softwares as boot software for example t= hat > > may not be upgradable on systems still in use. > > Not a real problem, since if the device doesn't support > the 5 byte commands, it's not booting with the legacy > system software anyway, since you can't boot legacy stuff > on it. > > > > Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > This I don't understand. FreeBSD appears to have a > preference for the 6 byte commands in the drivers, > which are only used after boot. > > Further, it makes sense that you'd prefer 6 byte if > you could, since it makes your commands 60% smaller, > which should make them faster. The gain is probably no more that 1 microsecond and only applies to the first GB of hard disks (Logical Block Address is 21 bits). There are tons of other places where optimizations are more relevant than sticking with such a questionnable 6 byte commands preference in my humble opinion. Note that not only FreeBSD seems to want not to change this. > > So, unless we want to accomodate applications that still may send 6 byt= e > > commands through passthrough driver, no translator should be needed. Ju= st > > make class drivers use 10 byte commands instead. > > There has to be a reason that FreeBSD has a preference > for 6 bytes in the CAM code... ?!? The main reason could well be that I'm not the maintainer of this code. :-) > > OTOH, using 6 byte READ/WRITE commands is very restrictive if we ever w= ant > > to implemement kind of trustable disk write caching support since they = do > > not allow to selectively force media access (this is achieved by the FU= A > > bit in >=3D 10 byte READ/WRITE command). > > > > As a result, no device should be quirked nowadays as failing READ/WRITE= 6 > > byte commands. Just maintained softwares should get rid of those comman= ds > > asap. > > It sounds like devices that only support 6 byte commands > are the ones that need quirked? Speaking about direct access devices, may-be none has to be so or just a few number of them: - SCSI-1 devices only knew about READ(6)/WRITE(6) commands. - SCSI-2 made READ(10) mandatory, WRITE(10) being optional but just because read-only devices exist. Supporting READ(10) but only WRITE(6) for a read/write device looking like a great strangeness to me. This should be checked for other device types... > In other words, you're just reversing the default and > the fallback positions. > > I think auto-detecting the quirk is still a good bet, > even in the 6 byte only case, just as it would have > been in the 10 byte only case. May-be just applying simple rules based on [SCSI version | SCSI plagiarism (ex: USDB, ATAPI,...)] + Device type should avoid autodetection in most situations. > Thanks for the info on what's supposed to be done going > forward, though. If there's no performance issue with > 10 byte commands, inverting the default and the quirk > handling in the failure case seems to be the right thing > to do. The performance issue is certainly negligible (~ 1 micro-second), and as I wrote above it only applies to the first GB of disks. (Additionnaly, the tranfer length is limited to 256 sectors) So, unless we want to advertise about best support for 1 GB hard disks, better not to mix disk performance issue with 6 byte command preference, in my humble opinion. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11:45:20 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from alcatraz.iptelecom.net.ua (alcatraz.iptelecom.net.ua [212.9.224.15]) by hub.freebsd.org (Postfix) with ESMTP id 5F61037B420; Fri, 8 Feb 2002 11:45:07 -0800 (PST) Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by alcatraz.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id VAA94716; Fri, 8 Feb 2002 21:44:50 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (h37.228.dialup.iptcom.net [212.9.228.37]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id VAA36835; Fri, 8 Feb 2002 21:44:46 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g18JKMd69847; Fri, 8 Feb 2002 21:20:22 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3C642503.168DDF93@FreeBSD.org> Date: Fri, 08 Feb 2002 21:20:35 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Terry Lambert Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> <3C6410A6.495CFD3A@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Maxim Sobolev wrote: > > But no library has it here! libc comes out of blue just before libc_r > > - see attached script. Perhaps I'm missing something, but I can't > > figure out where it comes from, could you? > > What does your patched ldd say about each and every one > of those .so's you are linking in perhaps being linked > against libc.so, or linked against something linked > against something ... linked against something linked > against libc.so? It reports the full chain, so that when A.so depends on B.so, while B.so depends on C.so, but A.so doesn't explicitly depend on C.so, `ldd A.so' will show both B.so and C.so. > Are *any* of the object files created with "ld -r"? I don't think so. > Which binutils are you using? $ ld -v GNU ld version 2.11.2 20010719 [FreeBSD] (with BFD 2.11.2 20010719 [FreeBSD]) -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11:46:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 8A42337B4A8 for ; Fri, 8 Feb 2002 11:46:23 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id g18Jk8Y83164; Fri, 8 Feb 2002 11:46:08 -0800 (PST) (envelope-from obrien) Date: Fri, 8 Feb 2002 11:46:08 -0800 From: "David O'Brien" To: Marco Molteni Cc: freebsd-hackers@freebsd.org Subject: Re: upgrading to the new version of libpcap? Message-ID: <20020208114608.A43908@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020208181505.A46981@cobweb.example.org> <20020208183424.A50136@cobweb.example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020208183424.A50136@cobweb.example.org>; from molter@tin.it on Fri, Feb 08, 2002 at 06:34:24PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 06:34:24PM +0100, Marco Molteni wrote: > Please find included a small patch to src/contrib/libpcap/FREEBSD-upgrade Committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 11:49:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 06C5C37B41F for ; Fri, 8 Feb 2002 11:49:37 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id A6F652F6; Fri, 8 Feb 2002 19:49:35 +0000 (GMT) Date: Fri, 8 Feb 2002 19:49:35 +0000 From: Josef Karthauser To: "Duane H. Hesser" Cc: Ulf Zimmermann , hackers@FreeBSD.ORG, Josef Karthauser Subject: Re: USB UHCI speed issue ? Message-ID: <20020208194935.D64209@genius.tao.org.uk> References: <20020207152736.T45642@seven.alameda.net> <200202081906.g18J6Lw67038@androcles.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EY/WZ/HvNxOox07X" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202081906.g18J6Lw67038@androcles.com>; from dhh@androcles.com on Fri, Feb 08, 2002 at 11:06:21AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --EY/WZ/HvNxOox07X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 08, 2002 at 11:06:21AM -0800, Duane H. Hesser wrote: > > I was wondering if this has been ported over and if so, how about a -st= able > > version. >=20 > Josef Karthauser has reported that the NetBSD changes to address this pro= blem > are much more complex than the patch above; he is working on importing th= em > to -current, but it may be a while before they reach -stable. It has been merged to -current. I'll look at the merge to -stable, but I've not got any -stable hardware with USB to test on. Joe --EY/WZ/HvNxOox07X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxkK88ACgkQXVIcjOaxUBbPKACg5ps9BZa2G8hNLrfcLHTTBFJS crsAnjoXf88iohG8D/c6uR5DsLTTpYTg =5Vn9 -----END PGP SIGNATURE----- --EY/WZ/HvNxOox07X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 13:51:16 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f127.law3.hotmail.com [209.185.241.127]) by hub.freebsd.org (Postfix) with ESMTP id F020A37B41A for ; Fri, 8 Feb 2002 13:51:12 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 8 Feb 2002 13:51:12 -0800 Received: from 205.158.104.176 by lw3fd.law3.hotmail.msn.com with HTTP; Fri, 08 Feb 2002 21:51:12 GMT X-Originating-IP: [205.158.104.176] From: "Srinivas Dharmasanam" To: n_hibma@qubesoft.com Cc: freebsd-hackers@freebsd.org Subject: USB device framework in FreeBSD 4.2 Date: Fri, 08 Feb 2002 13:51:12 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 08 Feb 2002 21:51:12.0729 (UTC) FILETIME=[B9B0C490:01C1B0EA] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nick, I'm trying to use a modified version of the ugen driver in FreeBSD 4.2 to control a USB device from the kernel space and am getting a kernel crash with a page fault trap (trap_fatal) when I try to do open on this device. From a user process, I am able to open this device with no problem but when I call the underlying open() function from an ISR (so that I get kernel mode), I get this fatal trap. The backtrace of the kernel core dump is pasted below. Note that the usbd_transfer() function in usbdi.c has the call tsleep() that is causing this trap. Can you please let me know how I would be able to access a USB device from the kernel space? Do I have to write another USB driver along with the usbdi.c interface or is there a way I can do this with the existing USB device framework? Thanks, -Srinivas _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 16:53:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from neo.spbnit.ru (mail.spbnit.ru [212.48.192.115]) by hub.freebsd.org (Postfix) with ESMTP id 03B6A37B41D for ; Fri, 8 Feb 2002 16:53:13 -0800 (PST) Received: from default (ppp-135.pool-121.spbnit.ru [212.48.199.135]) by neo.spbnit.ru (8.9.3+mPOP/8.9.3) with ESMTP id DAA62563; Sat, 9 Feb 2002 03:52:05 +0300 (MSK) Message-Id: <200202090052.DAA62563@neo.spbnit.ru> From: "Vladislav V. Anikiev" To: "Brian Reichert" Cc: Subject: Re: MAC address Date: Sat, 9 Feb 2002 04:10:19 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Brian, The MAC address - I meen The Media Access Control address (i.e., ethernet hardware address, not IP address). I want to use the default hardware (not current physical ) address in my license management software. Why did you write: "Depending on the NIC". The NIC means Network Information Center. Doesn't it ? Vladislav ---------- > Îò: Brian Reichert > Êîìó: Vladislav V. Anikiev > Êîïèÿ: freebsd-hackers@FreeBSD.ORG > Òåìà: Re: MAC address > Äàòà: 8 ôåâðàëÿ 2002 ã. 5:45 > > On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > > > Hello everyone, > > > > I'm writing some license management software. It needs to be node-locked. > > I would like to use an ethernet MAC address. There are two addresses > > (default hardware address and current physical address). I would prefer to > > use the default hardware address, because it can't be changed by setting in > > software. > > Depending on the NIC, the MAC address _can_ be changed. Unless > I've completely misunderstood you... > > And, what if you have two NICs? > > > How can I take this default hardware address (I'm using FreeBSD 4.4 > > curently)? > > The output from 'dmesg' seems to record the device's MAC address > before it mght get changed via ifconfig. But, that's not preserved > forever... > > > I've found out the way how it works in "ifconfig", but in this case I've > > got the current physical address, I think (right?), which can be changed. > > > > Help me, please > > > > Vladislav > > -- > Brian 'you Bastard' Reichert > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA Intel architecture: the left-hand path > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17: 0:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from neo.spbnit.ru (mail.spbnit.ru [212.48.192.115]) by hub.freebsd.org (Postfix) with ESMTP id B758937B405 for ; Fri, 8 Feb 2002 17:00:16 -0800 (PST) Received: from default (ppp-7.pool-113.spbnit.ru [212.48.205.7]) by neo.spbnit.ru (8.9.3+mPOP/8.9.3) with ESMTP id DAA62977; Sat, 9 Feb 2002 03:59:17 +0300 (MSK) Message-Id: <200202090059.DAA62977@neo.spbnit.ru> From: "Vladislav V. Anikiev" To: "Brian Reichert" Cc: Subject: Re: Re: MAC address Date: Sat, 9 Feb 2002 04:20:02 +0300 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1157 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Brian, The MAC address - I meen The Media Access Control address (i.e., ethernet hardware address, not IP address). I want to use the default hardware (not current physical ) address in my license management software. Why did you write: "Depending on the NIC". The NIC means Network Information Center. Doesn't it ? Vladislav ---------- > Îò: Brian Reichert > Êîìó: Vladislav V. Anikiev > Êîïèÿ: freebsd-hackers@FreeBSD.ORG > Òåìà: Re: MAC address > Äàòà: 8 ôåâðàëÿ 2002 ã. 5:45 > > On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > > > Hello everyone, > > > > I'm writing some license management software. It needs to be node-locked. > > I would like to use an ethernet MAC address. There are two addresses > > (default hardware address and current physical address). I would prefer to > > use the default hardware address, because it can't be changed by setting in > > software. > > Depending on the NIC, the MAC address _can_ be changed. Unless > I've completely misunderstood you... > > And, what if you have two NICs? > > > How can I take this default hardware address (I'm using FreeBSD 4.4 > > curently)? > > The output from 'dmesg' seems to record the device's MAC address > before it mght get changed via ifconfig. But, that's not preserved > forever... > > > I've found out the way how it works in "ifconfig", but in this case I've > > got the current physical address, I think (right?), which can be changed. > > > > Help me, please > > > > Vladislav > > -- > Brian 'you Bastard' Reichert > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA Intel architecture: the left-hand path > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17: 6:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-40.dsl.lsan03.pacbell.net [64.165.226.40]) by hub.freebsd.org (Postfix) with ESMTP id 8E88F37B41C for ; Fri, 8 Feb 2002 17:06:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B939466D8B; Fri, 8 Feb 2002 17:06:42 -0800 (PST) Date: Fri, 8 Feb 2002 17:06:42 -0800 From: Kris Kennaway To: Marco Molteni Cc: freebsd-hackers@freebsd.org Subject: Re: upgrading to the new version of libpcap? Message-ID: <20020208170641.A86860@xor.obsecurity.org> References: <20020208181016.A39670@cobweb.example.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020208181016.A39670@cobweb.example.org>; from molter@tin.it on Fri, Feb 08, 2002 at 06:10:16PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 08, 2002 at 06:10:16PM +0100, Marco Molteni wrote: > Hi, >=20 > FreeBSD -current and -stable have libpcap 0.6.2, imported 10 months > ago. The current libpcap from www.tcpdump.org is 0.7.1 (and has > features I am interested in, namely the parsing of 802.11 frames). > Is there a rule on how/when to update to a newer version? Try pestering the person who imported the last version. Kris --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8ZHYhWry0BWjoQKURAn1hAKCSNOBzNe8WfV/gIyCFEB75FMvbFACg/0zi KsOh1yviKLBdX5rgcsDSVlo= =TtQ6 -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17:10:25 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from saruman.xwin.net (saruman.xwin.net [205.219.158.250]) by hub.freebsd.org (Postfix) with ESMTP id 4CCC837B402 for ; Fri, 8 Feb 2002 17:10:15 -0800 (PST) Received: from localhost (dp@localhost) by saruman.xwin.net (8.11.4/8.11.4) with ESMTP id g191BAl23577; Fri, 8 Feb 2002 19:11:10 -0600 Date: Fri, 8 Feb 2002 19:11:10 -0600 (CST) From: Paul Halliday X-X-Sender: To: "Vladislav V. Anikiev" Cc: Brian Reichert , Subject: Re: Re: MAC address In-Reply-To: <200202090059.DAA62977@neo.spbnit.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG NIC is an abbreviation sometimes used to describe a Network interface. It is not an acronym. Paul H. "Don't underestimate the power of stupid people in large groups" ___________________ http://dp.penix.org On Sat, 9 Feb 2002, Vladislav V. Anikiev wrote: > > Hello Brian, > > The MAC address - I meen The Media Access Control address (i.e., ethern= et > hardware address, not IP address). I want to use the default hardware (no= t > current physical ) address in my license management software. > > Why did you write: "Depending on the NIC". The NIC means Network > Information Center. Doesn't it ? > > Vladislav > > ---------- > > =CE=F2: Brian Reichert > > =CA=EE=EC=F3: Vladislav V. Anikiev > > =CA=EE=EF=E8=FF: freebsd-hackers@FreeBSD.ORG > > =D2=E5=EC=E0: Re: MAC address > > =C4=E0=F2=E0: 8 =F4=E5=E2=F0=E0=EB=FF 2002 =E3. 5:45 > > > > On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > > > > > Hello everyone, > > > > > > I'm writing some license management software. It needs to be > node-locked. > > > I would like to use an ethernet MAC address. There are two addresses > > > (default hardware address and current physical address). I would pref= er > to > > > use the default hardware address, because it can't be changed by > setting in > > > software. > > > > Depending on the NIC, the MAC address _can_ be changed. Unless > > I've completely misunderstood you... > > > > And, what if you have two NICs? > > > > > How can I take this default hardware address (I'm using FreeBSD 4.= 4 > > > curently)? > > > > The output from 'dmesg' seems to record the device's MAC address > > before it mght get changed via ifconfig. But, that's not preserved > > forever... > > > > > I've found out the way how it works in "ifconfig", but in this case > I've > > > got the current physical address, I think (right?), which can be > changed. > > > > > > Help me, please > > > > > > Vladislav > > > > -- > > Brian 'you Bastard' Reichert=09=09 > > 37 Crystal Ave. #303=09=09=09Daytime number: (603) 434-6842 > > Derry NH 03038-1713 USA=09=09=09Intel architecture: the left-hand path > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17:13:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 28ADB37B483 for ; Fri, 8 Feb 2002 17:12:20 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id g191CGp37888; Fri, 8 Feb 2002 20:12:16 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200202090052.DAA62563@neo.spbnit.ru> References: <200202090052.DAA62563@neo.spbnit.ru> Date: Fri, 8 Feb 2002 20:12:15 -0500 To: "Vladislav V. Anikiev" , "Brian Reichert" From: Garance A Drosihn Subject: Re: MAC address Cc: Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 4:10 AM +0300 2/9/02, Vladislav V. Anikiev wrote: > Hello Brian, > > The MAC address - I meen The Media Access Control address (i.e., ethernet >hardware address, not IP address). I want to use the default hardware (not >current physical ) address in my license management software. > > Why did you write: "Depending on the NIC". The NIC means Network >Information Center. Doesn't it ? This is a case of TOL (TLA OverLoad)... (TLA = Three-Letter Acronyms) NIC can also mean Network Interface Card, and each card will (hopefully) have it's own unique MAC address. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17:16:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.taconic.net (mail.taconic.net [205.231.144.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A4BB37B420 for ; Fri, 8 Feb 2002 17:16:21 -0800 (PST) Received: from coyotepoint.com ([205.231.27.66]) by mail.taconic.net (8.10.2+Sun/8.11.4) with ESMTP id g191GEp14872 for ; Fri, 8 Feb 2002 20:16:15 -0500 (EST) Message-ID: <3C6478BE.BE6F5A70@coyotepoint.com> Date: Fri, 08 Feb 2002 20:17:50 -0500 From: Bill Kish X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers Subject: Debugging double page fault Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, I've recently started seeing "double fault" panics on a formerly FreeBSD 2.2.8 based system (It's running 2.2.8 as a somewhat embedded OS, so please don't flame me about being back rev!) The stack trace looks like: $ gdb -k kernel.0 vmcore.0 GDB 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...(no debugging symbols found)... IdlePTD 1aa000 current pcb at 1967a0 panic: double fault #0 0xf010cf63 in boot () (kgdb) bt #0 0xf010cf63 in boot () #1 0xf010d232 in panic () #2 0xf0176f5a in trap_fatal () #3 0xf0176a1c in trap_pfault () #4 0xf01766df in trap () #5 0xf012baae in vget () #6 0xf01558dc in ffs_sync () #7 0xf012cf7b in sync () #8 0xf010ce2d in boot () #9 0xf010d232 in panic () #10 0xf0176ff0 in trapwrite () (kgdb) My rough understanding is that double faults are usually the result of running out of stack, and that the underlying cause of the panic can probably be uncovered if I can find the previous stack . Can anyone point me towards some hints for debugging this sort of crash. Any advice greatly appreciated. -=BK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17:21:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id BDC4937B42B for ; Fri, 8 Feb 2002 17:20:22 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020209012022.QAKM1214.rwcrmhc54.attbi.com@InterJet.elischer.org>; Sat, 9 Feb 2002 01:20:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA04339; Fri, 8 Feb 2002 17:04:34 -0800 (PST) Date: Fri, 8 Feb 2002 17:04:33 -0800 (PST) From: Julian Elischer To: "Vladislav V. Anikiev" Cc: Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: Re: MAC address In-Reply-To: <200202090059.DAA62977@neo.spbnit.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Network Interface Card On Sat, 9 Feb 2002, Vladislav V. Anikiev wrote: >=20 > Hello Brian, >=20 > The MAC address - I meen The Media Access Control address (i.e., ethern= et > hardware address, not IP address). I want to use the default hardware (no= t > current physical ) address in my license management software. >=20 > Why did you write: "Depending on the NIC". The NIC means Network > Information Center. Doesn't it ? >=20 > Vladislav >=20 > ---------- > > =CE=F2: Brian Reichert > > =CA=EE=EC=F3: Vladislav V. Anikiev > > =CA=EE=EF=E8=FF: freebsd-hackers@FreeBSD.ORG > > =D2=E5=EC=E0: Re: MAC address > > =C4=E0=F2=E0: 8 =F4=E5=E2=F0=E0=EB=FF 2002 =E3. 5:45 > >=20 > > On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > >=20 > > > Hello everyone, > > >=20 > > > I'm writing some license management software. It needs to be > node-locked. > > > I would like to use an ethernet MAC address. There are two addresses > > > (default hardware address and current physical address). I would pref= er > to > > > use the default hardware address, because it can't be changed by > setting in > > > software. > >=20 > > Depending on the NIC, the MAC address _can_ be changed. Unless > > I've completely misunderstood you... > >=20 > > And, what if you have two NICs? > >=20 > > > How can I take this default hardware address (I'm using FreeBSD 4.= 4 > > > curently)? > >=20 > > The output from 'dmesg' seems to record the device's MAC address > > before it mght get changed via ifconfig. But, that's not preserved > > forever... > >=20 > > > I've found out the way how it works in "ifconfig", but in this case > I've > > > got the current physical address, I think (right?), which can be > changed. > > >=20 > > > Help me, please > > >=20 > > > Vladislav > >=20 > > --=20 > > Brian 'you Bastard' Reichert=09=09 > > 37 Crystal Ave. #303=09=09=09Daytime number: (603) 434-6842 > > Derry NH 03038-1713 USA=09=09=09Intel architecture: the left-hand path > >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 17:38:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 02E7D37B405 for ; Fri, 8 Feb 2002 17:38:12 -0800 (PST) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id EAA14955; Sat, 9 Feb 2002 04:45:13 +0300 (MSK) Message-Id: <200202090145.EAA14955@aaz.links.ru> Subject: Re: MAC address In-Reply-To: <200202090052.DAA62563@neo.spbnit.ru> from "Vladislav V. Anikiev" at "Feb 9, 2 04:10:19 am" To: vladani@mail.spbnit.ru (Vladislav V. Anikiev) Date: Sat, 9 Feb 2002 04:38:46 +0300 (MSK) Cc: reichert@numachi.com, freebsd-hackers@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vladislav V. Anikiev writes: > The MAC address - I meen The Media Access Control address (i.e., ethernet > hardware address, not IP address). I want to use the default hardware (not > current physical ) address in my license management software. MAC address is stored in flash. It is easy to reprogram any MAC in many NICs > Why did you write: "Depending on the NIC". The NIC means Network > Information Center. Doesn't it ? Network Interface Card BTW there is the only easy way to prevent programm from distribution - rm BEFORE(instead) first distribution. No other easy way. And no need. Just take money from service. > Vladislav > > ---------- > > __: Brian Reichert > > ____: Vladislav V. Anikiev > > _____: freebsd-hackers@FreeBSD.ORG > > ____: Re: MAC address > > ____: 8 _______ 2002 _. 5:45 > > > > On Thu, Feb 07, 2002 at 10:45:01PM +0300, Vladislav V. Anikiev wrote: > > > > > > Hello everyone, > > > > > > I'm writing some license management software. It needs to be > node-locked. > > > I would like to use an ethernet MAC address. There are two addresses > > > (default hardware address and current physical address). I would prefer > to > > > use the default hardware address, because it can't be changed by > setting in > > > software. > > > > Depending on the NIC, the MAC address _can_ be changed. Unless > > I've completely misunderstood you... > > > > And, what if you have two NICs? > > > > > How can I take this default hardware address (I'm using FreeBSD 4.4 > > > curently)? > > > > The output from 'dmesg' seems to record the device's MAC address > > before it mght get changed via ifconfig. But, that's not preserved > > forever... > > > > > I've found out the way how it works in "ifconfig", but in this case > I've > > > got the current physical address, I think (right?), which can be > changed. > > > > > > Help me, please > > > > > > Vladislav > > > > -- > > Brian 'you Bastard' Reichert > > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > > Derry NH 03038-1713 USA Intel architecture: the left-hand path > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 18:15:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from magnum.tsua.net (magnum.tsua.net [212.40.34.2]) by hub.freebsd.org (Postfix) with ESMTP id AC0F237B416 for ; Fri, 8 Feb 2002 18:15:25 -0800 (PST) Received: from citadel.icyb.net.ua (root@citadel.icyb.net.ua [212.40.38.140]) by magnum.tsua.net (8.11.6/8.11.5) with ESMTP id g192FAi57665; Sat, 9 Feb 2002 04:15:10 +0200 (EET) (envelope-from diman@landsystems.com.ua) Received: from core.is.kiev.ua (gw.landsystems.com.ua [212.40.38.105]) by citadel.icyb.net.ua (8.8.8/ICyb-2.3exp) with ESMTP id EAA17166; Sat, 9 Feb 2002 04:15:05 +0200 (EET) (envelope-from diman@landsystems.com.ua) Received: from localhost (core.asd-g.com [62.244.5.177] (may be forged)) by core.is.kiev.ua (8.11.1/ASDG-2.3-NR) with ESMTP id g192Evu85319; Sat, 9 Feb 2002 04:14:58 +0200 (EET) (envelope-from diman@landsystems.com.ua) Date: Sat, 9 Feb 2002 05:20:59 +0000 (GMT) From: diman X-X-Sender: To: <"\".\""@babolo.ru> Cc: , , Subject: Re: MAC address In-Reply-To: <200202090145.EAA14955@aaz.links.ru> Message-ID: <20020209045653.H1957-100000@portal.none.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 9 Feb 2002 "."@babolo.ru wrote: > Vladislav V. Anikiev writes: > > The MAC address - I meen The Media Access Control address (i.e., ethernet > > hardware address, not IP address). I want to use the default hardware (not > > current physical ) address in my license management software. > MAC address is stored in flash. > It is easy to reprogram any MAC in many NICs I have once pressed reset while running vendor's 'test NIC EEPROM' program and have found after reboot that my card has A5:A5:A5:A5:A5:A5 MAC now :-) But if you know an EEPROM layout and how to read/write it you can use your network card as real electonic key like HASP :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 18:21:49 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from pr0n.kutulu.org (pr0n.kutulu.org [151.196.107.157]) by hub.freebsd.org (Postfix) with ESMTP id 938D837B41E for ; Fri, 8 Feb 2002 18:21:45 -0800 (PST) Received: from cc191573g (beta.kutulu.org [68.50.102.129]) by pr0n.kutulu.org (Postfix) with SMTP id DC67212E for ; Fri, 8 Feb 2002 21:25:48 -0500 (EST) Message-ID: <005601c1b128$3fcd9390$81663244@longhill1.md.home.com> From: "Kutulu" Cc: References: Subject: Re: Re: MAC address Date: Fri, 8 Feb 2002 21:11:36 -0800 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Paul Halliday" > NIC is an abbreviation sometimes used to describe a Network interface. > It is not an acronym. Network Interface Card (?) --K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19: 3:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id CDC7437B405; Fri, 8 Feb 2002 19:03:43 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZNnC-00078N-00; Fri, 08 Feb 2002 19:03:15 -0800 Message-ID: <3C648F73.1663C5E9@mindspring.com> Date: Fri, 08 Feb 2002 18:54:43 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?G=E9rard?= Roudier Cc: Josef Karthauser , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List Subject: Re: USB "Memorybird" quirks References: <20020207205736.W1763-100000@gerard> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG G=E9rard Roudier wrote: > The performance issue is certainly negligible (~ 1 micro-second), and a= s I > wrote above it only applies to the first GB of disks. (Additionnaly, th= e > tranfer length is limited to 256 sectors) > = > So, unless we want to advertise about best support for 1 GB hard disks,= > better not to mix disk performance issue with 6 byte command preference= , > in my humble opinion. :-) You want to create some patches? I'm not really a CAM-head. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:11:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id E513A37B421; Fri, 8 Feb 2002 19:11:29 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZNv7-0006vH-00; Fri, 08 Feb 2002 19:11:26 -0800 Message-ID: <3C649147.BB4F28C9@mindspring.com> Date: Fri, 08 Feb 2002 19:02:31 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: Ruslan Ermilov , Jason Evans , jdp@FreeBSD.org, deischen@FreeBSD.org, jasone@FreeBSD.org, hackers@FreeBSD.org, jlemon@FreeBSD.org Subject: Re: Linking libc before libc_r into application causes weird problems References: <1013147180.73417.2.camel@notebook> <20020207234233.D23162@canonware.com> <3C639A8C.6D100326@FreeBSD.org> <3C63A62D.3E4A4FC4@mindspring.com> <3C63AD02.79BA5AF5@FreeBSD.org> <20020208164132.D78163@sunbay.com> <3C63E5D1.1E423698@FreeBSD.org> <3C63E961.45706408@mindspring.com> <20020208172503.H78163@sunbay.com> <3C63F3FE.D4E73334@FreeBSD.org> <3C6410A6.495CFD3A@mindspring.com> <3C642503.168DDF93@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > What does your patched ldd say about each and every one > > of those .so's you are linking in perhaps being linked > > against libc.so, or linked against something linked > > against something ... linked against something linked > > against libc.so? > > It reports the full chain, so that when A.so depends on B.so, while > B.so depends on C.so, but A.so doesn't explicitly depend on C.so, `ldd > A.so' will show both B.so and C.so. Was your ldd output your patched ldd, or not? > > Which binutils are you using? > > $ ld -v > GNU ld version 2.11.2 20010719 [FreeBSD] (with BFD 2.11.2 20010719 > [FreeBSD]) Is this one of the three revisions of the new one, or the old one? If it's not the old one, try the old one. If it's the new one, make sure it's the newest new one. > > Are *any* of the object files created with "ld -r"? > > I don't think so. Then it looks like you are going to have to "nm" each of the object files to see if they define a libc routine. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:13:12 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 07EA637B41A for ; Fri, 8 Feb 2002 19:12:52 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZNwD-0000yV-00; Fri, 08 Feb 2002 19:12:39 -0800 Message-ID: <3C6491B1.5518EFD8@mindspring.com> Date: Fri, 08 Feb 2002 19:04:17 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: "Duane H. Hesser" , Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: USB UHCI speed issue ? References: <20020207152736.T45642@seven.alameda.net> <200202081906.g18J6Lw67038@androcles.com> <20020208194935.D64209@genius.tao.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Josef Karthauser wrote: > It has been merged to -current. I'll look at the merge to -stable, but > I've not got any -stable hardware with USB to test on. Oh, oh, the jokes... must... resist... the... jokes... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:29: 4 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 13E3B37B404 for ; Fri, 8 Feb 2002 19:28:59 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZOBk-0007Hc-00; Fri, 08 Feb 2002 19:28:38 -0800 Message-ID: <3C649564.F51D18BE@mindspring.com> Date: Fri, 08 Feb 2002 19:20:04 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Vladislav V. Anikiev" Cc: Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address References: <200202090052.DAA62563@neo.spbnit.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Vladislav V. Anikiev" wrote: > > Hello Brian, > > The MAC address - I meen The Media Access Control address (i.e., ethernet > hardware address, not IP address). I want to use the default hardware (not > current physical ) address in my license management software. > > Why did you write: "Depending on the NIC". The NIC means Network > Information Center. Doesn't it ? Network Interface Card. Some NICs allow you to change the default MAC address by reflashing the BIOS in them. There are tools to do this in software. The common reason for doing this is to replace a dead NIC card with a new NIC card, so that you can still use all the same licenses with the same license manager software, which is node-locked. 8-). Another reason to do this is to de3feat license managers. Typically, people who are really anal about their license management then respond by using a cryptographic dongle. Crackers then respond by making the kernel act as if the dongle hardware were local, and proxying the dongle requests across the network to a real dongle on some other machine. Perhaps you can use the Pentium unique ID? This is what Microsoft does for XP online registration: they turn on the unique ID feature, get the unique ID to uniquely identify you, and then upload all sorts of demographic information about your machine to them, to better maintain their monopoly by forcing users of their products to provide demographic information to them that no one else has access to, putting them in a stronger position to know what hardware to target with their software products. If you were to use the unique ID, by loading a kernel module, turning it on in protected mode, and then reading the unique ID, then turning it off, you could be just like Microsoft Windows XP machine identification. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:35:23 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 20F8537B41B for ; Fri, 8 Feb 2002 19:35:21 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZOIC-0006bp-00; Fri, 08 Feb 2002 19:35:15 -0800 Message-ID: <3C6496F9.199A6309@mindspring.com> Date: Fri, 08 Feb 2002 19:26:49 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Garance A Drosihn Cc: "Vladislav V. Anikiev" , Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address References: <200202090052.DAA62563@neo.spbnit.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garance A Drosihn wrote: > NIC can also mean Network Interface Card, and each card will (hopefully) > have it's own unique MAC address. It's Simple: NIC = MAC + PHI + BI A NIC (Network Interface Card) is a MAC (Media Access Controller) plus a PHI (Physical Hardware Interface) plus a BI (Bus Interface). Oh, "PHI" is pronounced "fie", and "BI" is pronounced "bye". 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:39:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id 7D24237B417 for ; Fri, 8 Feb 2002 19:39:16 -0800 (PST) Received: from pool0053.cvx21-bradley.dialup.earthlink.net ([209.179.192.53] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZOLu-0002vi-00; Fri, 08 Feb 2002 19:39:05 -0800 Message-ID: <3C6497EA.73CDEC64@mindspring.com> Date: Fri, 08 Feb 2002 19:30:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Kish Cc: hackers Subject: Re: Debugging double page fault References: <3C6478BE.BE6F5A70@coyotepoint.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Kish wrote: > I've recently started seeing "double fault" panics on a formerly FreeBSD > 2.2.8 based system (It's running 2.2.8 as a somewhat embedded OS, so please > don't flame me about being back rev!) [ ... ] > My rough understanding is that double faults are usually the result of > running out of stack, and that the underlying cause of the panic can probably > be uncovered if I can find the previous stack . > > Can anyone point me towards some hints for debugging this sort of crash. Any > advice greatly appreciated. It's very old. This makes me think that it used to work, and now it doesn't. What did you change just before it stopped working? If nothing, then it's likely a hardware problem. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 19:49:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 5ACA837B405 for ; Fri, 8 Feb 2002 19:49:14 -0800 (PST) Received: (qmail 14889 invoked from network); 9 Feb 2002 03:49:13 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.90.117.49]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 03:49:13 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020207193911.U1513-100000@gerard> Date: Fri, 08 Feb 2002 22:49:08 -0500 (EST) From: John Baldwin To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Subject: Re: USB "Memorybird" quirks Cc: FreeBSD Hackers Mailing List , Cc: FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert , Josef Karthauser Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Feb-02 Gérard Roudier wrote: > > On Thu, 7 Feb 2002, Josef Karthauser wrote: > >> On Thu, Feb 07, 2002 at 03:52:26PM -0800, Terry Lambert wrote: >> > > >> > > IIRC this problem is being addressed at a more fundamental level on >> > > -current, by adding a 6-byte-to-10-byte READ command translator >> > > somewhere in the abstraction layer. >> > >> > Could this be "auto-quirked"? >> > >> >> As in, try a 6 byte command, and if that fails try a 10 byte command >> instead? >> >> Unfortunately although I'm maintaining USB in -current, I don't have a >> complete in depth understanding of the code yet. :( I'm mainly trying >> to fix my problems by taking from NetBSD. > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > devices in order to accomodate softwares as boot software for example that > may not be upgradable on systems still in use. Softwares that are > maintained should no longer use 6 byte commands, but use the 10 byte > commands replacement (for years...). Just so you know, I made the umass driver for UFI and ATA translate SCSI 6 byte commands to 10 byte commands. There is a simple function call to do the change if you wish to do this in for the SCSI transforms as well. As far as axeing 6 byte commands all together, I will plead ignorance and defer to the scsi@ list and CAM folks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 20:47:22 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from sigbus.com (we-24-126-148-218.we.mediaone.net [24.126.148.218]) by hub.freebsd.org (Postfix) with ESMTP id 3890637B41E; Fri, 8 Feb 2002 20:47:18 -0800 (PST) Received: (from henrich@localhost) by sigbus.com (8.11.1/8.11.1) id g1946VP20608; Fri, 8 Feb 2002 20:06:31 -0800 (PST) (envelope-from henrich) Date: Fri, 8 Feb 2002 20:06:31 -0800 From: Charles Henrich To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: anyone familier with bktr driver? Message-ID: <20020208200631.A20501@sigbus.com> Mail-Followup-To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F X-GPG-Fingerprint: EA4C AB9B 0C38 17C0 AB3F 11DE 41F6 5883 41E7 4F49 X-MailScanner: Found to be clean Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'd like to add support to the mplayer/mencoder software (which is turning out to be a fantastic tool, can playback and encode to all sorts of formats, from VCD's, to DVD's, to AVI files, to DIVX, etc..). There is support for the video4linux driver, as wll as an example "dummy" driver as input mechanisms. The problem is im having a hard time finding any information about the basic bktr driver, how to set it up, how to read a frame, etc.. Anyone out there who can shed some light, would be appreciated! -Crh Charles Henrich Eon Entertainment henrich@msu.edu http://www.sigbus.com:81/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 22:10:52 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 036B337B405 for ; Fri, 8 Feb 2002 22:10:50 -0800 (PST) Received: from grinch ([12.234.224.67]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020209061049.UCBB2951.rwcrmhc53.attbi.com@grinch> for ; Sat, 9 Feb 2002 06:10:49 +0000 Date: Fri, 8 Feb 2002 22:10:48 -0800 Subject: Re: USB device framework in FreeBSD 4.2 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v475) From: Justin C.Walker To: freebsd-hackers@FreeBSD.ORG Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.475) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, February 8, 2002, at 01:51 PM, Srinivas Dharmasanam wrote: > Nick, > I'm trying to use a modified version of the ugen driver in FreeBSD 4.2 > to control a USB device from the kernel space and am getting a kernel > crash with a page fault trap (trap_fatal) when I try to do open on this > device. > > From a user process, I am able to open this device with no problem but > when I call the underlying open() function from an ISR (so that I get > kernel mode), I get this fatal trap. > > The backtrace of the kernel core dump is pasted below. > > Note that the usbd_transfer() function in usbdi.c has the call tsleep() > that is causing this trap. > > Can you please let me know how I would be able to access a USB device > from the kernel space? Do I have to write another USB driver along with > the usbdi.c interface or is there a way I can do this with the existing > USB device framework? First, try usb@lists.apple.com, where the USB mavins tend to hang out. Next, be aware that the device driver model in Darwin and Mac OS X is significantly different from that in FreeBSD, so it won't be a simple matter to get this code working. Also, you don't want to call open() in the kernel, unless it is *really* necessary; if you do need to do this, which is unlikely, you should study the open() call in the kernel source to be sure you are obeying all the rules. In particular, *don't* call open() from an ISR. Finally, don't call tsleep() from an ISR. Oh, and the backtrace seems to have disappeared between the time you wrote the above and when you sent it. There are several USB components in the darwin repository; check them out and look at the code. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | It's not whether you win or lose... | It's whether *I* win or lose. *--------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 22:12:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 178D837B41C for ; Fri, 8 Feb 2002 22:12:26 -0800 (PST) Received: from grinch ([12.234.224.67]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020209061220.USXH1214.rwcrmhc54.attbi.com@grinch> for ; Sat, 9 Feb 2002 06:12:20 +0000 Date: Fri, 8 Feb 2002 22:12:20 -0800 Mime-Version: 1.0 (Apple Message framework v475) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Fwd: USB device framework in FreeBSD 4.2 From: Justin C.Walker To: freebsd-hackers@FreeBSD.ORG Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.475) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Forgive the inane chatter below. I have too many windows open, and my brain went to sleep before I did. Regards, Justin Begin forwarded message: > From: "Justin C.Walker" > Date: Fri Feb 08, 2002 10:10:48 PM US/Pacific > To: freebsd-hackers@FreeBSD.ORG > Subject: Re: USB device framework in FreeBSD 4.2 > > > On Friday, February 8, 2002, at 01:51 PM, Srinivas Dharmasanam wrote: > >> Nick, >> I'm trying to use a modified version of the ugen driver in FreeBSD 4.2 >> to control a USB device from the kernel space and am getting a kernel >> crash with a page fault trap (trap_fatal) when I try to do open on >> this device. >> >> From a user process, I am able to open this device with no problem but >> when I call the underlying open() function from an ISR (so that I get >> kernel mode), I get this fatal trap. >> >> The backtrace of the kernel core dump is pasted below. >> >> Note that the usbd_transfer() function in usbdi.c has the call >> tsleep() that is causing this trap. >> >> Can you please let me know how I would be able to access a USB device >> from the kernel space? Do I have to write another USB driver along >> with the usbdi.c interface or is there a way I can do this with the >> existing USB device framework? > > First, try usb@lists.apple.com, where the USB mavins tend to hang out. > > Next, be aware that the device driver model in Darwin and Mac OS X is > significantly different from that in FreeBSD, so it won't be a simple > matter to get this code working. > > Also, you don't want to call open() in the kernel, unless it is > *really* necessary; if you do need to do this, which is unlikely, you > should study the open() call in the kernel source to be sure you are > obeying all the rules. In particular, *don't* call open() from an ISR. > > Finally, don't call tsleep() from an ISR. > > Oh, and the backtrace seems to have disappeared between the time you > wrote the above and when you sent it. > > There are several USB components in the darwin repository; check them > out and look at the code. > > Regards, > > Justin > > -- > Justin C. Walker, Curmudgeon-At-Large * > Institute for General Semantics | It's not whether you win or > lose... > | It's whether *I* win or lose. > *--------------------------------------*-------------------------------* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Men are from Earth. | Women are from Earth. | Deal with it. *--------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 22:29:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dexter.starfire.mn.org (starfire.skypoint.net [199.199.159.71]) by hub.freebsd.org (Postfix) with ESMTP id 73D4137B41C for ; Fri, 8 Feb 2002 22:29:43 -0800 (PST) Received: (from john@localhost) by dexter.starfire.mn.org (8.11.3/8.11.3) id g196TfA00618 for freebsd-hackers@freebsd.org; Sat, 9 Feb 2002 00:29:41 -0600 (CST) (envelope-from john) Date: Sat, 9 Feb 2002 00:29:41 -0600 From: John To: freebsd-hackers@freebsd.org Subject: requesting guidance for updating the RocketPort driver Message-ID: <20020209002941.A575@dexter.starfire.mn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG *** Please reply directly, since I am not currently subscribed to this list *** It seems to be a given that Comtrol is not in a position to support and develop the driver for the RocketPort cards. I happen to be the owner of a couple of these, and I'm having problems with newer versions of FreeBSD. For one, I get Feb 8 23:35:27 dexter /kernel: rp0: driver is using old-style compatibility shims Feb 8 23:35:37 dexter /kernel: WARNING: driver rp should register devices with ma ke_dev() (dev_t = "#rp/0x10007") That'd be fine and well, if the silly thing WORKED, which it doesn't, quite. tcsetattr returns "Invalid argument" when perfectly reasonable things are going on, preventing me from running PPP on these, or indeed making other reasonable changes to the terminal line driver characteristics. I just grabbed the latest version from -stable, and it diffs against what I'm using with no changes. The version I have with FreeBSD 2.1 doesn't have the problem with setting line characteristics, but it differs in many details from the driver in -stable. I was actually working with a developer at Comtrol in 1997 (they are/were local), and I have several versions of the driver from February 24, March 11, April 10, and May 22 which may be in a more advanced state than the driver in the distribution. At any rate, I've run PPP on that version of the driver for a almost 5 years, and it has done that quite well. I'd be very happy to work on this and get a superior driver into the distribution, but I could use just a bit of hand-holding, particularly with regard to that "old style driver shims" thing. I suspect, jumping from a 1997 FreeBSD (2.1) to a 2002 FreeBSD, there may be a few bumps in the road. Can someone point me in the right direction, or provide a little hand-holding? Thanks! *** Please reply directly, since I am not currently subscribed to this list *** -- John Lind john@starfire.MN.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Feb 8 22:40:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id CF8A437B402 for ; Fri, 8 Feb 2002 22:40:20 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020209064020.XOYM1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sat, 9 Feb 2002 06:40:20 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA05504; Fri, 8 Feb 2002 22:37:51 -0800 (PST) Date: Fri, 8 Feb 2002 22:37:49 -0800 (PST) From: Julian Elischer To: John Cc: freebsd-hackers@freebsd.org Subject: Re: requesting guidance for updating the RocketPort driver In-Reply-To: <20020209002941.A575@dexter.starfire.mn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG he infrastructure needed for a new driver can be taken from the sample driver in /usr/share/examples/drivers/make_device_driver.sh IN -CURRENT. (use cvdweb on the website to get it) that will at least get rid of the 'shims' stuff. On Sat, 9 Feb 2002, John wrote: > *** Please reply directly, since I am not currently subscribed to this list *** > > It seems to be a given that Comtrol is not in a position to support > and develop the driver for the RocketPort cards. I happen to be > the owner of a couple of these, and I'm having problems with > newer versions of FreeBSD. > > For one, I get > Feb 8 23:35:27 dexter /kernel: rp0: driver is using old-style compatibility shims > Feb 8 23:35:37 dexter /kernel: WARNING: driver rp should register devices with ma > ke_dev() (dev_t = "#rp/0x10007") > > That'd be fine and well, if the silly thing WORKED, which it doesn't, > quite. tcsetattr returns "Invalid argument" when perfectly reasonable > things are going on, preventing me from running PPP on these, or > indeed making other reasonable changes to the terminal line driver > characteristics. > > I just grabbed the latest version from -stable, and it diffs against > what I'm using with no changes. The version I have with FreeBSD > 2.1 doesn't have the problem with setting line characteristics, > but it differs in many details from the driver in -stable. I was > actually working with a developer at Comtrol in 1997 (they are/were > local), and I have several versions of the driver from February > 24, March 11, April 10, and May 22 which may be in a more advanced > state than the driver in the distribution. At any rate, I've run > PPP on that version of the driver for a almost 5 years, and it has > done that quite well. > > I'd be very happy to work on this and get a superior driver into > the distribution, but I could use just a bit of hand-holding, > particularly with regard to that "old style driver shims" thing. > > I suspect, jumping from a 1997 FreeBSD (2.1) to a 2002 FreeBSD, there > may be a few bumps in the road. > > Can someone point me in the right direction, or provide a little > hand-holding? > > Thanks! > > *** Please reply directly, since I am not currently subscribed to this list *** > -- > > John Lind > john@starfire.MN.ORG > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 0:55:47 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from eagle.he.net (eagle.he.net [216.218.174.2]) by hub.freebsd.org (Postfix) with ESMTP id 65CAD37B404 for ; Sat, 9 Feb 2002 00:55:41 -0800 (PST) Received: from anjali ([61.11.16.239] (may be forged)) by eagle.he.net (8.8.6/8.8.2) with SMTP id AAA06290 for ; Sat, 9 Feb 2002 00:55:39 -0800 Message-ID: <001701c1b147$4b1fbc90$0a00a8c0@indranet> From: "Anjali Kulkarni" To: Subject: Zones Date: Sat, 9 Feb 2002 14:23:17 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C1B175.51733800" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C1B175.51733800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, This is probably not the right place for this qs., but I am posting it = here since it's a quick & easy one. Does something like the FreeBSD = zones exist in Linux ? Thanks, Anjali ------=_NextPart_000_000D_01C1B175.51733800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
This is probably not the right place = for this qs.,=20 but I am posting it here since it's a quick & easy one. Does = something=20 like the FreeBSD zones exist in Linux ?
 
Thanks,
Anjali
------=_NextPart_000_000D_01C1B175.51733800-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 1:41:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 789CD37B402 for ; Sat, 9 Feb 2002 01:41:43 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g199ffC66627; Sat, 9 Feb 2002 04:41:41 -0500 (EST) (envelope-from mwlucas) Date: Sat, 9 Feb 2002 04:41:41 -0500 From: Michael Lucas To: Anjali Kulkarni Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Zones Message-ID: <20020209044141.A66561@blackhelicopters.org> References: <001701c1b147$4b1fbc90$0a00a8c0@indranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001701c1b147$4b1fbc90$0a00a8c0@indranet>; from anjali@indranetworks.com on Sat, Feb 09, 2002 at 02:23:17PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Your best bet for general questions is the freebsd-questions@freebsd.org mailig list. It might be quick and easy, but historically, the people in -hackers are not interested in quick and easy. They're more interested in long, drawn-out, and complicated. On Sat, Feb 09, 2002 at 02:23:17PM +0530, Anjali Kulkarni wrote: > Hi, > > This is probably not the right place for this qs., but I am posting it here since it's a quick & easy one. Does something like the FreeBSD zones exist in Linux ? > > Thanks, > Anjali -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 2:54: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from eagle.he.net (eagle.he.net [216.218.174.2]) by hub.freebsd.org (Postfix) with ESMTP id AB02F37B417 for ; Sat, 9 Feb 2002 02:53:58 -0800 (PST) Received: from anjali ([61.11.16.239] (may be forged)) by eagle.he.net (8.8.6/8.8.2) with SMTP id CAA16202; Sat, 9 Feb 2002 02:53:56 -0800 Message-ID: <002301c1b157$d0c38470$0a00a8c0@indranet> From: "Anjali Kulkarni" To: "Michael Lucas" Cc: References: <001701c1b147$4b1fbc90$0a00a8c0@indranet> <20020209044141.A66561@blackhelicopters.org> Subject: Re: Zones Date: Sat, 9 Feb 2002 16:21:33 +0530 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for your reminder. I guess I didnt realize they would consider simple and easy beneath their dignity. Truly sorry for the trouble this one email caused you and others, Regards, Anjali ----- Original Message ----- From: "Michael Lucas" To: "Anjali Kulkarni" Cc: Sent: Saturday, February 09, 2002 3:11 PM Subject: Re: Zones > Hello, > > Your best bet for general questions is the > freebsd-questions@freebsd.org mailig list. > > It might be quick and easy, but historically, the people in -hackers > are not interested in quick and easy. They're more interested in > long, drawn-out, and complicated. > > On Sat, Feb 09, 2002 at 02:23:17PM +0530, Anjali Kulkarni wrote: > > Hi, > > > > This is probably not the right place for this qs., but I am posting it here since it's a quick & easy one. Does something like the FreeBSD zones exist in Linux ? > > > > Thanks, > > Anjali > > -- > Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org > my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > > http://www.blackhelicopters.org/~mwlucas/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 3:15:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id CE9C337B405 for ; Sat, 9 Feb 2002 03:15:08 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.11.6/8.11.6) id g19BF4r67013; Sat, 9 Feb 2002 06:15:04 -0500 (EST) (envelope-from mwlucas) Date: Sat, 9 Feb 2002 06:15:03 -0500 From: Michael Lucas To: Anjali Kulkarni Cc: freebsd-hackers@freebsd.org Subject: Re: Zones Message-ID: <20020209061503.A66997@blackhelicopters.org> References: <001701c1b147$4b1fbc90$0a00a8c0@indranet> <20020209044141.A66561@blackhelicopters.org> <002301c1b157$d0c38470$0a00a8c0@indranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002301c1b157$d0c38470$0a00a8c0@indranet>; from anjali@indranetworks.com on Sat, Feb 09, 2002 at 04:21:33PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It really isn't a question of beneath their dignity, it's just not what the mailing list is for. People who are interested in answering easy questions read -questions. People hwo are interested in discussing technical issues read -hackers. While there is a certain amount of overlap, you're more likely to get a better answer asking people who are interested in answering questions. ==ml PS: If I had any idea what a zone in Linux was, I would have just answered the question. Sorry. On Sat, Feb 09, 2002 at 04:21:33PM +0530, Anjali Kulkarni wrote: > Thanks for your reminder. I guess I didnt realize they would consider > simple and easy beneath their dignity. > > Truly sorry for the trouble this one email caused you and others, > Regards, > Anjali > > ----- Original Message ----- > From: "Michael Lucas" > To: "Anjali Kulkarni" > Cc: > Sent: Saturday, February 09, 2002 3:11 PM > Subject: Re: Zones > > > > Hello, > > > > Your best bet for general questions is the > > freebsd-questions@freebsd.org mailig list. > > > > It might be quick and easy, but historically, the people in -hackers > > are not interested in quick and easy. They're more interested in > > long, drawn-out, and complicated. > > > > On Sat, Feb 09, 2002 at 02:23:17PM +0530, Anjali Kulkarni wrote: > > > Hi, > > > > > > This is probably not the right place for this qs., but I am posting it > here since it's a quick & easy one. Does something like the FreeBSD zones > exist in Linux ? > > > > > > Thanks, > > > Anjali > > > > -- > > Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org > > my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > > > > http://www.blackhelicopters.org/~mwlucas/ > > > > -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 4:16:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id E978537B402; Sat, 9 Feb 2002 04:16:49 -0800 (PST) Received: (from olli@localhost) by lurza.secnetix.de (8.11.6/8.11.6) id g19CGk874726; Sat, 9 Feb 2002 13:16:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) From: Oliver Fromme Message-Id: <200202091216.g19CGk874726@lurza.secnetix.de> Subject: Re: USB "Memorybird" quirks To: jhb@FreeBSD.org (John Baldwin) Date: Sat, 9 Feb 2002 13:16:46 +0100 (CET) Cc: groudier@free.fr (=?ISO-8859-1?Q?G=E9rard_Roudier?=), hackers@FreeBSD.org (FreeBSD Hackers Mailing List), hardware@FreeBSD.org (FreeBSD Hardware Mailing List), olli@secnetix.de (Oliver Fromme), gene@nttmcl.com (Eugene M. Kim), tlambert2@mindspring.com (Terry Lambert), joe@tao.org.uk (Josef Karthauser) In-Reply-To: from "John Baldwin" at Feb 08, 2002 10:49:08 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > On 07-Feb-02 Gérard Roudier wrote: > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI block > > devices in order to accomodate softwares as boot software for example that > > may not be upgradable on systems still in use. Softwares that are > > maintained should no longer use 6 byte commands, but use the 10 byte > > commands replacement (for years...). > > Just so you know, I made the umass driver for UFI and ATA translate SCSI > 6 byte commands to 10 byte commands. There is a simple function call to do the > change if you wish to do this in for the SCSI transforms as well. I think that would be a very good idea. The boot software issue is negligible, because there aren't any USB devices you can boot from. Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 4:36: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id B263237B421; Sat, 9 Feb 2002 04:35:59 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 651E92F6; Sat, 9 Feb 2002 12:35:58 +0000 (GMT) Date: Sat, 9 Feb 2002 12:35:58 +0000 From: Josef Karthauser To: Oliver Fromme Cc: John Baldwin , =?iso-8859-1?Q?G=E9rard_Roudier?= , FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert Subject: Re: USB "Memorybird" quirks Message-ID: <20020209123558.A81896@genius.tao.org.uk> References: <200202091216.g19CGk874726@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200202091216.g19CGk874726@lurza.secnetix.de>; from oliver.fromme@secnetix.de on Sat, Feb 09, 2002 at 01:16:46PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote: > John Baldwin wrote: > > On 07-Feb-02 G=E9rard Roudier wrote: > > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI = block > > > devices in order to accomodate softwares as boot software for exampl= e that > > > may not be upgradable on systems still in use. Softwares that are > > > maintained should no longer use 6 byte commands, but use the 10 byte > > > commands replacement (for years...). > >=20 > > Just so you know, I made the umass driver for UFI and ATA translate SC= SI > > 6 byte commands to 10 byte commands. There is a simple function call = to do the > > change if you wish to do this in for the SCSI transforms as well. I'd love the patches if you've got them to hand. Joe --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxlF60ACgkQXVIcjOaxUBaBPQCgh4aTu64MnnqXQpK45BCDKRA9 WA4An02hKJBC2vEMQE7xyUex15kH6SO+ =mu+I -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 4:37:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id DE8F337B419 for ; Sat, 9 Feb 2002 04:37:45 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g19Cbcj31368; Sat, 9 Feb 2002 13:37:38 +0100 (CET) (envelope-from wkb) Date: Sat, 9 Feb 2002 13:37:38 +0100 From: Wilko Bulte To: Terry Lambert Cc: "Vladislav V. Anikiev" , Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address Message-ID: <20020209133738.A31278@freebie.xs4all.nl> References: <200202090052.DAA62563@neo.spbnit.ru> <3C649564.F51D18BE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C649564.F51D18BE@mindspring.com>; from tlambert2@mindspring.com on Fri, Feb 08, 2002 at 07:20:04PM -0800 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Feb 08, 2002 at 07:20:04PM -0800, Terry Lambert wrote: > "Vladislav V. Anikiev" wrote: > > > > Hello Brian, > > > > The MAC address - I meen The Media Access Control address (i.e., ethernet > > hardware address, not IP address). I want to use the default hardware (not > > current physical ) address in my license management software. > > > > Why did you write: "Depending on the NIC". The NIC means Network > > Information Center. Doesn't it ? > > Network Interface Card. > > Some NICs allow you to change the default MAC address by > reflashing the BIOS in them. There are tools to do this > in software. Or just reprogram it for runtime use only. DECnet comes to mind. No flashing needed there. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 5:37:32 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id D005C37B41C for ; Sat, 9 Feb 2002 05:37:30 -0800 (PST) Received: from pool0251.cvx21-bradley.dialup.earthlink.net ([209.179.192.251] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ZXgx-00012P-00; Sat, 09 Feb 2002 05:37:23 -0800 Message-ID: <3C65235E.F46A40B1@mindspring.com> Date: Sat, 09 Feb 2002 05:25:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: "Vladislav V. Anikiev" , Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address References: <200202090052.DAA62563@neo.spbnit.ru> <3C649564.F51D18BE@mindspring.com> <20020209133738.A31278@freebie.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > Some NICs allow you to change the default MAC address by > > reflashing the BIOS in them. There are tools to do this > > in software. > > Or just reprogram it for runtime use only. DECnet comes to mind. > No flashing needed there. Yes. The LANCE based DEQNA's from the MicroVAX II were really strange in supporting that. It wasn't until I realized that the MAC address was the DEC assigned address block prefix plus an internal prefix, plus the DECNet node number, that I realized why I could not talk to DECNet with my raw EtherLink I drivers, even though the packets were formatted correctly. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 5:54:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 17E5737B402 for ; Sat, 9 Feb 2002 05:54:24 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g19DsEH00386; Sat, 9 Feb 2002 14:54:14 +0100 (CET) (envelope-from wkb) Date: Sat, 9 Feb 2002 14:54:14 +0100 From: Wilko Bulte To: Terry Lambert Cc: "Vladislav V. Anikiev" , Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: MAC address Message-ID: <20020209145414.A372@freebie.xs4all.nl> References: <200202090052.DAA62563@neo.spbnit.ru> <3C649564.F51D18BE@mindspring.com> <20020209133738.A31278@freebie.xs4all.nl> <3C65235E.F46A40B1@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C65235E.F46A40B1@mindspring.com>; from tlambert2@mindspring.com on Sat, Feb 09, 2002 at 05:25:50AM -0800 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Feb 09, 2002 at 05:25:50AM -0800, Terry Lambert wrote: > Wilko Bulte wrote: > > > Some NICs allow you to change the default MAC address by > > > reflashing the BIOS in them. There are tools to do this > > > in software. > > > > Or just reprogram it for runtime use only. DECnet comes to mind. > > No flashing needed there. > > Yes. The LANCE based DEQNA's from the MicroVAX II were > really strange in supporting that. It wasn't until I > realized that the MAC address was the DEC assigned > address block prefix plus an internal prefix, plus the > DECNet node number, that I realized why I could not > talk to DECNet with my raw EtherLink I drivers, even > though the packets were formatted correctly. 8-). Cool huh? We once had that when we wanted to isolate a part of the network using a programmable bridge. The network folks programmed it for us, then a colleague put DECnet on it. And nuked another DECnet node on the network because the bridge happily forwarded the new MAC-address' packets. The fact that we picked an arbitrary DECnet address which proved a main node on the DEC internal Easynet left us pretty impopulair for a considerable time ;-) -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 6:10:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57]) by hub.freebsd.org (Postfix) with ESMTP id 03FD637B405 for ; Sat, 9 Feb 2002 06:10:54 -0800 (PST) Received: from user-37kaoto.dialup.mindspring.com ([207.69.99.184] helo=mr-p.protolan) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16ZYDL-0000qL-00; Sat, 09 Feb 2002 09:10:52 -0500 Date: Sat, 9 Feb 2002 09:15:21 -0500 From: "Marko" X-Mailer: The Bat! (v1.53d) Personal Reply-To: Anikin X-Priority: 3 (Normal) Message-ID: <5743342710.20020209091521@mindspring.com> To: "Rogier R. Mulhuijzen" Cc: freebsd-hackers@freebsd.org Subject: Re[6]: natd UDP errors with PPP demand dial In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2/8/2002 Rogier R. Mulhuijzen drwilco@drwilco.net wrote: RRM> 1) Maybe the IP change isn't getting through to natd like it should. RRM> 2) Have ppp kill -9 natd on link down and start natd on linkup. RRM> Doc Thank you for the suggestion, Doc. The IP change gets through to natd, but the packets causing the problem seem to be out of its jurisdiction by then, and headed for the Internet. It seems to me that stopping and starting natd would cause another set of problems. The outgoing packets that prompt ppp to set up a link are generated by machines on a private LAN. That means that if natd is not running at the beginning of ppp link setup, ppp will receive and will route to the Internet some packets with private source IP. Right? I think I solved the problem by using a couple of in and out ppp filters, which I mentioned in my previous message: # Allow incoming only to current address set filter in 0 permit 0/0 MYADDR # Block destination - previous IP. set filter in 1 deny 0/0 0/0 # Allow outgoing only from current address set filter out 0 permit MYADDR 0/0 # Block source - previous IP. set filter out 1 deny 0/0 0/0 I don't know if I did the filters the best way, or if this is the best way to handle the problem. However, it seems to be working. I don't get errors from natd since then. I might try just using the out filter because the outbound packets seem to initiate the whole error sequence. Thank you again for responding. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 7: 2:58 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by hub.freebsd.org (Postfix) with ESMTP id 9A3DA37B416 for ; Sat, 9 Feb 2002 07:02:55 -0800 (PST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g19F2ri64142 for ; Sun, 10 Feb 2002 04:02:53 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200202091502.g19F2ri64142@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: hackers@freebsd.org Date: Sat, 9 Feb 2002 10:02:51 -0500 MIME-Version: 1.0 Subject: is this character encoding or corrupted text? Reply-To: dan@langille.org X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm looking at this commit: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=292893+0+archive/2001/cvs- all/20010429.cvs-all In the log, the name "Matthias Kvppe" appears. Is that the correct name? If you look at the underlying HTML, or fetch the HTML and view it using vi, you will see "Matthias K^[,Av^[(Bppe". I'm wondering if there are special characters in there which were not well handled by the cvs-all process. My next question is how to properly handle these characters. Thanks. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 7:51:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id B185C37B416 for ; Sat, 9 Feb 2002 07:50:52 -0800 (PST) Received: (qmail 16271 invoked from network); 9 Feb 2002 15:50:50 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.153.195]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 15:50:50 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020209123558.A81896@genius.tao.org.uk> Date: Sat, 09 Feb 2002 10:50:48 -0500 (EST) From: John Baldwin To: Josef Karthauser Subject: Re: USB "Memorybird" quirks Cc: Terry Lambert , "Eugene M. Kim" , Oliver Fromme , FreeBSD Hardware Mailing List , FreeBSD Hackers Mailing List , =?iso-8859-1?Q?G=E9rard_Roudier?= , Oliver Fromme Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 09-Feb-02 Josef Karthauser wrote: > On Sat, Feb 09, 2002 at 01:16:46PM +0100, Oliver Fromme wrote: > >> John Baldwin wrote: >> > On 07-Feb-02 Gérard Roudier wrote: >> > > A couple of READ/WRITE 6 byte commands are still mandatory for SCSI >> > > block >> > > devices in order to accomodate softwares as boot software for example >> > > that >> > > may not be upgradable on systems still in use. Softwares that are >> > > maintained should no longer use 6 byte commands, but use the 10 byte >> > > commands replacement (for years...). >> > >> > Just so you know, I made the umass driver for UFI and ATA translate SCSI >> > 6 byte commands to 10 byte commands. There is a simple function call to >> > do the >> > change if you wish to do this in for the SCSI transforms as well. > > I'd love the patches if you've got them to hand. Unless you've spammed the commits I made to umass.c they've been in the tree for a month or so. :-P Look at the UFI transform for example: umass_ufi_transform(struct umass_softc *sc, unsigned char *cmd, int cmdlen, unsigned char **rcmd, int *rcmdlen) { ... if (umass_scsi_6_to_10(cmd, cmdlen, rcmd, rcmdlen)) return (1); ... } Same code is in the atapi_transform function as well. Just add those two lines before the big switch() on the command to the scsi_transform function. > Joe -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 7:51:38 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 123AD37B447 for ; Sat, 9 Feb 2002 07:50:56 -0800 (PST) Received: (qmail 5138 invoked from network); 9 Feb 2002 15:50:54 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([65.91.153.195]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Feb 2002 15:50:54 -0000 Message-ID: X-Mailer: XFMail 1.4.0 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: Sat, 09 Feb 2002 10:50:52 -0500 (EST) From: John Baldwin To: Julian Elischer Subject: Re: requesting guidance for updating the RocketPort driver Cc: freebsd-hackers@freebsd.org, John Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 09-Feb-02 Julian Elischer wrote: > he infrastructure needed for a new driver can be taken from > the sample driver in /usr/share/examples/drivers/make_device_driver.sh > IN -CURRENT. (use cvdweb on the website to get it) > > that will at least get rid of the 'shims' stuff. There is already a newer driver in current. I've backported it but it didn't help me get my RocketPort working. :-P (I think my rocketport has other issues though as other people have had success with the cards on the old driver.) The backport is fairly easy. You need to bascially take the src/sys/dev/rp/ directory from current, merge the appropriate lines from sys/conf/files (and remove references to i386/isa/rp.c in files.i386 and files.pc98), change all 'struct thread *td's to 'struct proc *p', and change 'suser_td(td)' to 'suser(p)'. Finally, you need to sys/i386/isa/edit isa_compat.h and remove references to rpdriver. If someone with a workign RP card can test that that works and commit the changes, that would be nice. :) > On Sat, 9 Feb 2002, John wrote: > >> *** Please reply directly, since I am not currently subscribed to this list >> *** >> >> It seems to be a given that Comtrol is not in a position to support >> and develop the driver for the RocketPort cards. I happen to be >> the owner of a couple of these, and I'm having problems with >> newer versions of FreeBSD. >> >> For one, I get >> Feb 8 23:35:27 dexter /kernel: rp0: driver is using old-style compatibility >> shims >> Feb 8 23:35:37 dexter /kernel: WARNING: driver rp should register devices >> with ma >> ke_dev() (dev_t = "#rp/0x10007") >> >> That'd be fine and well, if the silly thing WORKED, which it doesn't, >> quite. tcsetattr returns "Invalid argument" when perfectly reasonable >> things are going on, preventing me from running PPP on these, or >> indeed making other reasonable changes to the terminal line driver >> characteristics. >> >> I just grabbed the latest version from -stable, and it diffs against >> what I'm using with no changes. The version I have with FreeBSD >> 2.1 doesn't have the problem with setting line characteristics, >> but it differs in many details from the driver in -stable. I was >> actually working with a developer at Comtrol in 1997 (they are/were >> local), and I have several versions of the driver from February >> 24, March 11, April 10, and May 22 which may be in a more advanced >> state than the driver in the distribution. At any rate, I've run >> PPP on that version of the driver for a almost 5 years, and it has >> done that quite well. >> >> I'd be very happy to work on this and get a superior driver into >> the distribution, but I could use just a bit of hand-holding, >> particularly with regard to that "old style driver shims" thing. >> >> I suspect, jumping from a 1997 FreeBSD (2.1) to a 2002 FreeBSD, there >> may be a few bumps in the road. >> >> Can someone point me in the right direction, or provide a little >> hand-holding? >> >> Thanks! >> >> *** Please reply directly, since I am not currently subscribed to this list >> *** >> -- >> >> John Lind >> john@starfire.MN.ORG >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 9:40:21 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 0705B37B41A for ; Sat, 9 Feb 2002 09:40:19 -0800 (PST) Received: (from geoffb@localhost) by chuggalug.clues.com (8.11.6/8.9.3) id g19HeHm23181 for hackers@freebsd.org; Sat, 9 Feb 2002 17:40:17 GMT (envelope-from geoffb) Date: Sat, 9 Feb 2002 17:40:17 +0000 From: Geoff Buckingham To: hackers@freebsd.org Subject: loader and extended ext2fs partitions? Message-ID: <20020209174017.A23150@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Should the loader be able to understand ext2fs partitions within an extended (type 4) partition? I have been trying this with a disk containing a suse 7.2 install (automatic) its fstab looks like this: /dev/sda7 / ext2 defaults 1 1 /dev/sda5 /boot ext2 defaults 1 2 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/sda6 swap swap pri=42 0 0 setting currdev=disk1s[7|5] in the loader just produces errors (boot loader from floppy, hence disk1 not disk0). Is suse unique in installing everything this way by default? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 10:40:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 31B9837B41D for ; Sat, 9 Feb 2002 10:40:16 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020209184010.FCZQ1147.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sat, 9 Feb 2002 18:40:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA07798; Sat, 9 Feb 2002 10:39:31 -0800 (PST) Date: Sat, 9 Feb 2002 10:39:30 -0800 (PST) From: Julian Elischer To: Anjali Kulkarni Cc: Michael Lucas , freebsd-hackers@freebsd.org Subject: Re: Zones In-Reply-To: <002301c1b157$d0c38470$0a00a8c0@indranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG well he may speak for only himself.. as for me I have no idea what a 'zone' is in Linux.. timezone? memory zone allocator in the kernel? routing zones? On Sat, 9 Feb 2002, Anjali Kulkarni wrote: > Thanks for your reminder. I guess I didnt realize they would consider > simple and easy beneath their dignity. > > Truly sorry for the trouble this one email caused you and others, > Regards, > Anjali > > ----- Original Message ----- > From: "Michael Lucas" > To: "Anjali Kulkarni" > Cc: > Sent: Saturday, February 09, 2002 3:11 PM > Subject: Re: Zones > > > > Hello, > > > > Your best bet for general questions is the > > freebsd-questions@freebsd.org mailig list. > > > > It might be quick and easy, but historically, the people in -hackers > > are not interested in quick and easy. They're more interested in > > long, drawn-out, and complicated. > > > > On Sat, Feb 09, 2002 at 02:23:17PM +0530, Anjali Kulkarni wrote: > > > Hi, > > > > > > This is probably not the right place for this qs., but I am posting it > here since it's a quick & easy one. Does something like the FreeBSD zones > exist in Linux ? > > > > > > Thanks, > > > Anjali > > > > -- > > Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org > > my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons > > > > http://www.blackhelicopters.org/~mwlucas/ > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:13:41 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C043837B400; Sat, 9 Feb 2002 11:13:36 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA21191; Sat, 9 Feb 2002 14:13:24 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g19JD5Y42767; Sat, 9 Feb 2002 14:13:05 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15461.29889.851409.807358@grasshopper.cs.duke.edu> Date: Sat, 9 Feb 2002 14:13:05 -0500 (EST) To: John Cc: Julian Elischer , freebsd-hackers@freebsd.org, John Baldwin Subject: Re: requesting guidance for updating the RocketPort driver In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: > > On 09-Feb-02 Julian Elischer wrote: > > he infrastructure needed for a new driver can be taken from > > the sample driver in /usr/share/examples/drivers/make_device_driver.sh > > IN -CURRENT. (use cvdweb on the website to get it) > > > > that will at least get rid of the 'shims' stuff. > > There is already a newer driver in current. I've backported it but it didn't > help me get my RocketPort working. :-P (I think my rocketport has other issues > though as other people have had success with the cards on the old driver.) The > backport is fairly easy. You need to bascially take the src/sys/dev/rp/ <..> I've done essentially that and have been using it to drive serial consoles off my alpha for a few months now on -stable with no problems. I needed the newer driver from -current because the old driver isn't bus-space-ified and doens't work on alpha rp0: port 0x10180-0x101bf irq 9 at device 10.0 on pci0 RocketPort0 (Version 3.02) 8 ports. Try http://people.freebsd.org/~gallatin/rp.tgz. I never bothered to touch all the files files so that means you must build it as a module: cd /usr/src fetch http://people.freebsd.org/~gallatin/rp.tgz tar zxf rp.tgz cd sys/modules/rp make depend && make && make install kldload rp (this assumes you're not already running a kernel with old driver built in) All the standard disclaimers apply. Don't blame me if it blows up your computer, gives you an ulcer or gives your cat hairballs... Anyway, let me know if it works any better for you than the old driver in -stable. I've been reluctant to commit it since I don't want to be responsible for maintaining it and just running serial consoles at 9600 baud doesn't push things hard enough to find bugs. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:22:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2F4CE37B405 for ; Sat, 9 Feb 2002 11:22:26 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 65BE85341; Sat, 9 Feb 2002 20:22:24 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem References: From: Dag-Erling Smorgrav Date: 09 Feb 2002 20:22:23 +0100 In-Reply-To: Message-ID: Lines: 13 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang writes: > The following small program demonstrates that a parent process can write > into the data space of its child by ptrace(). If the parent waits for the > child to exit, there is no problem. However, if the parent does not do so, > the child will get a SIGTRAP signal and core dumps. Can anyone give me a > clue how this is the case? Thanks! The parent must either detach from the child, or wait for it to terminate. See ptrace(2). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:30:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 1B0BF37B402 for ; Sat, 9 Feb 2002 11:30:37 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16ZdCl-000765-00; Sat, 9 Feb 2002 20:30:35 +0100 Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.11.6/8.11.6) id g19Ij0C10586 for freebsd-hackers@freebsd.org; Sat, 9 Feb 2002 19:45:00 +0100 (CET) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: is this character encoding or corrupted text? Date: Sat, 9 Feb 2002 18:45:00 +0000 (UTC) Message-ID: References: <200202091502.g19F2ri64142@lists.unixathome.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Langille wrote: > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=292893+0+archive/2001/cvs- > all/20010429.cvs-all > > In the log, the name "Matthias Kvppe" appears. Is that the correct name? That is probably "Matthias Köppe" (ISO 8859-15) with the top bit cut off. Or "Matthias Koeppe" in transcription. > My next question is how to properly handle these characters. First you need to figure what the original character was. Since you can't tag CVS logs and such with character sets, you'll then have to come up with an ASCII transcription according to the rules of the originating language. (Alternatively people could agree to use UTF-8, but FreeBSD support for that is painfully weak. And you'd still have to convert from whatever original character set to UTF-8.) -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:51:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D0CB37B41E; Sat, 9 Feb 2002 11:51:42 -0800 (PST) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA69074; Sat, 9 Feb 2002 13:51:32 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 9 Feb 2002 13:51:32 -0600 (CST) From: Chris Dillon To: Oliver Fromme Cc: John Baldwin , =?ISO-8859-1?Q?G=E9rard_Roudier?= , FreeBSD Hackers Mailing List , FreeBSD Hardware Mailing List , Oliver Fromme , "Eugene M. Kim" , Terry Lambert , Josef Karthauser Subject: Re: USB "Memorybird" quirks In-Reply-To: <200202091216.g19CGk874726@lurza.secnetix.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 9 Feb 2002, Oliver Fromme wrote: > I think that would be a very good idea. The boot software issue > is negligible, because there aren't any USB devices you can boot > from. You mean can't boot from USB devices in just FreeBSD, or anywhere? I've not actually tried it yet, but many motherboard vendors have added the ability to boot from USB ZIP drives and probably other USB mass storage devices to their BIOSes, so it at least should be possible. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet - Available for IA32 (Intel x86) and Alpha architectures - IA64, PowerPC, UltraSPARC, and ARM architectures under development - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:58:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from f434.n5020.z2.fidonet.org (host5.mtelecom.ru [212.44.147.5]) by hub.freebsd.org (Postfix) with ESMTP id 6A0DE37B416 for ; Sat, 9 Feb 2002 11:58:33 -0800 (PST) Received: (from seva@localhost) by f434.n5020.z2.fidonet.org (8.11.6/8.11.3) id g19JvgV04553; Sat, 9 Feb 2002 22:57:42 +0300 (MSK) (envelope-from seva) From: vs3volod@yahoo.com To: hackers@FreeBSD.ORG Subject: ping: sendto: No buffer space available Date: 09 Feb 2002 22:57:40 +0300 In-Reply-To: "Vladimir B. " Grebenschikov's message of "08 Feb 2002 19:22:37 +0300" Message-ID: <86aduisa17.fsf@f434.n5020.z2.fidonet.org> Lines: 47 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Some times connections to my host freeze. What buffer ping talks about? ~:# ping p109 ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes --- p109.f434.n5020.z2.fidonet.org ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss ~:# pstat -T 236/1064 files 0M/255M swap space ~:# netstat -m 97/128/4096 mbufs in use (current/peak/max): 49 mbufs allocated to data 48 mbufs allocated to packet headers 17/28/1024 mbuf clusters in use (current/peak/max) 88 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines ~:# ifconfig ep0: flags=8c43 mtu 1500 inet 192.168.44.41 netmask 0xffffff00 broadcast 192.168.44.255 inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 inet 192.168.44.42 netmask 0xffffffff broadcast 192.168.44.42 ether 00:a0:24:46:b8:23 media: Ethernet 10baseT/UTP faith0: flags=8000 mtu 1500 stf0: flags=0<> mtu 1280 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8051 mtu 1500 inet 192.168.10.202 --> 192.168.3.3 netmask 0xffffff00 ppp1: flags=8010 mtu 1500 ~:# uname -a FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 root@f434.n5020.z2.fidonet.org:/usr/src/sys/compile/PP i386 ~:# Seva. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 11:59:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id CB59537B43F for ; Sat, 9 Feb 2002 11:59:03 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g19JwuQ21614; Sat, 9 Feb 2002 14:58:56 -0500 (EST) Date: Sat, 9 Feb 2002 14:58:52 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@opal To: Dag-Erling Smorgrav Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have tested four cases: - PT_CONTINUE + waitpid() works fine, the trace program prints out values. - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP - PT_DETACH + waitpid() does not work and core-dump - PT_DETACH alone does not work and core-dump. Who is sending the SIGRAP (5) signal? The same program works fine on SunOS. Maybe there is a bug in the kernel. I have looked into sys_process.c and still have no idea. -Zhihui On 9 Feb 2002, Dag-Erling Smorgrav wrote: > Zhihui Zhang writes: > > The following small program demonstrates that a parent process can write > > into the data space of its child by ptrace(). If the parent waits for the > > child to exit, there is no problem. However, if the parent does not do so, > > the child will get a SIGTRAP signal and core dumps. Can anyone give me a > > clue how this is the case? Thanks! > > The parent must either detach from the child, or wait for it to > terminate. See ptrace(2). > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 12:22:26 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mmk.ru (ns1.mmk.ru [195.54.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 7E23437B400; Sat, 9 Feb 2002 12:22:15 -0800 (PST) Received: from antivirus.mmk.ru (sinful [161.8.100.3]) by ns.mmk.ru (8.11.6/8.11.6) with ESMTP id g19KTVh16372; Sun, 10 Feb 2002 01:29:31 +0500 (YEKT) Received: from dimasic (localhost [127.0.0.1]) by antivirus.mmk.ru (8.11.6/8.11.6) with SMTP id g19KLUD14817; Sun, 10 Feb 2002 01:21:30 +0500 (ESK) Message-ID: <00e201c1b1a7$58b27630$02010101@dimasic> From: "Dmitry A. Bondareff" To: "Dmitry A. Bondareff" , Cc: References: <004501c1af93$79b0fca0$02010101@wall> <20020207110319.A64437@dragon.nuxi.com> <012e01c1b061$514cd2b0$02010101@wall> Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE Date: Sun, 10 Feb 2002 00:13:00 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I successfuly upgrade from 4.0 to 4.1 and then up it to 4.5. Thanks. :)) ----- Original Message ----- From: "Dmitry A. Bondareff" To: Cc: Sent: Friday, February 08, 2002 10:27 AM Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > If you lie me, I'll be back !! :)) > > ----- Original Message ----- > From: "David O'Brien" > To: "Dmitry A. Bondareff" > Cc: > Sent: Friday, February 08, 2002 12:03 AM > Subject: Re: Error compiling src for 4.5-RELEASE on 4.0-RELEASE > > > > On Thu, Feb 07, 2002 at 09:54:07AM +0500, Dmitry A. Bondareff wrote: > > > Yesterday I've tried to update it teel 4.5-RELEASE. > > ... > > > P.S. Day before it I was upgrade from 4.4-RELEASE to 4.5-RELEASE easy. > > > > That means if you need to upgrade the box right now, you can upgrade your > > 4.0 box to 4.4 and then to 4.5. (you might also need to upgrade to 4.1 > > or 4.2 first). Or wait for ru. :) > > > > -- > > -- David (obrien@FreeBSD.org) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 12:37:33 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from venom.ai.net (venom.ai.net [205.134.190.250]) by hub.freebsd.org (Postfix) with ESMTP id D783E37B404 for ; Sat, 9 Feb 2002 12:37:24 -0800 (PST) Received: from blood (pool-138-88-74-86.res.east.verizon.net [138.88.74.86]) by venom.ai.net (8.11.1/8.9.3) with SMTP id g19K8ls19480; Sat, 9 Feb 2002 15:08:47 -0500 (EST) (envelope-from deepak@ai.net) Reply-To: From: "Deepak Jain" To: , Subject: RE: ping: sendto: No buffer space available Date: Sat, 9 Feb 2002 15:37:18 -0500 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <86aduisa17.fsf@f434.n5020.z2.fidonet.org> Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Try increasing your maxsockbuf: kern.ipc.maxsockbuf: 262144 is the default setting, try: sysctl -w kern.ipc.maxsockbuf=384000 [or higher, depending on your RAM and your network usage] There are a bunch of other network buffers you might want to tune as I am sure others will mention. Deepak Jain AiNET -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of vs3volod@yahoo.com Sent: Saturday, February 09, 2002 2:58 PM To: hackers@FreeBSD.ORG Subject: ping: sendto: No buffer space available Some times connections to my host freeze. What buffer ping talks about? ~:# ping p109 ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes --- p109.f434.n5020.z2.fidonet.org ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss ~:# pstat -T 236/1064 files 0M/255M swap space ~:# netstat -m 97/128/4096 mbufs in use (current/peak/max): 49 mbufs allocated to data 48 mbufs allocated to packet headers 17/28/1024 mbuf clusters in use (current/peak/max) 88 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines ~:# ifconfig ep0: flags=8c43 mtu 1500 inet 192.168.44.41 netmask 0xffffff00 broadcast 192.168.44.255 inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 inet 192.168.44.42 netmask 0xffffffff broadcast 192.168.44.42 ether 00:a0:24:46:b8:23 media: Ethernet 10baseT/UTP faith0: flags=8000 mtu 1500 stf0: flags=0<> mtu 1280 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 ppp0: flags=8051 mtu 1500 inet 192.168.10.202 --> 192.168.3.3 netmask 0xffffff00 ppp1: flags=8010 mtu 1500 ~:# uname -a FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 root@f434.n5020.z2.fidonet.org:/usr/src/sys/compile/PP i386 ~:# Seva. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 12:56:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from 207-194-143-195.dsl.axion.net (207-194-143-195.dsl.axion.net [207.194.143.195]) by hub.freebsd.org (Postfix) with ESMTP id 38F4837B41C for ; Sat, 9 Feb 2002 12:56:22 -0800 (PST) Received: from roller.pangolin-systems.com (h24-77-105-71.vc.shawcable.net [24.77.105.71] (may be forged)) by 207-194-143-195.dsl.axion.net (8.11.6/8.11.6) with ESMTP id g19Ku8j00368; Sat, 9 Feb 2002 12:56:10 -0800 (PST) (envelope-from jhanna@shaw.ca) Message-Id: <200202092056.g19Ku8j00368@207-194-143-195.dsl.axion.net> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86aduisa17.fsf@f434.n5020.z2.fidonet.org> Date: Sat, 09 Feb 2002 12:56:06 -0800 (PST) Reply-To: Jonathan Hanna From: Jonathan Hanna To: vs3volod@yahoo.com Subject: RE: ping: sendto: No buffer space available Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This looks like the bug in the "ep" driver. When the interrupt routine gets both TX and RX interrupts it acknowledges both but only services the read. Karl Dietz, is working on an overhaul but my quick fix is to take out the "continue" after the "epread()" in ep_intr(). The buffer talked about is actually the ep queue being full. --- if_ep.c Fri Feb 1 19:51:43 2002 +++ if_ep.c.fix Sat Feb 9 12:49:31 2002 @@ -571,7 +571,6 @@ if (status & (S_RX_COMPLETE | S_RX_EARLY)) { epread(sc); - continue; } if (status & S_TX_AVAIL) { /* we need ACK */ Karl Dietz On 09-Feb-02 vs3volod@yahoo.com wrote: > > Some times connections to my host freeze. > What buffer ping talks about? > > ~:# ping p109 > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ping: sendto: No buffer space available > ping: sendto: No buffer space available > PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes > > --- p109.f434.n5020.z2.fidonet.org ping statistics --- > 4 packets transmitted, 0 packets received, 100% packet loss > ~:# pstat -T > 236/1064 files > 0M/255M swap space > ~:# netstat -m > 97/128/4096 mbufs in use (current/peak/max): > 49 mbufs allocated to data > 48 mbufs allocated to packet headers > 17/28/1024 mbuf clusters in use (current/peak/max) > 88 Kbytes allocated to network (2% of mb_map in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > ~:# ifconfig > ep0: flags=8c43 mtu 1500 > inet 192.168.44.41 netmask 0xffffff00 broadcast 192.168.44.255 > inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 > inet 192.168.44.42 netmask 0xffffffff broadcast 192.168.44.42 > ether 00:a0:24:46:b8:23 > media: Ethernet 10baseT/UTP > faith0: flags=8000 mtu 1500 > stf0: flags=0<> mtu 1280 > lo0: flags=8049 mtu 16384 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8051 mtu 1500 > inet 192.168.10.202 --> 192.168.3.3 netmask 0xffffff00 > ppp1: flags=8010 mtu 1500 > ~:# uname -a > FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 root@f434.n5020.z2.fidon et.org:/usr/src/sys/compile/PP i386 > ~:# > > > Seva. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Jonathan Hanna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 13:37:27 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 413C737B427 for ; Sat, 9 Feb 2002 13:37:15 -0800 (PST) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id g19BXFR13998 for ; Sat, 9 Feb 2002 11:33:15 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200202091133.g19BXFR13998@jhs.muc.de> Date: Sat, 09 Feb 2002 12:33:14 +0100 From: Julian Stacey Subject: Re: set uf UNIX utilites written on asm To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------- Blind-Carbon-Copy To: freebsd-small@FreeBSD.ORG cc: "Vladimir B. Grebenschikov" Reply-to: "Vladimir B. Grebenschikov" , freebsd-small@FreeBSD.ORG Subject: Re: set uf UNIX utilites written on asm From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Fri, 08 Feb 2002 17:22:37 +0100." <1013185357.5139.1.camel@vbook.express.ru> Date: Sat, 09 Feb 2002 12:33:14 +0100 Sender: jhs@park.jhs.private Vladimir, Your posting seems better not on hackers@ list, but on small@ so I reposted it with this header: To: freebsd-small@FreeBSD.ORG cc: "Vladimir B. Grebenschikov" Reply-to: "Vladimir B. Grebenschikov" , freebsd-small@FreeBSD.ORG bcc: freebsd-hackers@freebsd.org All picobsd follow up to freebsd-small@ please. PS I wonder if we have or should have a mail alias picobsd@freebsd --> small@freebsd ? or similar (it might make it easier to relate things) ? Reference: > From: "Vladimir B. " Grebenschikov > Date: Fri, 8 Feb 2002 17:22:37 +0100 > Message-id: <1013185357.5139.1.camel@vbook.express.ru> "Vladimir B. " Grebenschikov wrote: > Hi > > May it will be interesting for createing small setup like picobsd: > > http://linuxassembly.org/asmutils.html > > -- > SW Soft, Moscow > Vladimir B. Grebenschikov, vova@sw.ru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Julian J.Stacey Munich Unix (FreeBSD, Linux etc) Independent Consultant Reduce costs to secure jobs: Use free software: http://bim.bsn.com/~jhs/free/ Ihr Rauchen = mein allergischer Kopfschmerz ! Schnupftabak probieren ! ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 13:56:48 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tholian.rsasecurity.com (mail.rsasecurity.com [204.167.112.129]) by hub.freebsd.org (Postfix) with SMTP id 5B41137B417 for ; Sat, 9 Feb 2002 13:56:43 -0800 (PST) Received: from sdtihq24.securid.com by tholian.rsasecurity.com via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 9 Feb 2002 21:56:06 UT Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4]) by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id QAA12945 for ; Sat, 9 Feb 2002 16:56:38 -0500 (EST) Received: from spirit.dynas.se (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.10.2+Sun/8.9.1) with SMTP id g19LuaL28553 for ; Sat, 9 Feb 2002 16:56:36 -0500 (EST) Received: (qmail 18691 invoked from network); 9 Feb 2002 21:56:35 -0000 Received: from explorer.rsa.com (HELO mikko.rsa.com) (10.81.217.59) by spirit.dynas.se with SMTP; 9 Feb 2002 21:56:35 -0000 Received: (from mikko@localhost) by mikko.rsa.com (8.11.6/8.11.6) id g19LuXg06033; Sat, 9 Feb 2002 13:56:33 -0800 (PST) (envelope-from mikko) Date: Sat, 9 Feb 2002 13:56:33 -0800 (PST) From: Mikko Tyolajarvi Message-Id: <200202092156.g19LuXg06033@mikko.rsa.com> To: henrich@sigbus.com Cc: hackers@freebsd.org Subject: Re: anyone familier with bktr driver? Newsgroups: local.freebsd.hackers References: <20020208200631.A20501@sigbus.com> X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In local.freebsd.hackers you write: >I'd like to add support to the mplayer/mencoder software (which is turning out >to be a fantastic tool, can playback and encode to all sorts of formats, from >VCD's, to DVD's, to AVI files, to DIVX, etc..). There is support for the >video4linux driver, as wll as an example "dummy" driver as input mechanisms. >The problem is im having a hard time finding any information about the basic >bktr driver, how to set it up, how to read a frame, etc.. Anyone out there >who can shed some light, would be appreciated! Have you looked at the source for fxtv (ports/graphics/fxtv)? $.02, /Mikko -- Mikko Työläjärvi_______________________________________mikko@rsasecurity.com RSA Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 14:30:17 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient217-162-168-98.hispeed.ch [217.162.168.98]) by hub.freebsd.org (Postfix) with ESMTP id DD3FD37B404 for ; Sat, 9 Feb 2002 14:30:09 -0800 (PST) Received: from beerswilling.netscum.dyndns.dk (dcf77-zeit.netscum.dyndns.dk [172.27.72.27] (may be forged)) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6) with ESMTP id g19MU4c01719 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified FAIL) for ; Sat, 9 Feb 2002 23:30:07 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/8.11.6) id g19MU4C01718; Sat, 9 Feb 2002 23:30:04 +0100 (CET) (envelope-from bounce@dcf77-zeit.netscum.dyndns.dk) Date: Sat, 9 Feb 2002 23:30:04 +0100 (CET) Message-Id: <200202092230.g19MU4C01718@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery To: freebsd-hackers@freebsd.org Subject: SC_DISABLE_SUSPEND ? Organization: Men not wearing any pants that dont shave X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: Mountain Informatik AG, Zuerich X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Argh, did it again, as I seem to do once a day... Is the proper place for me to request the possibility to disable the ctrl-alt-space (suspend) key combination here, by agitating for Yet Another Kernel Option (like the subject), or should I simply hack it out of the keymap? Basically, I wonder if I'm the only one fumble-fingered enough to have run across it and would prefer not to on a running system that is trying to keep accurate time... thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 14:38:28 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 1357C37B405 for ; Sat, 9 Feb 2002 14:38:24 -0800 (PST) Received: (qmail 53364 invoked by uid 100); 9 Feb 2002 22:38:22 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15461.42206.43835.878972@guru.mired.org> Date: Sat, 9 Feb 2002 16:38:22 -0600 To: Michael Lucas Cc: Anjali Kulkarni , freebsd-hackers@freebsd.org Subject: Re: Zones Reply-To: chat@freebsd.org In-Reply-To: <20020209061503.A66997@blackhelicopters.org> References: <001701c1b147$4b1fbc90$0a00a8c0@indranet> <20020209044141.A66561@blackhelicopters.org> <002301c1b157$d0c38470$0a00a8c0@indranet> <20020209061503.A66997@blackhelicopters.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-STABLE-i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Replies have been pointed to -chat.] Michael Lucas types: > People who are interested in answering easy questions read -questions. Um - people who are interested in helping others by answering questions read -question. Not all the questions on -questions are easy. Not all of them have answers. > People who are interested in discussing technical issues read > -hackers. While there is a certain amount of overlap, you're more > likely to get a better answer asking people who are interested in > answering questions. That's certainly right. If you ask a question properly, the worst case on -questions is that you'll be pointed to another list - -scsi and -multimedia are good examples, or -hackers for some - where people who are more likely to know the answer hang out. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 14:58: 7 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8766837B405 for ; Sat, 9 Feb 2002 14:58:03 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 57FFD5341; Sat, 9 Feb 2002 23:57:59 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem References: From: Dag-Erling Smorgrav Date: 09 Feb 2002 23:57:59 +0100 In-Reply-To: Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang writes: > - PT_CONTINUE + waitpid() works fine, the trace program prints out values. This is expected behaviour. > - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP > - PT_DETACH + waitpid() does not work and core-dump > - PT_DETACH alone does not work and core-dump. These three cases are unexpected. I'll have to dig some more into this, but I'm afraid I won't have time until some time next week. > Who is sending the SIGRAP (5) signal? execve(2) in kern_exec.c posts SIGTRAP if the process has debugging turned on (which it does as a result of PT_TRACE_ME). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 15: 8:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 8EE7137B416 for ; Sat, 9 Feb 2002 15:08:09 -0800 (PST) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id g19N85Q02248; Sat, 9 Feb 2002 18:08:05 -0500 (EST) Date: Sat, 9 Feb 2002 18:08:04 -0500 (EST) From: Zhihui Zhang X-Sender: zzhang@opal To: Dag-Erling Smorgrav Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 9 Feb 2002, Dag-Erling Smorgrav wrote: > Zhihui Zhang writes: > > - PT_CONTINUE + waitpid() works fine, the trace program prints out values. > > This is expected behaviour. > > > - PT_CONTINUE alone does not work but no core-dump caused by SIGTRAP > > - PT_DETACH + waitpid() does not work and core-dump > > - PT_DETACH alone does not work and core-dump. > > These three cases are unexpected. I'll have to dig some more into > this, but I'm afraid I won't have time until some time next week. > > > Who is sending the SIGRAP (5) signal? > > execve(2) in kern_exec.c posts SIGTRAP if the process has debugging > turned on (which it does as a result of PT_TRACE_ME). This is one time thing. It will be catched by the first wait() call in the parent process. Thanks for your reply. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 15:13:11 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5F85637B421 for ; Sat, 9 Feb 2002 15:13:06 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id F0EC45343; Sun, 10 Feb 2002 00:13:04 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem References: From: Dag-Erling Smorgrav Date: 10 Feb 2002 00:13:04 +0100 In-Reply-To: Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang writes: > On 9 Feb 2002, Dag-Erling Smorgrav wrote: > > execve(2) in kern_exec.c posts SIGTRAP if the process has debugging > > turned on (which it does as a result of PT_TRACE_ME). > This is one time thing. It will be catched by the first wait() > call in the parent process. Yes. Subsequent SIGTRAPs normally indicate that syscall tracing is enabled (see /sys/i386/i386/trap.c) but I don't think that's the case here. I'll try to figure out what's happening when I find time. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 18:33:46 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 89E4137B417 for ; Sat, 9 Feb 2002 18:33:43 -0800 (PST) Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id g1A2Xh324266 for ; Sat, 9 Feb 2002 18:33:43 -0800 (PST) Received: from orbit-fe.eng (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.12.2/8.12.2/NTAP-1.4) with ESMTP id g1A2Xgw0017157 for ; Sat, 9 Feb 2002 18:33:43 -0800 (PST) Received: from localhost (kmacy@localhost) by orbit-fe.eng (8.10.2+Sun/8.10.2) with ESMTP id g1A2Xgb18034 for ; Sat, 9 Feb 2002 18:33:42 -0800 (PST) Date: Sat, 9 Feb 2002 18:33:42 -0800 (PST) From: Kip Macy To: freebsd-hackers@freebsd.org Subject: Re: Ptrace and SIGTRAP problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Yes. Subsequent SIGTRAPs normally indicate that syscall tracing is > enabled (see /sys/i386/i386/trap.c) but I don't think that's the case > here. I'll try to figure out what's happening when I find time. > > DES Is it possible that this is related to gnu/33262, wherein sendsig() doesn't clear the trace flag and syscall() sometimes generates a SIGTRAP incorrectly? -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 18:51:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from sigbus.com (we-24-126-148-218.we.mediaone.net [24.126.148.218]) by hub.freebsd.org (Postfix) with ESMTP id 6BF9537B405 for ; Sat, 9 Feb 2002 18:51:09 -0800 (PST) Received: (from henrich@localhost) by sigbus.com (8.11.1/8.11.1) id g1A2p8513091 for freebsd-hackers@freebsd.org; Sat, 9 Feb 2002 18:51:08 -0800 (PST) (envelope-from henrich) Date: Sat, 9 Feb 2002 18:50:58 -0800 From: Charles Henrich To: freebsd-multimedia@freebsd.org Subject: gui free vic/vat (audio/video capture multicast mbone) Message-ID: <20020209185058.B12492@sigbus.com> Mail-Followup-To: freebsd-multimedia@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F X-GPG-Fingerprint: EA4C AB9B 0C38 17C0 AB3F 11DE 41F6 5883 41E7 4F49 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anyone know of a vic or vat that has been made to be gui free for remote execution without X? Or any multicast mbone capable tools? -Crh Charles Henrich henrich@msu.edu http://www.sigbus.com:81/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Feb 9 21:55:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 8B97837B41E for ; Sat, 9 Feb 2002 21:55:32 -0800 (PST) Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id g1A5tV327481 for ; Sat, 9 Feb 2002 21:55:32 -0800 (PST) Received: from orbit-fe.eng (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.12.2/8.12.2/NTAP-1.4) with ESMTP id g1A5tVE6027648 for ; Sat, 9 Feb 2002 21:55:31 -0800 (PST) Received: from localhost (kmacy@localhost) by orbit-fe.eng (8.10.2+Sun/8.10.2) with ESMTP id g1A5tVo26744 for ; Sat, 9 Feb 2002 21:55:31 -0800 (PST) Date: Sat, 9 Feb 2002 21:55:30 -0800 (PST) From: Kip Macy To: freebsd-hackers@freebsd.org Subject: to users of threads (GDB support) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A working version of gdb 5.1 with full user thread support (fixes for bin/24066, gnu/33182, and as yet unfiled seg fault when resuming from a non-running thread) is available at: http://www.eventdriven.org/freebsd.html I sent patches to obrien but he never committed them nor responded to my e-mails. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message