From owner-freebsd-current Sun Apr 2 1:17:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 07C0437BD65 for ; Sun, 2 Apr 2000 01:17:06 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA00601 for ; Sun, 2 Apr 2000 11:15:11 +0200 (CEST) Message-Id: <200004020915.LAA00601@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@freebsd.org Subject: MLEN and crashes From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Apr 2000 11:15:11 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a HEADS UP. The recent increase in MLEN from 128 to 256 bytes led to very surprising problems with the latest, so called developers', version of isdn4bsd. The new version uses slcompress by default. The change in MLEN makes struct slcompress 2KB larger than it used to be. BTW the entry csu_hdr in struct cstate, which has size MLEN, is not used anywhere in the kernel that I could find. csu_hdr is what leads to the increase in the size of struct slcompress. There's a comment in slcompress.h which states that MAX_HDR should really be defined as 128 and not MLEN. Maybe this should be taken to heart and MAX_HDR redefined as 128 and not MLEN. But I digress. struct slcompress is now in struct sppp, which is passed by ispppcontrol as part of an ioctl call. Eventually the kernel lands in sppp_params, which does a copyin to a struct spppreq (which contains struct sppp) on the kernel stack. Because struct sppp is 2KB larger as a result of the change in MLEN the copyin overruns the kernel stack which immediately results in a crash - no trace output, no ddb, zilch. Interesting is that the crash only happens on a Pentium (tested with a II and III). On a K6 it doesn't happen. AFAICT it's not related to using the FPU for copyin/copyout since I turned that functionality off using npx0 flags and the crash still happened. Moving the struct spppreq into global address space solves the problem, but that makes the kernel BSS somewhat larger. Redefining MAX_HDR to be 128 also fixes the problem, even with the struct spppreq on the stack. If those of you using slcompress start seeing problems then they may well be due to the increase in MLEN. I wonder how wise it was to change MLEN without more testing. But hey, this is -current, that's what it's there for. Anyway, I think MAX_HDR should be hardwired to 128 in slcompress. Any comments ? -------- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 1:17:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 23B2537B51A; Sun, 2 Apr 2000 01:17:16 -0800 (PST) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id EAA14991; Sun, 2 Apr 2000 04:20:21 -0500 Message-ID: <38E71022.1BC1943E@raccoon.com> Date: Sun, 02 Apr 2000 04:17:22 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Jeremiah Gowdy Cc: freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD References: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremiah Gowdy wrote: > > Does anyone have any experiance or information about using HP JetDirect 500X > Printer Hubs with FreeBSD ? This is mission critical for my company, so any > information greatly appriciated. Ah...printers...my next to modems, my least favorite periphial to deal with. I have hooked up a lot of different printers to FreeBSD boxes and HP JetDirect cards don't work as well since they only allow 1-2 simultanious network conections to the printer. If you haven't purchased them yet get an Axis print server box instead. I highly recommend them. www.axis.com. JetDirect cards work, just not was well as Axis cards. It is also important that you upgrade your jetdirect firmware to the latest rev if this is an older card. There are some bugs specific to their LPD implimentation. You can also turn off banner pages on the later firmware code. johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 1:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id B4B2E37B9E1 for ; Sun, 2 Apr 2000 01:17:57 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12bgW0-000P1R-0K; Sun, 2 Apr 2000 09:17:53 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA08394; Sun, 2 Apr 2000 10:22:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 2 Apr 2000 10:24:27 +0100 (BST) From: Doug Rabson To: Nikolai Saoukh Cc: freebsd-current@freebsd.org Subject: Re: kldload of driver for isa pnp card (cycle two) In-Reply-To: <20000401000654.A34004@Draculina.otdel-1.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 Apr 2000, Nikolai Saoukh wrote: > On Fri, Mar 31, 2000 at 08:55:37PM +0100, Doug Rabson wrote: > > > I will try to tackle these issues soon. Due to other commitments, this > > won't happen for a few days though. > > Can I halp somehow? After I get the basics working, I'll contact you privately if you want to test things. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 1:21:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 0BB9537B844 for ; Sun, 2 Apr 2000 01:21:26 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12bgZF-000B1F-0X; Sun, 2 Apr 2000 10:21:14 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA08403; Sun, 2 Apr 2000 10:25:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 2 Apr 2000 10:27:40 +0100 (BST) From: Doug Rabson To: "Pierre Y. Dampure" Cc: current@freebsd.org Subject: Re: PNP dependant configs in /sys/isa/pnpparse.c In-Reply-To: <200004011212.NAA00316@bladerunner.k2c.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 1 Apr 2000, Pierre Y. Dampure wrote: > > Since revision 1.5 of the above, my kernel is giving me a "too many dependant > configs (8)" when probing PNP resources. > > Problem is, it looks like the SoundBlaster AWE 64 Gold advertises 8 different > PNP configurations (at least, that's what I got when i bumped MAXDEP to 16 and > rebooted in verbose mode). > > Is there a set limit to the number of PNP configurations that can be > advertised? if it's indeed 8, shouldn't the test read: > > if (ncfgs > MAXDEP) { > > rather than > > if (ncfgs >= MAXDEP) { > > Comments appreciated... > I'll look into it. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 1:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 51B7C37BD94 for ; Sun, 2 Apr 2000 01:22:59 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e329m9i25647; Sun, 2 Apr 2000 01:48:09 -0800 (PST) Date: Sun, 2 Apr 2000 01:48:08 -0800 From: Alfred Perlstein To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Message-ID: <20000402014808.A21029@fw.wintelcom.net> References: <200004020915.LAA00601@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004020915.LAA00601@peedub.muc.de>; from garyj@muc.de on Sun, Apr 02, 2000 at 11:15:11AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gary Jennejohn [000402 01:43] wrote: > This is a HEADS UP. > > The recent increase in MLEN from 128 to 256 bytes led to very surprising > problems with the latest, so called developers', version of isdn4bsd. > > The new version uses slcompress by default. The change in MLEN makes > struct slcompress 2KB larger than it used to be. BTW the entry csu_hdr > in struct cstate, which has size MLEN, is not used anywhere in the kernel > that I could find. csu_hdr is what leads to the increase in the size of > struct slcompress. There's a comment in slcompress.h which states that > MAX_HDR should really be defined as 128 and not MLEN. Maybe this should > be taken to heart and MAX_HDR redefined as 128 and not MLEN. > > But I digress. > > struct slcompress is now in struct sppp, which is passed by ispppcontrol > as part of an ioctl call. Eventually the kernel lands in sppp_params, > which does a copyin to a struct spppreq (which contains struct sppp) on > the kernel stack. Because struct sppp is 2KB larger as a result of the > change in MLEN the copyin overruns the kernel stack which immediately > results in a crash - no trace output, no ddb, zilch. > Interesting is that the crash only happens on a Pentium (tested with > a II and III). On a K6 it doesn't happen. AFAICT it's not related to > using the FPU for copyin/copyout since I turned that functionality > off using npx0 flags and the crash still happened. > > Moving the struct spppreq into global address space solves the problem, > but that makes the kernel BSS somewhat larger. Redefining MAX_HDR to be > 128 also fixes the problem, even with the struct spppreq on the stack. > > If those of you using slcompress start seeing problems then they may well > be due to the increase in MLEN. > > I wonder how wise it was to change MLEN without more testing. But hey, > this is -current, that's what it's there for. > > Anyway, I think MAX_HDR should be hardwired to 128 in slcompress. Any > comments ? > Why not just malloc the structure instread of using a stack variable? Various other parts of the kernel do so to get around this problem, since we're heading up SMP now it _not_ the time to start using global variables. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 3:28: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 5374137B5CC; Sun, 2 Apr 2000 03:27:47 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F5491.dip0.t-ipconnect.de [193.159.84.145]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id LAA32152; Sun, 2 Apr 2000 11:27:18 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id EAFA6AC2C; Sun, 2 Apr 2000 12:29:35 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA03913; Sun, 2 Apr 2000 12:27:11 +0200 (CEST) (envelope-from alex) Date: Sun, 2 Apr 2000 12:27:11 +0200 From: Alexander Langer To: Andrew MacIntyre Cc: Jeremiah Gowdy , freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions Subject: Re: JetDirect 500X and FreeBSD Message-ID: <20000402122711.B2024@cichlids.cichlids.com> Mail-Followup-To: Andrew MacIntyre , Jeremiah Gowdy , freebsd-hackers@FreeBSD.ORG, current@FreeBSD.ORG, FreeBSD questions References: <004a01bf9b35$0cc56be0$0100000a@vista1.sdca.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from andymac@bullseye.apana.org.au on Sun, Apr 02, 2000 at 01:52:12PM +1000 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Andrew MacIntyre (andymac@bullseye.apana.org.au): > they weren't particularly reliable, particularly when multiple jobs were > queued simultaneously. I hope their more recent stuff is better behaved. It is now. A further thing is: If your LaserJet doesn't understand PostScript, you have to use apsfilter. I do it this way here at home, the Windows-boxes use the JetDirect directly (the Windows software is REALLY nice!) Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 4:37:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mgate04.so-net.ne.jp (mgate04.so-net.ne.jp [210.139.254.151]) by hub.freebsd.org (Postfix) with ESMTP id 2DD0C37BC09 for ; Sun, 2 Apr 2000 04:37:39 -0700 (PDT) (envelope-from daito@magical.egg.or.jp) Received: from mail.rj8.so-net.ne.jp (mspool04.so-net.ne.jp [210.139.254.183]) by mgate04.so-net.ne.jp (8.8.8+3.0Wbeta9/3.6W00032811) with ESMTP id UAA23798 for ; Sun, 2 Apr 2000 20:37:34 +0900 (JST) Received: from MAIL (pfa6f57.tkyont.ap.so-net.ne.jp [210.250.111.87]) by mail.rj8.so-net.ne.jp (8.9.3/3.7W99092111) with SMTP id UAA16020 for ; Sun, 2 Apr 2000 20:37:33 +0900 (JST) Message-ID: <2705.954676073408@magical.egg.or.jp> Date: Sun, 02 Apr 2000 20:47:53 +0900 (JST) From: =?iso-2022-jp?B?GyRCJSIlJCVJJWsjMiMwIzAjMRsoQhsoQg==?= Reply-To: daito@magical.egg.or.jp To: =?iso-2022-jp?B??= Subject: =?iso-2022-jp?B?GyRCIXolIiUkJUklayMyIzAjMCMxJSohPCVXGyhCGyhC?==?iso-2022-jp?B?GyRCJXMhKkw1TkFCTjgzJGIkIiRqIXobKEIbKEI=?= Mime-Version: 1.0 Content-Type: text/plain; charset =ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ================================================================== $B!!!!!!!!!!!!%"%$%I%k#2#0#0#1%*!<%W%s!*!*(B ================================================================== $B"##R#e#a#l#G#2!!%i%$%V%A%c%C%H?74k2h2q0wBgJg=8!*!*(B $B!!K\%5%$%H$O!"7n!9$NDj3[NA6b#1#0#0#0#01_$G!"2q0w$K$J$i$l$?3'MM$K$O!"%W(B $B%m%0%i%`$N%5!<%S%9Cf$G$"$l$P!"$$$/$i$G$b#R#e#a#l#G#2%W%l!<%d$r3hMQ$7$?(B $B%i%$%V1GA|$G$N%A%c%C%H$,!"3Z$7$`$+$H$,$G$-$^$9!#(B $B"##1#0J,4VL5NABN83%5!<%S%9!*!*(B $B!!%5%$%H$,%*!<%W%s$9$k#37n#2#1$h$j!!:G=i$N#1#0J,4V$,$*;n$7BN83$H$7$FL5(B $BNA$H$J$j$^$9!#(B $B#1#0J,4V7P$A$^$9$H<+F0E*$K2hLL$,Dd;_$7$^$9$N$G!"8e$GNA6b$r@A5a$9$k$H$$(B $B$C$?%H%i%V%k$O!"$"$j$^$;$s!#(B $B"#2q0w$N3'MM8BDj!*8+$k$3$H$N$G$-$J$$%W%i%$%Y!<%H$J1GA|!*!)(B $B!!%i%$%V%A%c%C%H%W%m%0%i%`%5!<%S%90J30$N;~4VBS$O!"=w$N;R$?$A$N%W%i%$%Y(B $B!<%H1GA|$r!"$[$H$s$IL5JT=8$N>uBV$G8+$k$3$H$,$G$-$^$9!#(B $B?o;~!"<}O?$7$??7$7$$$b$N$rA}$d$7$F!"%i%$%V%i%j!<2=$7$F$$$/M=Dj$G$9!#(B $B"#(B2000$BG/%(%C%=%l!<%9%/!<%s$NHSEg??M3!"(B2000$BG/%V%l%$%/@#A0$N@n0fCN0!5*(B 4$B7n(B6$BF|$+$i=iIqBf$KD)@o$9$k!"@>4]M%;R$i!"7]G=3&$G%a%A%c4hD%$C$F$$$k!"=w(B $B$N;RC#$,$>$/$>$/EP>l$9$k!"%i%$%V%A%c%C%H$G$9!#(B $B=w$N;RC#$N%W%m%b!<%7%g%s%S%G%*$O!"$@$l$G$b8+$l$^$9!"$N$G!"@'Hs$N$>$-$K(B $BMh$F2<$5$$!#%a%s%P!<@lMQ$N?eCe%S%G%*@):nM=DjM-$j!#(B $B"#(B6$B7n$K$O%*%U2q$r9T$J$$$^$9!#(B $B%"%$%I%kC#$KD>@\2q$$$KMh$F2<$5$$!#(B $BR2p$7$F2<$5$$!#(B $B!!7]G=3&$rL\;X$92D0&$$=w$N;R$r@'Hs>R2p$7$F2<$5$$!#:NMQ$5$;$F$$$?$@$$$?(B $B>l9g$O!"(B $B!!FCJLM%6x$5$;$F$$$?$@$-$^$9!#(B (I%%%$B#I#D#O#L#2#0#0#1(I%%%(B http://www.leotv.com/idol2001$B!!(B $B#G#A#L#s%W%m%U%#!<%k$H%i%$%V%A%c%C%H%9%1%8%e!<%k$r$4;2>H$/$@$5$$(B(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 4:57:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8DB3937B5BD for ; Sun, 2 Apr 2000 04:57:18 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 15004 invoked from network); 2 Apr 2000 11:57:14 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 2 Apr 2000 11:57:14 -0000 Date: Sun, 2 Apr 2000 21:56:55 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: <200004020915.LAA00601@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Apr 2000, Gary Jennejohn wrote: > struct slcompress is now in struct sppp, which is passed by ispppcontrol > as part of an ioctl call. Eventually the kernel lands in sppp_params, > which does a copyin to a struct spppreq (which contains struct sppp) on > the kernel stack. Because struct sppp is 2KB larger as a result of the > change in MLEN the copyin overruns the kernel stack which immediately > results in a crash - no trace output, no ddb, zilch. It's just a bug to allocate big structs on the kernel stack. Almost all structs are too big for utility routines. Top levels of syscall routines and a few other routines that are known not to be called from deep in the kernel stack can use moderately big structs. 512 bytes is probably too big for i386's now. The effective kernel stack size was shrunk by about 2K by the sigset_t changes, so there is only about 5K of kernel stack. > Interesting is that the crash only happens on a Pentium (tested with > a II and III). On a K6 it doesn't happen. AFAICT it's not related to > using the FPU for copyin/copyout since I turned that functionality > off using npx0 flags and the crash still happened. The behaviour is unpredictable. Severe cases will be detected as a double fault if you're lucky. The sigset_t changes gave an extra 2K of signal variables to clobber before there is a double fault :-). > Moving the struct spppreq into global address space solves the problem, > but that makes the kernel BSS somewhat larger. Redefining MAX_HDR to be > 128 also fixes the problem, even with the struct spppreq on the stack. Big structs need to be malloced. I think removing the unused bloat in `struct cstate' is the correct fix for this particular allocation. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 6:41:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id E450D37B6AC for ; Sun, 2 Apr 2000 06:41:46 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id D5B742CE69; Sun, 2 Apr 2000 15:41:39 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id B2B3B1C562B; Sun, 2 Apr 2000 15:39:35 +0200 (EET) Date: Sun, 2 Apr 2000 15:39:35 +0200 From: Vallo Kallaste To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402153935.A64937@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402015016.C24134@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 01:50:16AM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote: > > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on > > 7x 200M disks - it does not hang for me since a long time. > > The latest current I tested R5 well is from 19th March on alpha. That's shortly > > before PHKs changes - I don't beleave that it introduced something new. > > The only problem with R5 I know of is parity corruption because of a bug in > > lockrange() for which I've already send you a fix. Even it is a general bug it > > seems only to cause problems together with softupdates. > > Ops - I oversaw that this happened with a recent current. > The best I can say is that it is likely that it happened after the 19th March. I got now crash under 4.0-RELEASE, with syncer and bufdaemon in the same vrlock state, pax in flswait. I was in single-user mode using pax to extract usr archive to newly created raid5 volume. I'm using NFS mount with flags -3i -r16384 -w16384 over 100Mbit full-duplex link, fxp driver on both sides. Note that I'm using stripe unit size 512k now, otherwise same. Here's handcopy of DDB messages: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc1e03ef4 stack pointer = 0x10:0xc0244a84 frame pointer = 0x10:0xc0244aa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio kernel: type 12 trap, code=0 Stopped at complete_rqe+0x18: movl 0x4(%eax),%edx db> trace complete_rqe at complete_rqe+0x18 biodone at biodone+0x53 ad_interrupt at ad_interrupt+0x2e2 ata_intr at ata_intr+0xca Xresume15() at Xresume15+0x2b --- interrupt, eip = 0xc020e5ae, esp = 0xc0244b54, ebp = 0 --- default_halt() at default_halt+0x2 I hook up serial console to get full traceback next time, but I don't have any knowledge for further analysis. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 6:44:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp06.wxs.nl (smtp06.wxs.nl [195.121.6.58]) by hub.freebsd.org (Postfix) with ESMTP id DD13F37B833 for ; Sun, 2 Apr 2000 06:44:11 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (ipc379e4a5.dial.wxs.nl [195.121.228.165]) by smtp06.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FSE5WT01.C06 for ; Sun, 2 Apr 2000 15:38:53 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id PAA91631 for current@freebsd.org; Sun, 2 Apr 2000 15:08:18 +0200 (CEST) (envelope-from asmodai) Date: Sun, 2 Apr 2000 15:08:17 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: Summer/winter time problems with daily/460 Message-ID: <20000402150817.C21619@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just went through a few logfiles: Checking for rejected mail hosts: -1d: Cannot apply date adjustment usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] Someone more acquainted with the daily scripts may want to investigate/fix that. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Veni, Vidi, Vici... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 7: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 5A5CF37BD2A for ; Sun, 2 Apr 2000 07:05:36 -0700 (PDT) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id XAA28747; Sun, 2 Apr 2000 23:04:53 +0900 (JST) To: current@FreeBSD.org Subject: Please review newbus patch for amd and adv From: Takahashi Yoshihiro X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000402230532V.nyan@dd.catv.ne.jp> Date: Sun, 02 Apr 2000 23:05:32 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I converted the amd and adv drivers to new-bus. But, as I am not familiar with these drivers and new-bus, maybe I have mistaken. Will somebody please review these changes? For amd driver: http://home.jp.FreeBSD.org/~nyan/patches/amd.diff.gz For adv driver: http://home.jp.FreeBSD.org/~nyan/patches/advansys.diff.gz --- Takahashi Yoshihiro The Center for Information Science, Kogakuin Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 7:16:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CFBD37B5BD for ; Sun, 2 Apr 2000 07:16:09 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA06409; Sun, 2 Apr 2000 10:16:05 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200004021416.KAA06409@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: MLEN and crashes References: <200004020915.LAA00601@peedub.muc.de> In-reply-to: Your message of "Sun, 02 Apr 2000 11:15:11 +0200." <200004020915.LAA00601@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Apr 2000 10:16:05 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wonder how wise it was to change MLEN without more testing. But hey, > this is -current, that's what it's there for. I've been running with MLEN set to 256 bytes for more than a year for reasons unrelated to this commit, and haven't seen any problems at all. (Of course, I don't use sppp..) It's unclear how this could have been caught by more testing unless the tester was using sppp. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8: 9:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 07CFA37BD9E; Sun, 2 Apr 2000 08:09:13 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-36.iptelecom.net.ua [212.9.227.100]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id SAA04526; Sun, 2 Apr 2000 18:14:53 +0300 (EEST) Message-ID: <38E7631B.E06D3D70@altavista.net> Date: Sun, 02 Apr 2000 18:11:23 +0300 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: MIHIRA Sanpei Yoshiro Cc: cg@FreeBSD.ORG, current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Buffering issues of the pcm audio driver (Was: cvs commit: src/sys/dev/sound/isa ess.c) References: <38E68B29.2055235C@altavista.net> <200004021437.XAA34730@lavender.yy.cs.keio.ac.jp> Content-Type: multipart/mixed; boundary="------------42AABDBF5E5B30EDD5BCA01F" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------42AABDBF5E5B30EDD5BCA01F Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Hi, I've tried to track down sound issues of the SDL (Simple Direct Layer) library and found that current pcm buffering behaviour inconsistent with OSS specifications, which cause applications that require sophisticated sound control to misbehave on FreeBSD. There is two different buffers implemented in the pcm driver: one back-end, with size specified an a compile time (ranging from 4KB to 64KB on different chipsets), and one front-end size of which could be changed by the audio application at runtime. Problems arises when application tries to get current state of the audio buffer either by using select(), or by doing direct SNDCTL_DSP_GETOSPACE ioctl(). In both these cases current FreeBSD behaviour isn't consistent with OSS specs: - the SNDCTL_DSP_GETOSPACE ioctl() returns current state of the front buffer, while ignores much larger back buffer which usually absorbs all data sent to the pcm. Thus application using this ioctl() being fooled about how much data is in the audio buffers. - the select() call doesn't block until the whole back buffer will be filled, while according to specs it should block while fragsize*fragnumber amount of data already is in the buffers. Possible solution (from better to worse): 1. Fix select() support in the pcm driver to account effects of the two buffers. 2. Provide workaround to the SNDCTL_DSP_GETOSPACE to return largest free buffer space available in either front or back buffer. Thus aware applications would have a possibility to check how much data is in hardware buffers and behave accordingly. This will not violate OSS specs, as it is permitted to have this value larger than fragsize*fragments. See attached diffs. 3. Decrease size of the back buffers in all pcm drivers to a some reasonable value like 4KB. -Maxim --------------42AABDBF5E5B30EDD5BCA01F Content-Type: text/plain; charset=x-user-defined; name="dsp.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dsp.c.diff" --- /usr/src/sys/dev/sound/pcm/dsp.c 2000/04/02 09:41:26 1.1 +++ /usr/src/sys/dev/sound/pcm/dsp.c 2000/04/02 09:49:56 @@ -467,8 +467,8 @@ chn_checkunderflow(wrch); while (chn_wrfeed(wrch) > 0); } - a->bytes = bs->fl; - a->fragments = a->bytes / wrch->blocksize2nd; + a->bytes = (bs->fl > b->fl ? bs->fl : b->fl); + a->fragments = bs->fl / wrch->blocksize2nd; a->fragstotal = bs->bufsize / wrch->blocksize2nd; a->fragsize = wrch->blocksize2nd; } --------------42AABDBF5E5B30EDD5BCA01F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8:17:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 07ED337B5EA for ; Sun, 2 Apr 2000 08:17:05 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id E48632CE69; Sun, 2 Apr 2000 17:16:55 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 5ECFA1C5629; Sun, 2 Apr 2000 17:17:00 +0200 (EET) Date: Sun, 2 Apr 2000 17:17:00 +0200 From: Vallo Kallaste To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402171700.A69460@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402153935.A64937@myhakas.matti.ee>; from vallo@myhakas.matti.ee on Sun, Apr 02, 2000 at 03:39:35PM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote: > I hook up serial console to get full traceback next time, but I don't > have any knowledge for further analysis. Here's full traceback, environment is all same, except the filesystem is mounted with async (before it was default, which is nosync I guess): sh-2.03# cd /usr sh-2.03# pax -r -pe -f /mnt/usr.pax Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0fa0ef4 stack pointer = 0x10:0xc0244a84 frame pointer = 0x10:0xc0244aa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio kernel: type 12 trap, code=0 Stopped at complete_rqe+0x18: movl 0x4(%eax),%edx db> trace complete_rqe(c1069020,c0f04000,c1882f00,0,c1882f00) at complete_rqe+0x18 biodone(c1069020,c0f04034,c1069020,c0ed4180,0) at biodone+0x53 ad_interrupt(c1882f00,0,0,c02051e5,c0ed4180) at ad_interrupt+0x2e2 ata_intr(c0ed4180,0,c00f0010,c0690010,ffff0010) at ata_intr+0xca Xresume14() at Xresume14+0x2b --- interrupt, eip = 0xc020e5ae, esp = 0xc0244b54, ebp = 0 --- default_halt() at default_halt+0x2 db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 40 cc3a5440 cd747000 0 6 40 004006 3 getblk c62d1cd0 pax 15 cc3a5100 cd74d000 0 1 15 000204 3 vinum c0fa0b68 vinum 6 cc3a55e0 cd744000 0 1 6 004086 3 wait cc3a55e0 bash 5 cc3a5780 cc3b2000 0 0 0 000204 3 vrlock 52f801 syncer 4 cc3a5920 cc3b0000 0 0 0 100204 3 vrlock 582001 bufdaemon 3 cc3a5ac0 cc3ae000 0 0 0 000204 3 psleep c026c3c0 vmdaemon 2 cc3a5c60 cc3ac000 0 0 0 100204 3 psleep c0254df8 pagedaemon 1 cc3a5e00 cc3aa000 0 0 1 004284 3 wait cc3a5e00 init 0 c0274640 c02d2000 0 0 0 000204 3 sched c0274640 swapper db> I can give access to my system which is connected over null-modem to this test box. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8:37: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 2049E37BD33 for ; Sun, 2 Apr 2000 08:37:01 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id RAA18259; Sun, 2 Apr 2000 17:35:25 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id RAA30036; Sun, 2 Apr 2000 17:36:24 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id RAA25240; Sun, 2 Apr 2000 17:37:31 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 17:37:30 +0200 From: Bernd Walter To: Vallo Kallaste Cc: Bernd Walter , Greg Lehey , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402173729.A25194@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402153935.A64937@myhakas.matti.ee>; from vallo@matti.ee on Sun, Apr 02, 2000 at 03:39:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote: > I got now crash under 4.0-RELEASE, with syncer and bufdaemon in the same > vrlock state, pax in flswait. I was in single-user mode using pax to > extract usr archive to newly created raid5 volume. I'm using NFS mount > with flags -3i -r16384 -w16384 over 100Mbit full-duplex link, fxp > driver on both sides. Note that I'm using stripe unit size 512k now, > otherwise same. > > I hook up serial console to get full traceback next time, but I don't > have any knowledge for further analysis. You don't need a serial console to get further informations. You should compile the kernel with debug symbols and set dumpdev in rc.conf to get a crash dump. Are you for any chance running the NFS Server without nfsd? I expect them to be needed if you are serving vinum volumes. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8:38:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 34DA537BA47 for ; Sun, 2 Apr 2000 08:38:20 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA15130; Sun, 2 Apr 2000 17:38:01 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004021538.RAA15130@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402171700.A69460@myhakas.matti.ee> from Vallo Kallaste at "Apr 2, 2000 05:17:00 pm" To: vallo@matti.ee Date: Sun, 2 Apr 2000 17:38:01 +0200 (CEST) Cc: ticso@cicely.de (Bernd Walter), grog@lemis.com (Greg Lehey), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vallo Kallaste wrote: > On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote: > > > I hook up serial console to get full traceback next time, but I don't > > have any knowledge for further analysis. > > Here's full traceback, environment is all same, except the filesystem is > mounted with async (before it was default, which is nosync I guess): > > sh-2.03# cd /usr > sh-2.03# pax -r -pe -f /mnt/usr.pax This the exact problem I'm seeing here. Turning on INVARIANTS in the kernel shows that free'd malloc space are being reused when vinum is in the game :( > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x4 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0fa0ef4 > stack pointer = 0x10:0xc0244a84 > frame pointer = 0x10:0xc0244aa0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = bio > kernel: type 12 trap, code=0 > Stopped at complete_rqe+0x18: movl 0x4(%eax),%edx > db> trace > complete_rqe(c1069020,c0f04000,c1882f00,0,c1882f00) at complete_rqe+0x18 > biodone(c1069020,c0f04034,c1069020,c0ed4180,0) at biodone+0x53 > ad_interrupt(c1882f00,0,0,c02051e5,c0ed4180) at ad_interrupt+0x2e2 > ata_intr(c0ed4180,0,c00f0010,c0690010,ffff0010) at ata_intr+0xca > Xresume14() at Xresume14+0x2b > --- interrupt, eip = 0xc020e5ae, esp = 0xc0244b54, ebp = 0 --- > default_halt() at default_halt+0x2 > db> ps > pid proc addr uid ppid pgrp flag stat wmesg wchan cmd > 40 cc3a5440 cd747000 0 6 40 004006 3 getblk c62d1cd0 pax > 15 cc3a5100 cd74d000 0 1 15 000204 3 vinum c0fa0b68 vinum > 6 cc3a55e0 cd744000 0 1 6 004086 3 wait cc3a55e0 bash > 5 cc3a5780 cc3b2000 0 0 0 000204 3 vrlock 52f801 syncer > 4 cc3a5920 cc3b0000 0 0 0 100204 3 vrlock 582001 bufdaemon > 3 cc3a5ac0 cc3ae000 0 0 0 000204 3 psleep c026c3c0 vmdaemon > 2 cc3a5c60 cc3ac000 0 0 0 100204 3 psleep c0254df8 pagedaemon > 1 cc3a5e00 cc3aa000 0 0 1 004284 3 wait cc3a5e00 init > 0 c0274640 c02d2000 0 0 0 000204 3 sched c0274640 swapper > db> > > I can give access to my system which is connected over null-modem to > this test box. > -- > > Vallo Kallaste > vallo@matti.ee > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 473EA37BE0C for ; Sun, 2 Apr 2000 08:41:48 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id RAA18517; Sun, 2 Apr 2000 17:40:10 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id RAA30096; Sun, 2 Apr 2000 17:41:09 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id RAA25261; Sun, 2 Apr 2000 17:42:16 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 17:42:16 +0200 From: Bernd Walter To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402174216.B25194@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402015016.C24134@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 01:50:16AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote: > On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote: > > > > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on > > 7x 200M disks - it does not hang for me since a long time. > > The latest current I tested R5 well is from 19th March on alpha. That's shortly > > before PHKs changes - I don't beleave that it introduced something new. > > The only problem with R5 I know of is parity corruption because of a bug in > > lockrange() for which I've already send you a fix. Even it is a general bug it > > seems only to cause problems together with softupdates. > > Ops - I oversaw that this happened with a recent current. > The best I can say is that it is likely that it happened after the 19th March. I build a recent current and tested it with R5 and still don't see any hangs. Unfortunately I don't have a toy i386 system ready and testet on alpha. There may be some differences how data corruptions efects on this platform. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 8:52: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id F1DE037BBCC for ; Sun, 2 Apr 2000 08:51:57 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id RAA19070; Sun, 2 Apr 2000 17:50:21 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id RAA30114; Sun, 2 Apr 2000 17:51:22 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id RAA25287; Sun, 2 Apr 2000 17:52:26 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 17:52:26 +0200 From: Bernd Walter To: Vallo Kallaste Cc: Bernd Walter , Greg Lehey , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402175226.C25194@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402173729.A25194@cicely8.cicely.de>; from ticso on Sun, Apr 02, 2000 at 05:37:30PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 05:37:30PM +0200, Bernd Walter wrote: > Are you for any chance running the NFS Server without nfsd? > I expect them to be needed if you are serving vinum volumes. Sometimes I'm to stupid - the NFS case was a different thread. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 9:16:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 9614D37B55D for ; Sun, 2 Apr 2000 09:16:16 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id SAA20411; Sun, 2 Apr 2000 18:14:36 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id SAA30153; Sun, 2 Apr 2000 18:15:35 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id SAA25329; Sun, 2 Apr 2000 18:16:43 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 18:16:43 +0200 From: Bernd Walter To: Soren Schmidt Cc: vallo@matti.ee, Bernd Walter , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402181643.D25194@cicely8.cicely.de> References: <20000402171700.A69460@myhakas.matti.ee> <200004021538.RAA15130@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021538.RAA15130@freebsd.dk>; from sos@freebsd.dk on Sun, Apr 02, 2000 at 05:38:01PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 05:38:01PM +0200, Soren Schmidt wrote: > It seems Vallo Kallaste wrote: > > On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote: > > > > > I hook up serial console to get full traceback next time, but I don't > > > have any knowledge for further analysis. > > > > Here's full traceback, environment is all same, except the filesystem is > > mounted with async (before it was default, which is nosync I guess): > > > > sh-2.03# cd /usr > > sh-2.03# pax -r -pe -f /mnt/usr.pax > > This the exact problem I'm seeing here. > Turning on INVARIANTS in the kernel shows that free'd malloc space > are being reused when vinum is in the game :( Do you see it only with R5 or also with other organisations? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 9:38: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8F40437BE05 for ; Sun, 2 Apr 2000 09:37:57 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA30446; Sun, 2 Apr 2000 18:37:44 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004021637.SAA30446@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402181643.D25194@cicely8.cicely.de> from Bernd Walter at "Apr 2, 2000 06:16:43 pm" To: ticso@cicely.de (Bernd Walter) Date: Sun, 2 Apr 2000 18:37:44 +0200 (CEST) Cc: vallo@matti.ee, grog@lemis.com (Greg Lehey), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bernd Walter wrote: > On Sun, Apr 02, 2000 at 05:38:01PM +0200, Soren Schmidt wrote: > > It seems Vallo Kallaste wrote: > > > On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste wrote: > > > > > > > I hook up serial console to get full traceback next time, but I don't > > > > have any knowledge for further analysis. > > > > > > Here's full traceback, environment is all same, except the filesystem is > > > mounted with async (before it was default, which is nosync I guess): > > > > > > sh-2.03# cd /usr > > > sh-2.03# pax -r -pe -f /mnt/usr.pax > > > > This the exact problem I'm seeing here. > > Turning on INVARIANTS in the kernel shows that free'd malloc space > > are being reused when vinum is in the game :( > > Do you see it only with R5 or also with other organisations? I've only tried RAID5, thats the one I have a use for... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 9:52:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id A336737B99A for ; Sun, 2 Apr 2000 09:52:12 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from rccr.cremona.it (modem-1-2.rccr.cremona.it [192.168.2.12]) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with ESMTP id SAA01554 for ; Sun, 2 Apr 2000 18:47:28 +0200 Received: (from mirko@localhost) by rccr1.rccr.cremona.it (8.9.3/8.9.3) id SAA01488 for freebsd-current@FreeBSD.ORG; Sun, 2 Apr 2000 18:48:13 +0200 (MET DST) Message-Id: <200004021648.SAA01488@rccr1.rccr.cremona.it> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v148.2.1) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.1) Received: by NeXT.Mailer (1.148.2.1) From: Mirko Viviani Date: Sun, 2 Apr 2000 17:04:32 +0200 To: freebsd-current@FreeBSD.ORG Subject: GDB 5... Reply-To: mirko.viviani@rccr.cremona.it Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ciao. As stated in gdb mlist, gdb 5.0 is on the way but it hasn't support for freebsd-elf in the package. Is there anyone that could explain me why ? Thanks. --- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 9:58:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3C3AA37BCFD; Sun, 2 Apr 2000 09:58:09 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id JAA09654; Sun, 2 Apr 2000 09:58:09 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 2 Apr 2000 09:58:08 -0700 (PDT) From: Kris Kennaway To: Mirko Viviani Cc: freebsd-current@FreeBSD.ORG Subject: Re: GDB 5... In-Reply-To: <200004021648.SAA01488@rccr1.rccr.cremona.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Apr 2000, Mirko Viviani wrote: > Ciao. > > As stated in gdb mlist, gdb 5.0 is on the way but it hasn't support for > freebsd-elf in > the package. Is there anyone that could explain me why ? You're more likely to get an answer by asking the gdb developers on the gdb "mlist" :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 10: 3: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id E42A137BE30 for ; Sun, 2 Apr 2000 10:02:50 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id TAA01074; Sun, 2 Apr 2000 19:00:17 +0200 (CEST) Message-Id: <200004021700.TAA01074@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 02 Apr 2000 13:57:24 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Apr 2000 19:00:17 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: >On Sun, 2 Apr 2000, Gary Jennejohn wrote: >> Moving the struct spppreq into global address space solves the problem, >> but that makes the kernel BSS somewhat larger. Redefining MAX_HDR to be >> 128 also fixes the problem, even with the struct spppreq on the stack. > >Big structs need to be malloced. > Yes, but how does one know that a struct is too big ? Before the increase in MLEN strucct sppp was not too big. >I think removing the unused bloat in `struct cstate' is the correct fix >for this particular allocation. > I think we should nuke csu_hdr since it's not used anywhere. Is that what you really mean ? --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 11: 3: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 8483D37B5D4 for ; Sun, 2 Apr 2000 11:02:57 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id BA23D2CE6C; Sun, 2 Apr 2000 20:02:49 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id DF52D1C5629; Sun, 2 Apr 2000 20:02:54 +0200 (EET) Date: Sun, 2 Apr 2000 20:02:54 +0200 From: Vallo Kallaste To: Bernd Walter Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402200254.A69811@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402173729.A25194@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 05:37:30PM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 05:37:30PM +0200, Bernd Walter wrote: > > I hook up serial console to get full traceback next time, but I don't > > have any knowledge for further analysis. > > You don't need a serial console to get further informations. > You should compile the kernel with debug symbols and set dumpdev in rc.conf > to get a crash dump. > > Are you for any chance running the NFS Server without nfsd? > I expect them to be needed if you are serving vinum volumes. Yes, but I don't have space for crashdump and I can't build new kernel with limited memory usage because I don't have /usr filesystem up and running. Is there a way to limit memory usage without recompiling kernel? I can store 32MB crashdump at the moment, no separate /var filesystem because I thought 4.0-RELEASE will be stable enough for experimenting with vinum.. I don't have another 4.0-RELEASE or stable system but I'll try to build 4.0-R kernel on -current system. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 11:18:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id CD6A937B5A7 for ; Sun, 2 Apr 2000 11:18:31 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id CB2682CE6D; Sun, 2 Apr 2000 20:18:21 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 119A81C562B; Sun, 2 Apr 2000 20:18:27 +0200 (EET) Date: Sun, 2 Apr 2000 20:18:27 +0200 From: Vallo Kallaste To: Bernd Walter Cc: Soren Schmidt , Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402201826.A69925@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000402171700.A69460@myhakas.matti.ee> <200004021538.RAA15130@freebsd.dk> <20000402181643.D25194@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402181643.D25194@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 06:16:43PM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 06:16:43PM +0200, Bernd Walter wrote: > Do you see it only with R5 or also with other organisations? I don't have any problems with my own -current system which has striped volume over three UW SCSI disks. SCSI-only system, SMP. Sources from March 14. I had no problems with striped volume over two ATA disks in the first round with test box, then I added the two disks, configured raid5 and here we are 8-) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 12: 7: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 3DB6D37BB18 for ; Sun, 2 Apr 2000 12:07:02 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id VAA29870; Sun, 2 Apr 2000 21:05:27 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id VAA30613; Sun, 2 Apr 2000 21:06:25 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id VAA25531; Sun, 2 Apr 2000 21:07:33 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 21:07:33 +0200 From: Bernd Walter To: Vallo Kallaste Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402210733.A25516@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> <20000402200254.A69811@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402200254.A69811@myhakas.matti.ee>; from vallo@matti.ee on Sun, Apr 02, 2000 at 08:02:54PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote: > Yes, but I don't have space for crashdump and I can't build new kernel > with limited memory usage because I don't have /usr filesystem up and > running. Is there a way to limit memory usage without recompiling > kernel? I can store 32MB crashdump at the moment, no separate /var > filesystem because I thought 4.0-RELEASE will be stable enough for > experimenting with vinum.. > I don't have another 4.0-RELEASE or stable system but I'll try to build > 4.0-R kernel on -current system. Just to clearify the things... Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 12:12:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2917037BE30 for ; Sun, 2 Apr 2000 12:12:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA67427; Sun, 2 Apr 2000 21:12:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004021912.VAA67427@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402210733.A25516@cicely8.cicely.de> from Bernd Walter at "Apr 2, 2000 09:07:33 pm" To: ticso@cicely.de (Bernd Walter) Date: Sun, 2 Apr 2000 21:12:45 +0200 (CEST) Cc: vallo@matti.ee (Vallo Kallaste), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bernd Walter wrote: > On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote: > > Yes, but I don't have space for crashdump and I can't build new kernel > > with limited memory usage because I don't have /usr filesystem up and > > running. Is there a way to limit memory usage without recompiling > > kernel? I can store 32MB crashdump at the moment, no separate /var > > filesystem because I thought 4.0-RELEASE will be stable enough for > > experimenting with vinum.. > > I don't have another 4.0-RELEASE or stable system but I'll try to build > > 4.0-R kernel on -current system. > > Just to clearify the things... > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it might only occur with RAID5... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 12:25:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 99E2037BAFD for ; Sun, 2 Apr 2000 12:25:55 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e32JnvZ09986; Sun, 2 Apr 2000 12:49:57 -0700 (PDT) Date: Sun, 2 Apr 2000 12:49:57 -0700 From: Alfred Perlstein To: Soren Schmidt Cc: Bernd Walter , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402124957.M21029@fw.wintelcom.net> References: <20000402210733.A25516@cicely8.cicely.de> <200004021912.VAA67427@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021912.VAA67427@freebsd.dk>; from sos@freebsd.dk on Sun, Apr 02, 2000 at 09:12:45PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [000402 12:42] wrote: > It seems Bernd Walter wrote: > > On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote: > > > Yes, but I don't have space for crashdump and I can't build new kernel > > > with limited memory usage because I don't have /usr filesystem up and > > > running. Is there a way to limit memory usage without recompiling > > > kernel? I can store 32MB crashdump at the moment, no separate /var > > > filesystem because I thought 4.0-RELEASE will be stable enough for > > > experimenting with vinum.. > > > I don't have another 4.0-RELEASE or stable system but I'll try to build > > > 4.0-R kernel on -current system. > > > > Just to clearify the things... > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? > > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it > might only occur with RAID5... I've never seen it with just a striped setup: # Vinum configuration of thumper, saved at Sun Apr 2 16:34:43 2000 drive vinumdrive1 device /dev/da0s1e drive vinumdrive2 device /dev/da1s1e volume vinum0 plex name vinum0.p0 org striped 512s vol vinum0 sd name vinum0.p0.s0 drive vinumdrive1 plex vinum0.p0 len 16782848s driveoffset 265s plexoffset 0s sd name vinum0.p0.s1 drive vinumdrive2 plex vinum0.p0 len 16782848s driveoffset 265s plexoffset 512s just FYI. Have any of you guys running vinum had any problems with phk's recent patches with bio? Just wanted to know if I should take the plunge. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 12:40:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0CB1137B5CF for ; Sun, 2 Apr 2000 12:40:31 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA73985; Sun, 2 Apr 2000 21:39:36 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004021939.VAA73985@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402124957.M21029@fw.wintelcom.net> from Alfred Perlstein at "Apr 2, 2000 12:49:57 pm" To: bright@wintelcom.net (Alfred Perlstein) Date: Sun, 2 Apr 2000 21:39:36 +0200 (CEST) Cc: ticso@cicely.de (Bernd Walter), vallo@matti.ee (Vallo Kallaste), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alfred Perlstein wrote: > > > Just to clearify the things... > > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? > > > > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it > > might only occur with RAID5... > > I've never seen it with just a striped setup: > Have any of you guys running vinum had any problems with phk's recent > patches with bio? Just wanted to know if I should take the plunge. I dont think vinum is/was usable under -current at least not the RAID5 stuff, its broken, and some of it is because greg is not up to date with what -current looks like these days. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 13:13:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from laurin.munich.netsurf.de (laurin.munich.netsurf.de [194.64.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C29AB37BA4D for ; Sun, 2 Apr 2000 13:13:07 -0700 (PDT) (envelope-from Dirk.Roehrdanz@munich.netsurf.de) Received: from ns1134.munich.netsurf.de (ns1134.munich.netsurf.de [195.180.235.134]) by laurin.munich.netsurf.de (8.9.3/8.9.3) with ESMTP id WAA00021 for ; Sun, 2 Apr 2000 22:13:01 +0200 (MET DST) Received: (qmail 753 invoked by uid 1001); 2 Apr 2000 20:14:12 -0000 Date: Sun, 2 Apr 2000 22:14:12 +0200 From: Dirk Roehrdanz To: current@FreeBSD.ORG Subject: Re: RSA library problems Message-ID: <20000402221412.A661@diroxfbsd.dx> References: <38DA4E03.CB2E84A8@originative.co.uk> <20000331122424.A19141@diroxfbsd.dx> <38E55ED2.6A41C3DD@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E55ED2.6A41C3DD@acm.org>; from bloom@acm.org on Fri, Mar 31, 2000 at 09:28:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jim, On 0, Jim Bloom wrote: > A similar patch was added for the USA version of RSA for the same basic reason. > Your patch is almost correct. It should add the line: > > LDADD+= -L$[.OBJDIR]/../libcrypto -lcrypto ^ ^ > > Your version would reference the system crypto library and not the one being > built as part of buildworld. > > Jim Bloom > bloom@acm.org > Thanks for the modification. I have replaced the "[]" with "{}" . A run of "make buildworld" with the patch finished without errors. The output of objdump --private-headers on the created librsaINTL.so.1 libs under /usr/obj contains now the line "NEEDED libcrypto.so.1". Apache-modssl works now with encryption! Should I file a pr with the patch ? Regards Dirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 13:17:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 0D63537B66B for ; Sun, 2 Apr 2000 13:17:51 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id WAA03936; Sun, 2 Apr 2000 22:16:21 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id WAA30815; Sun, 2 Apr 2000 22:17:22 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id WAA25616; Sun, 2 Apr 2000 22:18:30 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 22:18:29 +0200 From: Bernd Walter To: Soren Schmidt Cc: Alfred Perlstein , Bernd Walter , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402221829.A25555@cicely8.cicely.de> References: <20000402124957.M21029@fw.wintelcom.net> <200004021939.VAA73985@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021939.VAA73985@freebsd.dk>; from sos@freebsd.dk on Sun, Apr 02, 2000 at 09:39:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote: > I dont think vinum is/was usable under -current at least not the > RAID5 stuff, its broken, and some of it is because greg is not > up to date with what -current looks like these days. Can you please explain what have massivly changed in current that relates to vinum? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 13:22:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8F35D37B990 for ; Sun, 2 Apr 2000 13:22:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA84522; Sun, 2 Apr 2000 22:22:40 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004022022.WAA84522@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000402221829.A25555@cicely8.cicely.de> from Bernd Walter at "Apr 2, 2000 10:18:29 pm" To: ticso@cicely.de (Bernd Walter) Date: Sun, 2 Apr 2000 22:22:39 +0200 (CEST) Cc: bright@wintelcom.net (Alfred Perlstein), vallo@matti.ee (Vallo Kallaste), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bernd Walter wrote: > On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote: > > I dont think vinum is/was usable under -current at least not the > > RAID5 stuff, its broken, and some of it is because greg is not > > up to date with what -current looks like these days. > > Can you please explain what have massivly changed in current that relates > to vinum? The changes done by phk to seperate out the io stuff from struct buf. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 14:44:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fuggle.veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id D3F4337B9B8 for ; Sun, 2 Apr 2000 14:44:49 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from veldy (cascade.veldy.net [192.168.0.1]) by fuggle.veldy.net (Postfix) with SMTP id 665D7193E for ; Sun, 2 Apr 2000 16:48:34 -0500 (CDT) Message-ID: <007501bf9cec$e0b77e80$0100a8c0@veldy.net> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Perl 5.6.0? Date: Sun, 2 Apr 2000 16:46:18 -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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any plans to merge perl-5.6.0 into current? I don't have any plans for using it currently, but I curious. Thanks, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 14:56:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 24E8D37B631 for ; Sun, 2 Apr 2000 14:56:25 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id RAA59020; Sun, 2 Apr 2000 17:56:22 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 2 Apr 2000 17:56:22 -0400 (EDT) From: Chuck Robey To: "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: <007501bf9cec$e0b77e80$0100a8c0@veldy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > Are there any plans to merge perl-5.6.0 into current? I don't have any > plans for using it currently, but I curious. Hmm. What with the nightmarish build structure of perl, I'm sure that reading this is just going to wreck Mark's day. In light of that, and in the absence of both any real software that needs the upgrade, and lack of confidence in a really squeaky new release, why don't we all grant Mark a little slack on this, at least for a while. Else we're going to have a drooling Mark on our hands :-) Unless, of course, you want to do it *for* Mark? > > Thanks, > > Tom Veldhouse > veldy@veldy.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:12:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A5B4837BB3C for ; Sun, 2 Apr 2000 15:12:19 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e32MZwQ14612; Sun, 2 Apr 2000 15:35:58 -0700 (PDT) Date: Sun, 2 Apr 2000 15:35:58 -0700 From: Alfred Perlstein To: Soren Schmidt Cc: Bernd Walter , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402153557.O21029@fw.wintelcom.net> References: <20000402124957.M21029@fw.wintelcom.net> <200004021939.VAA73985@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021939.VAA73985@freebsd.dk>; from sos@freebsd.dk on Sun, Apr 02, 2000 at 09:39:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [000402 13:05] wrote: > It seems Alfred Perlstein wrote: > > > > Just to clearify the things... > > > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? > > > > > > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it > > > might only occur with RAID5... > > > > I've never seen it with just a striped setup: > > Have any of you guys running vinum had any problems with phk's recent > > patches with bio? Just wanted to know if I should take the plunge. > > I dont think vinum is/was usable under -current at least not the > RAID5 stuff, its broken, and some of it is because greg is not > up to date with what -current looks like these days. Took a chance... So far my make world is proceeding fine with a kernel from ~1 hour ago. However I'm only using vinum for striping, not mirroring or RAID-5. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:13:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 2C3BC37BB72 for ; Sun, 2 Apr 2000 15:13:07 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id HAA41611; Mon, 3 Apr 2000 07:41:54 +0930 (CST) Date: Mon, 3 Apr 2000 07:41:54 +0930 From: Greg Lehey To: Soren Schmidt Cc: Bernd Walter , Alfred Perlstein , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403074154.Q59549@freebie.lemis.com> References: <20000402221829.A25555@cicely8.cicely.de> <200004022022.WAA84522@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004022022.WAA84522@freebsd.dk> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 2 April 2000 at 22:22:39 +0200, Søren Schmidt wrote: > It seems Bernd Walter wrote: >> On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote: >>> I dont think vinum is/was usable under -current at least not the >>> RAID5 stuff, its broken, and some of it is because greg is not >>> up to date with what -current looks like these days. >> >> Can you please explain what have massivly changed in current that relates >> to vinum? > > The changes done by phk to seperate out the io stuff from struct > buf. Alfred and Bernd came up with fixes that seem to work. I still need to review them, but I'm in the process of installing an up-to-date -CURRENT on my test box. Watch this space. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:14:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 3897137BB5B for ; Sun, 2 Apr 2000 15:14:23 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id HAA41632; Mon, 3 Apr 2000 07:43:00 +0930 (CST) Date: Mon, 3 Apr 2000 07:43:00 +0930 From: Greg Lehey To: Bernd Walter Cc: Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403074300.R59549@freebie.lemis.com> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402174216.B25194@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000402174216.B25194@cicely8.cicely.de> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 2 April 2000 at 17:42:16 +0200, Bernd Walter wrote: > On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote: >> On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote: >>> >>> Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on >>> 7x 200M disks - it does not hang for me since a long time. >>> The latest current I tested R5 well is from 19th March on alpha. That's shortly >>> before PHKs changes - I don't beleave that it introduced something new. >>> The only problem with R5 I know of is parity corruption because of a bug in >>> lockrange() for which I've already send you a fix. Even it is a general bug it >>> seems only to cause problems together with softupdates. >> >> Ops - I oversaw that this happened with a recent current. >> The best I can say is that it is likely that it happened after the 19th March. > > I build a recent current and tested it with R5 and still don't see any hangs. > Unfortunately I don't have a toy i386 system ready and testet on alpha. > There may be some differences how data corruptions efects on this platform. I found a potentially serious bug in the RAID calculations yesterday: it assumed that sizeof (int) == 4. I suspect that it would just slow down the calculations, but in any case I've fixed it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:16:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AF5C637BB5B for ; Sun, 2 Apr 2000 15:16:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA50901; Sun, 2 Apr 2000 15:15:44 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 15:15:44 -0700 (PDT) From: Matthew Dillon Message-Id: <200004022215.PAA50901@apollo.backplane.com> To: Greg Lehey Cc: Soren Schmidt , Bernd Walter , Alfred Perlstein , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 References: <20000402221829.A25555@cicely8.cicely.de> <200004022022.WAA84522@freebsd.dk> <20000403074154.Q59549@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>> to vinum? :> :> The changes done by phk to seperate out the io stuff from struct :> buf. : :Alfred and Bernd came up with fixes that seem to work. I still need :to review them, but I'm in the process of installing an up-to-date :-CURRENT on my test box. Watch this space. : :Greg I won't mess with the buffer allocation idea until after you've stabilized vinum. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:35:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 9528C37B6AC for ; Sun, 2 Apr 2000 15:35:54 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA12074; Mon, 3 Apr 2000 00:31:33 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id AAA31146; Mon, 3 Apr 2000 00:32:33 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA25790; Mon, 3 Apr 2000 00:33:40 +0200 (CEST) (envelope-from ticso) Date: Mon, 3 Apr 2000 00:33:40 +0200 From: Bernd Walter To: Greg Lehey Cc: Soren Schmidt , Bernd Walter , Alfred Perlstein , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403003339.C25555@cicely8.cicely.de> References: <20000402221829.A25555@cicely8.cicely.de> <200004022022.WAA84522@freebsd.dk> <20000403074154.Q59549@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <20000403074154.Q59549@freebie.lemis.com>; from grog@lemis.com on Mon, Apr 03, 2000 at 07:41:54AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 07:41:54AM +0930, Greg Lehey wrote: > On Sunday, 2 April 2000 at 22:22:39 +0200, Søren Schmidt wrote: > > It seems Bernd Walter wrote: > >> On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote: > >>> I dont think vinum is/was usable under -current at least not the > >>> RAID5 stuff, its broken, and some of it is because greg is not > >>> up to date with what -current looks like these days. > >> > >> Can you please explain what have massivly changed in current that relates > >> to vinum? > > > > The changes done by phk to seperate out the io stuff from struct > > buf. Yes but as the time being he only did some small changes as a preparation for the bigger ones still coming. If that were massivly changes I can't imagine the words to describe what the future brings... > Alfred and Bernd came up with fixes that seem to work. I still need > to review them, but I'm in the process of installing an up-to-date > -CURRENT on my test box. Watch this space. I'm running current with striped and R5 on alpha and Niels Chr. Bank-Pedersen checked this for striping on i386 - I asume Alfred also did. Afaik no degraded R5 tests yet but they should work as before. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 15:40:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id E234D37BBD2 for ; Sun, 2 Apr 2000 15:40:53 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id AAA12503; Mon, 3 Apr 2000 00:38:46 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id AAA31208; Mon, 3 Apr 2000 00:39:46 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA25818; Mon, 3 Apr 2000 00:40:53 +0200 (CEST) (envelope-from ticso) Date: Mon, 3 Apr 2000 00:40:53 +0200 From: Bernd Walter To: Greg Lehey Cc: Bernd Walter , Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403004053.D25555@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402174216.B25194@cicely8.cicely.de> <20000403074300.R59549@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000403074300.R59549@freebie.lemis.com>; from grog@lemis.com on Mon, Apr 03, 2000 at 07:43:00AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 07:43:00AM +0930, Greg Lehey wrote: > I found a potentially serious bug in the RAID calculations yesterday: > it assumed that sizeof (int) == 4. I suspect that it would just slow > down the calculations, but in any case I've fixed it. That's generaly not good but allways true on all FreeBSD platforms. Only long and pointers are different: 64bit on alpha and 32bit on i386 - char short and int are the same. I asume you mean the xor loop limitations - I already took a look at them before running R5 on alpha - the only reason to change here is speed as 64bit operations would be faster on alpha. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16: 5:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id AA83F37BC03 for ; Sun, 2 Apr 2000 16:05:45 -0700 (PDT) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id 37C713D24; Sun, 2 Apr 2000 19:04:42 -0400 (EDT) Date: Sun, 2 Apr 2000 19:04:42 -0400 From: Josh Tiefenbach To: current@freebsd.org Subject: kernel build busted in /sys/dev/sound/pci/emu10k1.c (fix included) Message-ID: <20000402190441.A70904@snickers.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="AhhlLboLdkugWU4S" X-Mailer: Mutt 1.0pre2i Organization: Hah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii In attempting to test out Cameron's emu10k1 support, one quickly notices that the build dies in $SUBJECT due to unresolved constants. The attached patch fixes the problem. I'm happy to report that mpg123 is playing mp3's quite fine. There's a little burst of static when it first starts up, but other than that, things look fine for me. josh -- Give me rampant intellectualism as a coping strategy! -- Chuck Palahniuk in Invisible Monsters --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="emu.patch" --- emu10k1.h Sun Apr 2 03:41:17 2000 +++ /tmp/emu10k1.h Sun Apr 2 19:01:32 2000 @@ -663,4 +663,12 @@ #define HIWORD_RESULT_MASK 0x000ffc00 /* Instruction result */ #define HIWORD_OPA_MASK 0x000003ff /* Instruction operand A */ +/* Following constants lifted from Creative's hwaccess.h file */ +/* Needed to get emu10k1.c rev 1.1 to compile */ +#define ENABLE 0xffffffff +#define DISABLE 0x00000000 + +#define ENV_ON 0x80 +#define ENV_OFF 0x00 + #endif /* _8010_H */ --AhhlLboLdkugWU4S-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16:10:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4401A37BB78; Sun, 2 Apr 2000 16:10:35 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e32NZrH16183; Sun, 2 Apr 2000 16:35:53 -0700 (PDT) Date: Sun, 2 Apr 2000 16:35:53 -0700 From: Alfred Perlstein To: Matt Dillon Cc: current@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c Message-ID: <20000402163552.P21029@fw.wintelcom.net> References: <200004021752.KAA13175@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021752.KAA13175@freefall.freebsd.org>; from dillon@FreeBSD.org on Sun, Apr 02, 2000 at 10:52:44AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [000402 11:18] wrote: > dillon 2000/04/02 10:52:44 PDT > > Modified files: > sys/i386/i386 support.s > sys/kern init_sysent.c kern_prot.c kern_sig.c > Log: > Make the sigprocmask() and geteuid() system calls MP SAFE. Expand > commentary for copyin/copyout to indicate that they are MP SAFE as > well. Along with snagging the "easy ones" for MP safeness, shouldn't getpid be MP safe? The struct proc is allocated from the proc_zone, and afaik zalloc allows for stable storage meaning it's safe to dereference the ppid pointer once the entire struct proc is populated, which needs to happen before the process can even call getpid(). phk seems to agree. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16:12:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6597037B58F for ; Sun, 2 Apr 2000 16:12:47 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA51299; Sun, 2 Apr 2000 16:12:18 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 16:12:18 -0700 (PDT) From: Matthew Dillon Message-Id: <200004022312.QAA51299@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Along with snagging the "easy ones" for MP safeness, shouldn't getpid :be MP safe? The struct proc is allocated from the proc_zone, and :afaik zalloc allows for stable storage meaning it's safe to dereference :the ppid pointer once the entire struct proc is populated, which needs :to happen before the process can even call getpid(). : :phk seems to agree. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] :"I have the heart of a child; I keep it in a jar on my desk." The problem is that getpid() also extracts the ppid (look at the syscall code), which is not MP safe. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16:22:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F1B0637BAD7 for ; Sun, 2 Apr 2000 16:22:18 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e32Nl0c16467; Sun, 2 Apr 2000 16:47:00 -0700 (PDT) Date: Sun, 2 Apr 2000 16:47:00 -0700 From: Alfred Perlstein To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c Message-ID: <20000402164700.R21029@fw.wintelcom.net> References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004022312.QAA51299@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Apr 02, 2000 at 04:12:18PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000402 16:37] wrote: > > :Along with snagging the "easy ones" for MP safeness, shouldn't getpid > :be MP safe? The struct proc is allocated from the proc_zone, and > :afaik zalloc allows for stable storage meaning it's safe to dereference > :the ppid pointer once the entire struct proc is populated, which needs > :to happen before the process can even call getpid(). > : > :phk seems to agree. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > :"I have the heart of a child; I keep it in a jar on my desk." > > The problem is that getpid() also extracts the ppid (look at > the syscall code), which is not MP safe. I did look at the code, struct proc is allocated from a zone, meaning it won't "go away" once allocated, there's no danger in dereferencing p_pptr, I don't get it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16:38:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A7D7D37BB7A for ; Sun, 2 Apr 2000 16:38:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA51565; Sun, 2 Apr 2000 16:38:38 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 16:38:38 -0700 (PDT) From: Matthew Dillon Message-Id: <200004022338.QAA51565@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I did look at the code, struct proc is allocated from a zone, :meaning it won't "go away" once allocated, there's no danger in :dereferencing p_pptr, I don't get it. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] :"I have the heart of a child; I keep it in a jar on my desk." What happens when the parent process exits and the system must reassign the parent to process 1? Now think about what happens when it occurs on one cpu while another is trying to access the ppid. cpu#1: cpu#2: read p->p_pptr indirect through to get ppid (stalls on a cache miss plus, due to heavy DMA, stalls on main memory) parent process finishes exiting, replaces p_pptr of children, releases struct proc. struct proc is reused, pid is reallocated read completes, wrong ppid is returned (neither the original ppid nor ppid 1 is returned). In an SMP system you have to assume the worst case, and the worst case is that a cpu can stall INDEFINITELY between instructions. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 16:58:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2665137B570 for ; Sun, 2 Apr 2000 16:58:32 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e330NnZ17390; Sun, 2 Apr 2000 17:23:49 -0700 (PDT) Date: Sun, 2 Apr 2000 17:23:49 -0700 From: Alfred Perlstein To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c Message-ID: <20000402172349.T21029@fw.wintelcom.net> References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> <200004022338.QAA51565@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004022338.QAA51565@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Apr 02, 2000 at 04:38:38PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000402 17:04] wrote: > > :I did look at the code, struct proc is allocated from a zone, > :meaning it won't "go away" once allocated, there's no danger in > :dereferencing p_pptr, I don't get it. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > :"I have the heart of a child; I keep it in a jar on my desk." > > What happens when the parent process exits and the system must > reassign the parent to process 1? Now think about what happens > when it occurs on one cpu while another is trying to access the > ppid. > > cpu#1: cpu#2: > > read p->p_pptr > indirect through to get ppid > (stalls on a cache miss plus, > due to heavy DMA, stalls on main memory) > parent process finishes > exiting, replaces p_pptr > of children, releases > struct proc. > > struct proc is reused, > pid is reallocated > read completes, wrong ppid is returned > (neither the original ppid nor ppid 1 > is returned). > > In an SMP system you have to assume the worst case, and the worst case > is that a cpu can stall INDEFINITELY between instructions. Good call. Ugh, I should think about this more, but i'll just grasp at straws and suggest that p_pptr is set to volatile variable, and we re-read it after we snarf the pid from the pointer and make sure it hasn't changed out from under us. Either that or store it in the child's proc struct as well. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 17:38:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 789F237BB2B for ; Sun, 2 Apr 2000 17:38:46 -0700 (PDT) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.251.241]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id UAA23548; Sun, 2 Apr 2000 20:38:41 -0400 (EDT) Message-ID: <38E7E811.DD52F9D2@acm.org> Date: Sun, 02 Apr 2000 20:38:41 -0400 From: Jim Bloom X-Mailer: Mozilla 4.72 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dirk Roehrdanz Cc: current@FreeBSD.ORG Subject: Re: RSA library problems References: <38DA4E03.CB2E84A8@originative.co.uk> <20000331122424.A19141@diroxfbsd.dx> <38E55ED2.6A41C3DD@acm.org> <20000402221412.A661@diroxfbsd.dx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dirk Roehrdanz wrote: > > Thanks for the modification. > I have replaced the "[]" with "{}" . A run of "make buildworld" with > the patch finished without errors. Sorry about that. I did it quickly and the font I was using has the characters looking identical. Time to change fonts :-) > The output of objdump --private-headers on the created librsaINTL.so.1 > libs under /usr/obj contains now the line "NEEDED libcrypto.so.1". > Apache-modssl works now with encryption! Good news. I was sure that would fix the problem. > > Should I file a pr with the patch ? If you like. Hopefully someone will pick it up from the list sooner and commit the patch. send-pr is the official channel for reporting bugs. Jim Bloom bloom@acm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 18: 4:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6D58837BCC4 for ; Sun, 2 Apr 2000 18:04:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA85370; Sun, 2 Apr 2000 19:04:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA56398; Sun, 2 Apr 2000 19:03:51 -0600 (MDT) Message-Id: <200004030103.TAA56398@harmony.village.org> To: Takahashi Yoshihiro Subject: Re: Please review newbus patch for amd and adv Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 02 Apr 2000 23:05:32 +0900." <20000402230532V.nyan@dd.catv.ne.jp> References: <20000402230532V.nyan@dd.catv.ne.jp> Date: Sun, 02 Apr 2000 19:03:51 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000402230532V.nyan@dd.catv.ne.jp> Takahashi Yoshihiro writes: : For adv driver: : http://home.jp.FreeBSD.org/~nyan/patches/advansys.diff.gz I took a look at this change. For the most part it looks good. However, I have a question. Why did you move the adv_isa into the md files file and then comment it out for pc98? I'm confused. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 18:32:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 30D0637BCDA for ; Sun, 2 Apr 2000 18:32:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA52156; Sun, 2 Apr 2000 18:32:20 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 18:32:20 -0700 (PDT) From: Matthew Dillon Message-Id: <200004030132.SAA52156@apollo.backplane.com> To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> <200004022338.QAA51565@apollo.backplane.com> <20000402172349.T21029@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Good call. : :Ugh, I should think about this more, but i'll just grasp at straws :and suggest that p_pptr is set to volatile variable, and we re-read :it after we snarf the pid from the pointer and make sure it hasn't :changed out from under us. : :Either that or store it in the child's proc struct as well. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Re-reading is still somewhat dangerous due to the non-deterministic nature of the possible changes, whereas with monotonically increasing timers re-reading can be made to work in an SMP-safe fashion. In general it isn't worth getting that convoluted. I think the MP-safe code can make certain assumptions about the consistency of curproc, but outside of that we have to be very very careful. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 19:55:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id CF1FB37BC7F for ; Sun, 2 Apr 2000 19:55:20 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id VAA75792 for current@freebsd.org; Sun, 2 Apr 2000 21:55:20 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004030255.VAA75792@celery.dragondata.com> Subject: Load average calculation? To: current@freebsd.org Date: Sun, 2 Apr 2000 21:55:19 -0500 (CDT) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure if this is -current fodder or not, but since it's still happening in -current, I'll ask. We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown on 5.0-current, too). Before, with the exact same load, we'd see load averages from between 0.20 and 0.30. Now, we're getting: load averages: 4.16, 4.23, 4.66 Top shows the same CPU percentages, just a much higher load average for the same work being done. Did the load average calculation change, or something with the scheduler differ? Customers are complaining that the load average is too high, which is kinda silly, since 4.0 seems noticably faster in some cases. Any ideas? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 20:49:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 71A0737B5D4 for ; Sun, 2 Apr 2000 20:49:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA52843; Sun, 2 Apr 2000 20:49:10 -0700 (PDT) (envelope-from dillon) Date: Sun, 2 Apr 2000 20:49:10 -0700 (PDT) From: Matthew Dillon Message-Id: <200004030349.UAA52843@apollo.backplane.com> To: Kevin Day Cc: current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030255.VAA75792@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm not sure if this is -current fodder or not, but since it's still :happening in -current, I'll ask. : :We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown :on 5.0-current, too). Before, with the exact same load, we'd see load :averages from between 0.20 and 0.30. Now, we're getting: : :load averages: 4.16, 4.23, 4.66 : :Top shows the same CPU percentages, just a much higher load average for the :same work being done. Did the load average calculation change, or something :with the scheduler differ? Customers are complaining that the load average :is too high, which is kinda silly, since 4.0 seems noticably faster in some :cases. : :Any ideas? : :Kevin I believe the load average was changed quite a while ago to reflect not only runnable processes but also processes stuck in disk-wait. It's a more accurate measure of load. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 21:11:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 3891137B942 for ; Sun, 2 Apr 2000 21:11:08 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id XAA75906; Sun, 2 Apr 2000 23:10:59 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004030410.XAA75906@celery.dragondata.com> Subject: Re: Load average calculation? To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 2 Apr 2000 23:10:59 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), current@FreeBSD.ORG In-Reply-To: <200004030349.UAA52843@apollo.backplane.com> from "Matthew Dillon" at Apr 02, 2000 08:49:10 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown > :on 5.0-current, too). Before, with the exact same load, we'd see load > :averages from between 0.20 and 0.30. Now, we're getting: > : > :load averages: 4.16, 4.23, 4.66 > : > :Top shows the same CPU percentages, just a much higher load average for the > :same work being done. Did the load average calculation change, or something > :with the scheduler differ? Customers are complaining that the load average > :is too high, which is kinda silly, since 4.0 seems noticably faster in some > :cases. > : > :Any ideas? > : > :Kevin > > I believe the load average was changed quite a while ago to reflect not > only runnable processes but also processes stuck in disk-wait. It's > a more accurate measure of load. > Ahh, and since nearly everything is done on this system via NFS, I can imagine that several things are waiting for NFS responses. It's probably more accurate, but from a PR standpoint it makes it "look" like FreeBSD is choking under the load, when it really isn't. Or am I the only one that even cares about this? :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 22:49:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 3C5A937B67B for ; Sun, 2 Apr 2000 22:49:09 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 9139 invoked from network); 3 Apr 2000 05:49:07 -0000 Received: from acs-63-90-88-170.zbzoom.net (HELO cvzoom.net) (63.90.88.170) by ns.cvzoom.net with SMTP; 3 Apr 2000 05:49:07 -0000 Message-ID: <38E830B9.F56032C5@cvzoom.net> Date: Mon, 03 Apr 2000 01:48:41 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Recent commits to /sys/dev/sound/isa/ess.c Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried this, and the buffer size of 16k doesn't work too well with the ESS 1868 isa. The fist .3 seconds or so of the beginning of the clip plays in an infinite loop. I bumped down the buffer size to 12k, and it seems to work pretty well. Actually, I tried experimenting with various buffer sizes, and anything from 4k to 12k seems to work, and the ranges 8k to 12k seem to work best. I think 12k is the best from what I've heard, but I'm not sure. Also, timidity is broken (ESS 1868) with the lastest revisions to pcm. pcm is a little flakier than it used to be, but not by much. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 22:51:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id EDA0237B50E for ; Sun, 2 Apr 2000 22:51:41 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 99c8f334c649856e3f2cdadc4054e412) with ESMTP id <20000403060010.DSXG11967.relay01@chello.nl>; Mon, 3 Apr 2000 08:00:10 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id HAA05595; Mon, 3 Apr 2000 07:51:31 +0200 (CEST) (envelope-from wkb) Date: Mon, 3 Apr 2000 07:51:31 +0200 From: Wilko Bulte To: Kevin Day Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Load average calculation? Message-ID: <20000403075130.B5528@yedi.wbnet> Reply-To: wc.bulte@chello.nl References: <200004030349.UAA52843@apollo.backplane.com> <200004030410.XAA75906@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004030410.XAA75906@celery.dragondata.com>; from toasty@dragondata.com on Sun, Apr 02, 2000 at 11:10:59PM -0500 X-OS: FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 11:10:59PM -0500, Kevin Day wrote: > > :We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown > > :on 5.0-current, too). Before, with the exact same load, we'd see load > > :averages from between 0.20 and 0.30. Now, we're getting: > > : > > :load averages: 4.16, 4.23, 4.66 > > : > > :Top shows the same CPU percentages, just a much higher load average for the > > :same work being done. Did the load average calculation change, or something > > :with the scheduler differ? Customers are complaining that the load average > > :is too high, which is kinda silly, since 4.0 seems noticably faster in some > > :cases. > > : > > :Any ideas? > > : > > :Kevin > > > > I believe the load average was changed quite a while ago to reflect not > > only runnable processes but also processes stuck in disk-wait. It's > > a more accurate measure of load. > > Ahh, and since nearly everything is done on this system via NFS, I can > imagine that several things are waiting for NFS responses. > > It's probably more accurate, but from a PR standpoint it makes it "look" > like FreeBSD is choking under the load, when it really isn't. Or am I the > only one that even cares about this? :) What does the man page for 'w' say about it? At least the change should be reflected there I guess. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 22:56:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id CC94F37BD63 for ; Sun, 2 Apr 2000 22:56:20 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id AAA76127; Mon, 3 Apr 2000 00:56:03 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004030556.AAA76127@celery.dragondata.com> Subject: Re: Load average calculation? To: wc.bulte@chello.nl Date: Mon, 3 Apr 2000 00:56:03 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG In-Reply-To: <20000403075130.B5528@yedi.wbnet> from "Wilko Bulte" at Apr 03, 2000 07:51:31 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I believe the load average was changed quite a while ago to reflect not > > > only runnable processes but also processes stuck in disk-wait. It's > > > a more accurate measure of load. > > > > Ahh, and since nearly everything is done on this system via NFS, I can > > imagine that several things are waiting for NFS responses. > > > > It's probably more accurate, but from a PR standpoint it makes it "look" > > like FreeBSD is choking under the load, when it really isn't. Or am I the > > only one that even cares about this? :) > > What does the man page for 'w' say about it? At least the change should be > reflected there I guess. getloadavg(3)(which 'w' and 'uptime' use) says: The getloadavg() function returns the number of processes in the system run queue averaged over various periods of time. The 'w' and 'uptime' manpages really don't mention anything relevant. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 23: 0:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 435F137B98E for ; Sun, 2 Apr 2000 23:00:26 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id HAA21497; Mon, 3 Apr 2000 07:59:48 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004030559.HAA21497@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000403074300.R59549@freebie.lemis.com> from Greg Lehey at "Apr 3, 2000 07:43:00 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 3 Apr 2000 07:59:48 +0200 (CEST) Cc: ticso@cicely.de (Bernd Walter), vallo@matti.ee, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > > Unfortunately I don't have a toy i386 system ready and testet on alpha. > > There may be some differences how data corruptions efects on this platform. > > I found a potentially serious bug in the RAID calculations yesterday: > it assumed that sizeof (int) == 4. I suspect that it would just slow > down the calculations, but in any case I've fixed it. This wont fix it on the i386 where the problem is, and btw I havn't seen any commits yet... Have you tried running a RAID5 on intel HW and have INVARIANTS in the kernel as I asked you to ?? Have you looked at the dumps I've put up that you asked for ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 23: 9:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from wyvern.cc.kogakuin.ac.jp (wyvern.cc.kogakuin.ac.jp [133.80.184.10]) by hub.freebsd.org (Postfix) with ESMTP id F0D6037B8F8 for ; Sun, 2 Apr 2000 23:09:14 -0700 (PDT) (envelope-from nyan@wyvern.cc.kogakuin.ac.jp) Received: from localhost (localhost [127.0.0.1]) by wyvern.cc.kogakuin.ac.jp (8.9.3+3.2W/3.7W/SAKURA) with ESMTP id PAA81332; Mon, 3 Apr 2000 15:09:08 +0900 (JST) To: imp@village.org Cc: current@FreeBSD.ORG Subject: Re: Please review newbus patch for amd and adv In-Reply-To: <200004030103.TAA56398@harmony.village.org> References: <20000402230532V.nyan@dd.catv.ne.jp> <200004030103.TAA56398@harmony.village.org> From: Takahashi Yoshihiro X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000403150908J.nyan@wyvern.cc.kogakuin.ac.jp> Date: Mon, 03 Apr 2000 15:09:08 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200004030103.TAA56398@harmony.village.org> Warner Losh writes: > In message <20000402230532V.nyan@dd.catv.ne.jp> Takahashi Yoshihiro writes: > : For adv driver: > : http://home.jp.FreeBSD.org/~nyan/patches/advansys.diff.gz > > I took a look at this change. For the most part it looks good. Thanks. > However, I have a question. Why did you move the adv_isa into the md > files file and then comment it out for pc98? I'm confused. Because, adv_isa.c is not required by PC-98, PC-98 requires only PCI frontend. Then it contains isa_dmacascade function which does not exist and is not needed for PC-98. The reason to comment out is to be clear that it is not required. If it is completely removed from files.pc98, we may guess wrong in the far future that we forgot to merge from files.i386. --- Takahashi Yoshihiro The Center for Information Science, Kogakuin Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 23:13:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E9C8237BBC5 for ; Sun, 2 Apr 2000 23:13:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA86616; Mon, 3 Apr 2000 00:13:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA59095; Mon, 3 Apr 2000 00:13:03 -0600 (MDT) Message-Id: <200004030613.AAA59095@harmony.village.org> To: Takahashi Yoshihiro Subject: Re: Please review newbus patch for amd and adv Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Apr 2000 15:09:08 +0900." <20000403150908J.nyan@wyvern.cc.kogakuin.ac.jp> References: <20000403150908J.nyan@wyvern.cc.kogakuin.ac.jp> <20000402230532V.nyan@dd.catv.ne.jp> <200004030103.TAA56398@harmony.village.org> Date: Mon, 03 Apr 2000 00:13:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000403150908J.nyan@wyvern.cc.kogakuin.ac.jp> Takahashi Yoshihiro writes: : Because, adv_isa.c is not required by PC-98, PC-98 requires only PCI : frontend. Then it contains isa_dmacascade function which does not : exist and is not needed for PC-98. Is that because there's not isa bus on a pc-98? Or that the adv_isa cannot possibly work on the ISA bus that is in a pc-98? If there's no isa on the pc98, then config should take care of not including it. So I'm a little confused here. If there is a isa bus, but it doesn't support dma, I think that we'd have problems with many different drivers, and not just adv. : The reason to comment out is to be clear that it is not required. If : it is completely removed from files.pc98, we may guess wrong in the : far future that we forgot to merge from files.i386. This part I understand. If it is a md file, then it makes sense to leave it commented out like you did. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 2 23:43: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A646637BB73 for ; Sun, 2 Apr 2000 23:43:04 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id CAA13542; Mon, 3 Apr 2000 02:42:41 -0400 (EDT) Message-ID: <20000403024241.A13365@netmonger.net> Date: Mon, 3 Apr 2000 02:42:41 -0400 From: Christopher Masto To: Chuck Robey , "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Perl 5.6.0? Mail-Followup-To: Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current References: <007501bf9cec$e0b77e80$0100a8c0@veldy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Chuck Robey on Sun, Apr 02, 2000 at 05:56:22PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 05:56:22PM -0400, Chuck Robey wrote: > On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > plans for using it currently, but I curious. > > Hmm. What with the nightmarish build structure of perl, I'm sure that > reading this is just going to wreck Mark's day. In light of that, and in > the absence of both any real software that needs the upgrade, and > lack of confidence in a really squeaky new release, why don't we all grant > Mark a little slack on this, at least for a while. I've been running Perl 5 since before it was included with FreeBSD, and I've never noticed anything nightmarish about the build process. I tried 5.6 a couple of days ago, and it built and tested out of the box. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:10:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5BB9A37BC27 for ; Mon, 3 Apr 2000 01:10:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA54079; Mon, 3 Apr 2000 01:10:17 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 01:10:17 -0700 (PDT) From: Matthew Dillon Message-Id: <200004030810.BAA54079@apollo.backplane.com> To: Kevin Day Cc: toasty@dragondata.com (Kevin Day), current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030410.XAA75906@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> a more accurate measure of load. :> : :Ahh, and since nearly everything is done on this system via NFS, I can :imagine that several things are waiting for NFS responses. : :It's probably more accurate, but from a PR standpoint it makes it "look" :like FreeBSD is choking under the load, when it really isn't. Or am I the :only one that even cares about this? :) : :Kevin Heh. You can always hack your kernel source locally. I think the code you want to mess around with is /usr/src/sys/vm/vm_meter.c, the 'loadav' procedure. Replacing the 'FALLTHROUGH' comment with a 'break;' statement ought to do the trick for you. I don't think we should change anything in the official tree. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:16:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id E632D37B67C; Mon, 3 Apr 2000 01:16:44 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA47232; Mon, 3 Apr 2000 17:46:15 +0930 (CST) Date: Mon, 3 Apr 2000 17:46:15 +0930 From: Greg Lehey To: Soren Schmidt Cc: Bernd Walter , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403174615.O42140@freebie.lemis.com> References: <20000403074300.R59549@freebie.lemis.com> <200004030559.HAA21497@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004030559.HAA21497@freebsd.dk> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 3 April 2000 at 7:59:48 +0200, Søren Schmidt wrote: > It seems Greg Lehey wrote: >>> Unfortunately I don't have a toy i386 system ready and testet on alpha. >>> There may be some differences how data corruptions efects on this platform. >> >> I found a potentially serious bug in the RAID calculations yesterday: >> it assumed that sizeof (int) == 4. I suspect that it would just slow >> down the calculations, but in any case I've fixed it. > > This wont fix it on the i386 where the problem is, and btw I havn't seen > any commits yet... No, I was just about to do something when phk changed the interfaces. I don't have the time to keep chasing him, so I'll wait until we have a relatively stable situation and then I'll continue. > Have you tried running a RAID5 on intel HW and have INVARIANTS in > the kernel as I asked you to ?? No, for the above reason. > Have you looked at the dumps I've put up that you asked for ?? Yes. I have some ideas, but before I can continue I need to get my test machine in a stable state. It could take a day or two. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:23:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id CD9EB37B5AE for ; Mon, 3 Apr 2000 01:23:09 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id A3F0C2CE67; Mon, 3 Apr 2000 10:23:05 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 3E6B81C5629; Mon, 3 Apr 2000 10:23:08 +0200 (EET) Date: Mon, 3 Apr 2000 10:23:08 +0200 From: Vallo Kallaste To: Bernd Walter Cc: Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000403102308.A71481@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> <20000402200254.A69811@myhakas.matti.ee> <20000402210733.A25516@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402210733.A25516@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 09:07:33PM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 09:07:33PM +0200, Bernd Walter wrote: > Just to clearify the things... > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? Here's the sequence of what I did: 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system built from March 31 sources. First I used striping over two disks and put /usr filesystem onto it, did overnight testing and all was well. 2. Same system, same sources plus two same disks. Now I tried raid5 over four disks and failed to extract pax archive, got deadlock, not panic. 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I failed to extract pax archive, got panic. No softupdates. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 962C837B67C for ; Mon, 3 Apr 2000 01:38:13 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA61927; Mon, 3 Apr 2000 10:36:21 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004030836.KAA61927@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000403174615.O42140@freebie.lemis.com> from Greg Lehey at "Apr 3, 2000 05:46:15 pm" To: grog@lemis.com (Greg Lehey) Date: Mon, 3 Apr 2000 10:36:21 +0200 (CEST) Cc: ticso@cicely.de (Bernd Walter), vallo@matti.ee, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Lehey wrote: > > This wont fix it on the i386 where the problem is, and btw I havn't seen > > any commits yet... > > No, I was just about to do something when phk changed the interfaces. > I don't have the time to keep chasing him, so I'll wait until we have > a relatively stable situation and then I'll continue. Thats a lame excuse, use RELENG_4 and be done with it for now, this problem is a serious showstopper for alot of people on exactly that branch. If you want vinum to gain users, RELENG_4 is the one tree you should care for _now_. > > Have you tried running a RAID5 on intel HW and have INVARIANTS in > > the kernel as I asked you to ?? > > No, for the above reason. > > > Have you looked at the dumps I've put up that you asked for ?? > > Yes. I have some ideas, but before I can continue I need to get my > test machine in a stable state. It could take a day or two. Thats exactly what RELENG_4 is for... *Sigh*, let me ask it this way then, are you going to invest the time in getting it to work any time soon ??, we have now been running in circles for over a week waiting for you to take this seriously... I need to know, and I need to know _soon_, or I'll have to either fix vinum myself, or use/invent something else... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:42:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7824837BD33 for ; Mon, 3 Apr 2000 01:42:25 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA63479; Mon, 3 Apr 2000 10:42:19 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004030842.KAA63479@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000403102308.A71481@myhakas.matti.ee> from Vallo Kallaste at "Apr 3, 2000 10:23:08 am" To: vallo@matti.ee Date: Mon, 3 Apr 2000 10:42:19 +0200 (CEST) Cc: ticso@cicely.de (Bernd Walter), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Vallo Kallaste wrote: > > Here's the sequence of what I did: > > 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system > built from March 31 sources. First I used striping over two disks and > put /usr filesystem onto it, did overnight testing and all was well. > 2. Same system, same sources plus two same disks. Now I tried raid5 over > four disks and failed to extract pax archive, got deadlock, not panic. > 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I > failed to extract pax archive, got panic. > No softupdates. Same story here, but using softupdates or async mounts I can reproduce the hang or panic in less than 60 secs.. Vinum with raid5 is plain broken, include INVARIANTS in the kernel and see why... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 1:43:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 5DBAA37B5AE for ; Mon, 3 Apr 2000 01:43:32 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2723 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Mon, 3 Apr 2000 10:43:20 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 6A6DC483D; Mon, 3 Apr 2000 10:43:30 +0200 (METDST) Subject: Re: MLEN and crashes In-Reply-To: from Bruce Evans at "Apr 2, 0 09:56:55 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 3 Apr 2000 10:43:30 +0200 (METDST) Cc: garyj@muc.de, freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1834 Message-Id: <20000403084330.6A6DC483D@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Bruce Evans: > It's just a bug to allocate big structs on the kernel stack. Please specify "big"! :-) I wonder how too "big" can be detected. The code in question is perfectly valid syntactically and semantically correct C-code. If a piece of code being considered buggy depends on the size of some externally defined "thing" (like the kernel stack size in this case) something - IMHO - is not in a good condition. Perhaps a sentence like "It's just a bug to allocate structs on the kernel stack" (note the missing "big") has to be put in style. Or a macro like (this is just a cheap shoot in the dark) void kernel_subr(void) { ALLOCATE_STRUCT_ON_STACK(struct bigstruct bigstr); .... could be created to check for potentially stack overflow at compile time and/or runtime and people are forced in style(9) to use it. > 512 bytes is probably too big for i386's now. The effective kernel stack > size was shrunk by about 2K by the sigset_t changes, so there is only > about 5K of kernel stack. Then isn't it time to make the kernel stack larger ? Please don't misunderstand. I can fully accept accecpt and acknowledge what you write (i've converted the piece of code in question to malloc'ing its data already), i'm just a bit concerned because its so perfectly legal and common to allocate a struct on the stack that i fear just that i and probably other don't think about it if it were not made absolutely clear and possibly enforced somehow to never do this in kernel land. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 2:13:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3429C37BA82 for ; Mon, 3 Apr 2000 02:13:50 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e339cwJ00962; Mon, 3 Apr 2000 02:38:58 -0700 (PDT) Date: Mon, 3 Apr 2000 02:38:58 -0700 From: Alfred Perlstein To: Hellmuth Michaelis Cc: Bruce Evans , garyj@muc.de, freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Message-ID: <20000403023858.F21029@fw.wintelcom.net> References: <20000403084330.6A6DC483D@hcswork.hcs.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000403084330.6A6DC483D@hcswork.hcs.de>; from hm@hcs.de on Mon, Apr 03, 2000 at 10:43:30AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Hellmuth Michaelis [000403 02:12] wrote: > >From the keyboard of Bruce Evans: > > > It's just a bug to allocate big structs on the kernel stack. > > Please specify "big"! :-) have a look at src/sys/nfs/nfs_vnops.c: line ~2787: #ifndef NFS_COMMITBVECSIZ #define NFS_COMMITBVECSIZ 20 #endif struct buf *bvec_on_stack[NFS_COMMITBVECSIZ]; int bvecsize = 0, bveccount; I guess 80 bytes is pushing it, some routines are worse, but 2k is totally out of line. If you're worried about such things happening then you can use the pre-processor to catch things that may make your structures too large. > I wonder how too "big" can be detected. The code in question is perfectly > valid syntactically and semantically correct C-code. There's code that #error (maybe #warning?) when it can detect that the size of a struct has been unreasonably grown, it's done via the pre-processor. > > If a piece of code being considered buggy depends on the size of some > externally defined "thing" (like the kernel stack size in this case) > something - IMHO - is not in a good condition. > > Perhaps a sentence like "It's just a bug to allocate structs on the > kernel stack" (note the missing "big") has to be put in style. Or a > macro like (this is just a cheap shoot in the dark) > > void > kernel_subr(void) > { > ALLOCATE_STRUCT_ON_STACK(struct bigstruct bigstr); > .... > > could be created to check for potentially stack overflow at compile > time and/or runtime and people are forced in style(9) to use it. noooooooooooooooooo :) > > 512 bytes is probably too big for i386's now. The effective kernel stack > > size was shrunk by about 2K by the sigset_t changes, so there is only > > about 5K of kernel stack. > > Then isn't it time to make the kernel stack larger ? > > Please don't misunderstand. I can fully accept accecpt and acknowledge what > you write (i've converted the piece of code in question to malloc'ing its > data already), i'm just a bit concerned because its so perfectly legal and > common to allocate a struct on the stack that i fear just that i and > probably other don't think about it if it were not made absolutely clear > and possibly enforced somehow to never do this in kernel land. When in doubt, ask. Design and Implementation clearly explains the kernel stack program as well as some other OS texts afaik. Just because it's legal C doesn't mean it's allowed, it's perfectly legal to do a lot of things in a usermode program that you can't do in a kernel routine, smashing the kernel stack is one of these things. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 2:55:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 5A2C437B67C for ; Mon, 3 Apr 2000 02:55:08 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 12c3ZV-000BZU-0V; Mon, 3 Apr 2000 10:55:02 +0100 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id KAA88548; Mon, 3 Apr 2000 10:57:14 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Mon, 3 Apr 2000 10:52:13 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Christopher Masto Cc: Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: <20000403024241.A13365@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there actually any good reasons why we _should_ upgrade in the first place? Security fixes, added functionality we require, etc. The perl we have is stable and the problems it has are well known, which is good enough in 99% of the cases. Including Perl in the make world build is something entirely different from doing a make install /usr/ports, I'm sure. Nick > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > > plans for using it currently, but I curious. > > > > Hmm. What with the nightmarish build structure of perl, I'm sure that > > reading this is just going to wreck Mark's day. In light of that, and in > > the absence of both any real software that needs the upgrade, and > > lack of confidence in a really squeaky new release, why don't we all grant > > Mark a little slack on this, at least for a while. > > I've been running Perl 5 since before it was included with FreeBSD, and > I've never noticed anything nightmarish about the build process. I > tried 5.6 a couple of days ago, and it built and tested out of the > box. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 2:56:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 9123B37B562 for ; Mon, 3 Apr 2000 02:56:42 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA48677; Mon, 3 Apr 2000 11:35:02 +0200 (CEST) Message-Id: <200004030935.LAA48677@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Alfred Perlstein Cc: Hellmuth Michaelis , freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 03 Apr 2000 11:13:50 +0200." <20000403023858.F21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 11:35:02 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: >* Hellmuth Michaelis [000403 02:12] wrote: >> Please don't misunderstand. I can fully accept accecpt and acknowledge what >> you write (i've converted the piece of code in question to malloc'ing its >> data already), i'm just a bit concerned because its so perfectly legal and >> common to allocate a struct on the stack that i fear just that i and >> probably other don't think about it if it were not made absolutely clear >> and possibly enforced somehow to never do this in kernel land. > >When in doubt, ask. Design and Implementation clearly explains the >kernel stack program as well as some other OS texts afaik. > >Just because it's legal C doesn't mean it's allowed, it's perfectly legal >to do a lot of things in a usermode program that you can't do in a >kernel routine, smashing the kernel stack is one of these things. :) > Yes, but it was perfectly legal to put the structure on the stack _before_ MLEN was doubled. If this is the attitude which now obtains, then there's a boatload of code in the kernel which is incorrect because structs are allocated on the stack without knowing how big they are at the *time of compilation*. This isn't a question of "was the routine sppp_params sloppily coded ?" (which I think Joerg would disagree with, since he wrote it). I still think that we should nuke csu_hdr from struct slcompress. It's not used in any code in our tree. I did a make buildowrld and a new kernel without csu_hdr and there were no errors. The change even made the kernel BSS 25KB smaller. --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3: 0:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id EC3EC37BE4F for ; Mon, 3 Apr 2000 03:00:46 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12c3et-0003sX-0C; Mon, 3 Apr 2000 10:00:36 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id LAA88748; Mon, 3 Apr 2000 11:02:47 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Mon, 3 Apr 2000 10:57:46 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Paul Haddad Cc: Christopher Masto , FreeBSD CURRENT Mailing List Subject: Re: Another current crash (cvs-cur.6183 In-Reply-To: <008501bf9b84$ad365270$0bac2ac0@pth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where are you guys now as far as USB drives are concerned? I've been looking a lot at the driver lately and would like to hear about any problems you have. Nick On Fri, 31 Mar 2000, Paul Haddad wrote: > Hi, > > Boy I wish I had read this message before I went out and bought a USB zip > drive... I'm in the exact same situation IOPENER with 4.0 installed and > screwed up to a point where I can boot but not mount the sandisk drive. I > figured that I would get a zip drive and mount it instead. > > Anyways if you found some way around this please let me know, otherwise I've > got to make another trip out and get a SuperDisk instead... > > BTW What state are you in? Mine will boot, but gets to the point where it > tries to mount the sandisk and panics with a ffs_write panic. Booting in > single user doesn't help. > --- > Paul Haddad (paul@pth.com) > Imagine that Cray computer decides to make a personal computer. It has > a 150 MHz processor, 200 megabytes of RAM, 1500 megabytes of disk > storage, a screen resolution of 4096 x 4096 pixels, relies entirely on > voice recognition for input, fits in your shirt pocket and costs $300. > What's the first question that the computer community asks? > > "Is it PC compatible?" > > ----- Original Message ----- > From: "Christopher Masto" > To: "Paul Richards" ; "Stephen Hocking-Senior > Programmer PGS SPS Perth" > Cc: ; > Sent: Wednesday, March 22, 2000 12:16 AM > Subject: Re: Another current crash (cvs-cur.6183 > > > > On Wed, Mar 22, 2000 at 03:02:02AM +0000, Paul Richards wrote: > > > I've got a different but I think related panic. > > > > > > #9 0xc0143280 in panic (fmt=0xc0250460 "vm_page_wakeup: page not > > > busy!!!") > > > at ../../kern/kern_shutdown.c:552 > > > #10 0xc01df583 in swp_pager_async_iodone (bp=0xc3236250) > > > at ../../vm/vm_page.h:346 > > > > I've been playing around with one of those iopener things and got > > myself into a state I thought I could get out of with the help of a > > USB Zip drive. Unfortunately, upon purchasing and connecting one, > > I discovered that I can't access it without a panic, which I > > point out here on the chance it's also related. > > > > #7 0xc024ac2c in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, > > tf_edi = -1018879976, tf_esi = 256, tf_ebp = -919618472, tf_isp > = -919618500, > > tf_ebx = -1071201278, tf_edx = 0, tf_ecx = -1070746656, tf_eax = 18, > > tf_trapno = 3, tf_err = 0, tf_eip = -1071396739, tf_cs = 8, > tf_eflags = 582, > > tf_esp = -1071099905, tf_ss = -1071212893}) at > ../../i386/i386/trap.c:549 > > #8 0xc023c87d in Debugger (msg=0xc02696a3 "panic") at > machine/cpufunc.h:64 > > #9 0xc01549e8 in panic (fmt=0xc026c402 "allocbuf: buffer too small") > > at ../../kern/kern_shutdown.c:552 > > #10 0xc0178f5a in allocbuf (bp=0xc3452018, size=83886080) at > ../../kern/vfs_bio.c:2346 > > #11 0xc0178f01 in geteblk (size=83886080) at ../../kern/vfs_bio.c:2315 > > #12 0xc025cb57 in dsinit (dev=0xc0be1e00, lp=0xc0c490f4, sspp=0xc0c490f0) > > at ../../kern/subr_diskmbr.c:186 > > #13 0xc015eec6 in dsopen (dev=0xc0be1e00, mode=8192, flags=0, > sspp=0xc0c490f0, > > lp=0xc0c490f4) at ../../kern/subr_diskslice.c:683 > > #14 0xc015dfbf in diskopen (dev=0xc0be1e00, oflags=1, devtype=8192, > p=0xc88be860) > > at ../../kern/subr_disk.c:146 > > #15 0xc018ae65 in spec_open (ap=0xc92fbe10) at > ../../miscfs/specfs/spec_vnops.c:191 > > #16 0xc018ad65 in spec_vnoperate (ap=0xc92fbe10) > > at ../../miscfs/specfs/spec_vnops.c:117 > > #17 0xc01ff2e9 in ufs_vnoperatespec (ap=0xc92fbe10) at > ../../ufs/ufs/ufs_vnops.c:2301 > > #18 0xc018595f in vn_open (ndp=0xc92fbedc, fmode=1, cmode=0) at > vnode_if.h:189 > > #19 0xc0181951 in open (p=0xc88be860, uap=0xc92fbf80) at > ../../kern/vfs_syscalls.c:994 > > #20 0xc024b4ce in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > > tf_edi = -1077937212, tf_esi = 134894800, tf_ebp = -1077937132, > > tf_isp = -919617580, tf_ebx = 0, tf_edx = 8, tf_ecx = 134894828, > tf_eax = 5, > > tf_trapno = 12, tf_err = 2, tf_eip = 672026540, tf_cs = 31, > tf_eflags = 642, > > tf_esp = -1077937316, tf_ss = 47}) at ../../i386/i386/trap.c:1073 > > #21 0xc023cf26 in Xint0x80_syscall () > > > > I'm not intimately familiar with the function involved, and I'm out of > > time tonight, so I'm backing up a few days to see if it goes away. > > -- > > Christopher Masto Senior Network Monkey NetMonger > Communications > > chris@netmonger.net info@netmonger.net > http://www.netmonger.net > > > > Free yourself, free your machine, free the daemon -- > http://www.freebsd.org/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3: 2:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id AADE637BF33 for ; Mon, 3 Apr 2000 03:02:06 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id MAA19867; Mon, 3 Apr 2000 12:01:22 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Gary Jennejohn Cc: Alfred Perlstein , Hellmuth Michaelis , freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-reply-to: Your message of "Mon, 03 Apr 2000 11:35:02 +0200." <200004030935.LAA48677@peedub.muc.de> Date: Mon, 03 Apr 2000 12:01:21 +0200 Message-ID: <19865.954756081@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004030935.LAA48677@peedub.muc.de>, Gary Jennejohn writes: >Yes, but it was perfectly legal to put the structure on the stack >_before_ MLEN was doubled. Just because it worked doesn't mean that it was correct. We need to be frugal about the kernel stack, for a lot of reasons, that's just the way it is, and as far as I know it is the way it will continue to be. Get used to it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3:18:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id AD99837BA9D for ; Mon, 3 Apr 2000 03:18:23 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id LAA34289; Mon, 3 Apr 2000 11:18:17 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA01870; Mon, 3 Apr 2000 11:18:13 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004031018.LAA01870@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Summer/winter time problems with daily/460 In-Reply-To: Message from Jeroen Ruigrok/Asmodai of "Sun, 02 Apr 2000 15:08:17 +0200." <20000402150817.C21619@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 11:18:13 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just went through a few logfiles: > > Checking for rejected mail hosts: > -1d: Cannot apply date adjustment > usage: date [-nu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... > [-f fmt date | [[[[[cc]yy]mm]dd]HH]MM[.ss]] [+format] > > Someone more acquainted with the daily scripts may want to > investigate/fix that. Yep, I've made a mental note to get this sorted this year.... > -- > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best > The BSD Programmer's Documentation Project > Veni, Vidi, Vici... -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3:35:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5493C37BDAE for ; Mon, 3 Apr 2000 03:35:14 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12c4CE-000IMZ-00; Mon, 03 Apr 2000 12:35:02 +0200 From: Sheldon Hearn To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-reply-to: Your message of "Sat, 01 Apr 2000 17:03:24 PST." <200004020103.RAA43602@apollo.backplane.com> Date: Mon, 03 Apr 2000 12:35:02 +0200 Message-ID: <70590.954758102@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 01 Apr 2000 17:03:24 PST, Matthew Dillon wrote: > I've committed it into -current and will MFC it into > -stable in a week if there aren't any problems. I > do not intend to MFC it into 3.x. Hi Matt, I'd like to suggest that a week is not enough. Given that we seem to be back on the bleeding edge in CURRENT, a lot of folks who might be able to send valuable feedback are less likely to manage a system update within the short space of 1 week. I'm not telling you what to do. I'm just mentioning it in case you'd overlooked the fact that acceptable MFC times grew abnormally short small during the code slush and freeze. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3:55:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 29E7137BEAA for ; Mon, 3 Apr 2000 03:55:24 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12c4V0-000ISq-00; Mon, 03 Apr 2000 12:54:26 +0200 From: Sheldon Hearn To: Nick Hibma Cc: Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-reply-to: Your message of "Mon, 03 Apr 2000 10:52:13 +0100." Date: Mon, 03 Apr 2000 12:54:26 +0200 Message-ID: <70979.954759266@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 03 Apr 2000 10:52:13 +0100, Nick Hibma wrote: > Are there actually any good reasons why we _should_ upgrade in the first > place? Security fixes, added functionality we require, etc. The perl we > have is stable and the problems it has are well known, which is good > enough in 99% of the cases. The only significant reason to upgrade (as far as I'm concerned) is for the updated base modules, many of which provide fixes and features that modern perl5 scripts rely on. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 3:56:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 76AFF37BF2F for ; Mon, 3 Apr 2000 03:56:07 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12c4WH-000ITJ-00; Mon, 03 Apr 2000 12:55:45 +0200 From: Sheldon Hearn To: Chuck Robey Cc: "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-reply-to: Your message of "Sun, 02 Apr 2000 17:56:22 -0400." Date: Mon, 03 Apr 2000 12:55:45 +0200 Message-ID: <71008.954759345@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 02 Apr 2000 17:56:22 -0400, Chuck Robey wrote: > Hmm. What with the nightmarish build structure of perl, I'm sure that > reading this is just going to wreck Mark's day. I doubt it. Not for a while, anyway. Mark and I chatted about the state of the mailing lists over drinks last Friday, and he and I are both pretty bad with keeping up to date on our -current mail. Anyone who'd like to help Mark with this should really mail him directly. Caio, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 4:57:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fuggle.veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id CFA0B37BF42 for ; Mon, 3 Apr 2000 04:57:18 -0700 (PDT) (envelope-from veldy@fuggle.veldy.net) Received: by fuggle.veldy.net (Postfix, from userid 1000) id 342C21948; Mon, 3 Apr 2000 07:01:10 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id 258A4193E; Mon, 3 Apr 2000 07:01:10 -0500 (CDT) Date: Mon, 3 Apr 2000 07:01:10 -0500 (CDT) From: "Thomas T. Veldhouse" To: Nick Hibma Cc: Christopher Masto , Chuck Robey , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have no real reason for including its functionality - I am as of yet - pretty much a perl novice. However, judging by the past, the C compiler upgrade is done in current - and I would think the perl upgrade would also be done in current. I would think you would want to track this sort of thing as closely as possible - unless there is an pending release - which there isn't. Users will follow current to get the latest and greatest - bleeding edge technology. Help test it. Seem to me the sooner it is done, the more thoroughly tested it will be. One year ought to be long enough :) Tom Veldhouse veldy@veldy.net On Mon, 3 Apr 2000, Nick Hibma wrote: > > Are there actually any good reasons why we _should_ upgrade in the first > place? Security fixes, added functionality we require, etc. The perl we > have is stable and the problems it has are well known, which is good > enough in 99% of the cases. > > Including Perl in the make world build is something entirely different > from doing a make install /usr/ports, I'm sure. > > Nick > > > > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > > > plans for using it currently, but I curious. > > > > > > Hmm. What with the nightmarish build structure of perl, I'm sure that > > > reading this is just going to wreck Mark's day. In light of that, and in > > > the absence of both any real software that needs the upgrade, and > > > lack of confidence in a really squeaky new release, why don't we all grant > > > Mark a little slack on this, at least for a while. > > > > I've been running Perl 5 since before it was included with FreeBSD, and > > I've never noticed anything nightmarish about the build process. I > > tried 5.6 a couple of days ago, and it built and tested out of the > > box. > > -- > > Christopher Masto Senior Network Monkey NetMonger Communications > > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > n_hibma@webweaving.org > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 4:59:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id ED2E837BD81 for ; Mon, 3 Apr 2000 04:59:08 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 1EC0FDADA; Mon, 3 Apr 2000 13:58:50 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200004030410.XAA75906@celery.dragondata.com> References: <200004030410.XAA75906@celery.dragondata.com> Date: Mon, 3 Apr 2000 12:56:12 +0200 To: Kevin Day , dillon@apollo.backplane.com (Matthew Dillon) From: Brad Knowles Subject: Re: Load average calculation? Cc: toasty@dragondata.com (Kevin Day), current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:10 PM -0500 2000/4/2, Kevin Day wrote: > It's probably more accurate, but from a PR standpoint it makes it "look" > like FreeBSD is choking under the load, when it really isn't. Or am I the > only one that even cares about this? :) It's also extremely confusing for Linux users/admins who are used to the system rolling over and dying if the load average ever gets over 2.0 (and panic'ing if the load average goes over 4.0), and who see FreeBSD capable of surviving (if not necessarily performing very well) with load averages as high as 100 or even 200. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 5: 0: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 0BAD337B9D7 for ; Mon, 3 Apr 2000 04:59:56 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id MAA34741; Mon, 3 Apr 2000 12:59:19 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id MAA02751; Mon, 3 Apr 2000 12:59:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004031159.MAA02751@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Takahashi Yoshihiro Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Please review newbus patch for amd and adv In-Reply-To: Message from Takahashi Yoshihiro of "Sun, 02 Apr 2000 23:05:32 +0900." <20000402230532V.nyan@dd.catv.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 12:59:14 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I converted the amd and adv drivers to new-bus. But, as I am not > familiar with these drivers and new-bus, maybe I have mistaken. > > Will somebody please review these changes? > > For amd driver: > http://home.jp.FreeBSD.org/~nyan/patches/amd.diff.gz Hi, I'm afraid this code fails in bus_alloc_resource(...SYS_RES_IOPORT...). I know nothing about what that does, but notice that the old code didn't even call pci_map_port() (which makes the compat code call bus_alloc_resource)... I also added these patches - possibly worth leaving in the final version of this code ? Let me know if you need any more data here.... Cheers. -- Brian Don't _EVER_ lose your sense of humour ! --- amd.c.orig Mon Apr 3 12:20:52 2000 +++ amd.c Mon Apr 3 12:42:11 2000 @@ -2256,8 +2256,11 @@ iores = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0, ~0, 1, RF_ACTIVE); - if (iores == NULL) + if (iores == NULL) { + if (bootverbose) + printf("amd_init: bus_alloc_resource failure!\n"); return ENXIO; + } amd->tag = rman_get_bustag(iores); amd->bsh = rman_get_bushandle(iores); @@ -2271,6 +2274,8 @@ /*maxsegsz*/AMD_MAXTRANSFER_SIZE, /*flags*/BUS_DMA_ALLOCNOW, &amd->buffer_dmat) != 0) { + if (bootverbose) + printf("amd_init: bus_dma_tag_create failure!\n"); return ENXIO; } TAILQ_INIT(&amd->free_srbs); @@ -2355,8 +2360,11 @@ void *ih; struct resource *irqres; - if (amd_init(dev)) + if (amd_init(dev)) { + if (bootverbose) + printf("amd_attach: amd_init failure!\n"); return ENXIO; + } /* Reset Pending INT */ intstat = amd_read8(amd, INTSTATREG); @@ -2379,19 +2387,26 @@ * max_sim_transactions */ devq = cam_simq_alloc(MAX_START_JOB); - if (devq == NULL) + if (devq == NULL) { + if (bootverbose) + printf("amd_attach: cam_simq_alloc failure!\n"); return ENXIO; + } amd->psim = cam_sim_alloc(amd_action, amd_poll, "amd", amd, amd->unit, 1, MAX_TAGS_CMD_QUEUE, devq); if (amd->psim == NULL) { cam_simq_free(devq); + if (bootverbose) + printf("amd_attach: cam_sim_alloc failure!\n"); return ENXIO; } if (xpt_bus_register(amd->psim, 0) != CAM_SUCCESS) { cam_sim_free(amd->psim, /*free_devq*/TRUE); + if (bootverbose) + printf("amd_attach: xpt_bus_register failure!\n"); return ENXIO; } @@ -2400,6 +2415,8 @@ CAM_LUN_WILDCARD) != CAM_REQ_CMP) { xpt_bus_deregister(cam_sim_path(amd->psim)); cam_sim_free(amd->psim, /* free_simq */ TRUE); + if (bootverbose) + printf("amd_attach: xpt_create_path failure!\n"); return ENXIO; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 5: 9:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 1C0A537B980 for ; Mon, 3 Apr 2000 05:09:51 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id IAA61083; Mon, 3 Apr 2000 08:09:52 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Mon, 3 Apr 2000 08:09:52 -0400 (EDT) From: Chuck Robey To: Christopher Masto Cc: "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: <20000403024241.A13365@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Christopher Masto wrote: > On Sun, Apr 02, 2000 at 05:56:22PM -0400, Chuck Robey wrote: > > On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > > > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > > plans for using it currently, but I curious. > > > > Hmm. What with the nightmarish build structure of perl, I'm sure that > > reading this is just going to wreck Mark's day. In light of that, and in > > the absence of both any real software that needs the upgrade, and > > lack of confidence in a really squeaky new release, why don't we all grant > > Mark a little slack on this, at least for a while. > > I've been running Perl 5 since before it was included with FreeBSD, and > I've never noticed anything nightmarish about the build process. I > tried 5.6 a couple of days ago, and it built and tested out of the > box. It's the way that perl builds itself. Isn't perl the only thing we build that *doesn't* use make alone to guide the build process? Isn't perl the only thing in the tree that uses itself to build it's manpages? Have you looked at the make files for perl, say the one in gnu/usr.bin/perl/perl? It works *real* slickly, but it sure wouldn't have been easy to piece together. Maybe you misinterpreted what I said to mean "the build is screwed up". I think the job done was great, but I wouldn't want to get the job of modifying it, say moving it's local library location. > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 5:28:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B569137BBE3 for ; Mon, 3 Apr 2000 05:28:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id OAA20939 for ; Mon, 3 Apr 2000 14:28:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: 2nd call for reviews and tests: buf->bio patch From: Poul-Henning Kamp Date: Mon, 03 Apr 2000 14:28:38 +0200 Message-ID: <20937.954764918@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://phk.freebsd.dk/misc I belive the patch is now fundamentally ready for commit, I'm running it here myself, and the delta in kernel warnings have been analyzed and deemed mostly harmless. Some componenents are still not converted and use a cast from bio to buf, prominently vinum and ccd, but they should work all the same anyway. Poul-Henning To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 5:29:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id D07A037B9D7 for ; Mon, 3 Apr 2000 05:29:21 -0700 (PDT) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id OAA32271; Mon, 3 Apr 2000 14:30:09 +0200 (CEST) (envelope-from tobez) Date: Mon, 3 Apr 2000 14:30:09 +0200 From: Anton Berezin To: "Thomas T. Veldhouse" Cc: Nick Hibma , Christopher Masto , Chuck Robey , FreeBSD-Current Subject: Re: Perl 5.6.0? Message-ID: <20000403143009.C31459@plab.ku.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from veldy@fuggle.veldy.net on Mon, Apr 03, 2000 at 07:01:10AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 07:01:10AM -0500, Thomas T. Veldhouse wrote: > I would think the perl upgrade would also be done in current. I would > think you would want to track this sort of thing as closely as > possible - unless there is an pending release - which there isn't. > Users will follow current to get the latest and greatest - bleeding > edge technology. Everybody who wants to have the bleeding edge Perl on their systems is welcome to install it himself. 5.6.0 builds out of the box and passes its regression test suit just fine on 2.2.X, 3.X, 4.X, and 5.0. > Help test it. Seem to me the sooner it is done, the more thoroughly > tested it will be. One year ought to be long enough :) Historical evidence suggests there will be 5.6.1 *very* soon, and 5.6.2 shortly after that. Let's wait a couple of months before jumping on this vagon... :-) 5.6.0 will almost surely prove to have far too many problems to include it into FreeBSD source tree. Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 5:53:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 0E60637BE72; Mon, 3 Apr 2000 05:53:29 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 3B111DCBD; Mon, 3 Apr 2000 14:53:03 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Mon, 3 Apr 2000 14:52:31 +0200 To: FreeBSD-CURRENT Mailing List From: Brad Knowles Subject: Sysctl for CAM SCSI quirks? Cc: freebsd-scsi@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I just did a bit of searching on the website, and garnered enough information from to be able to add a new "quirk" in /usr/src/sys/cam/cam_xpt.c for a piece of hardware I'm having some difficulty with. Assuming this works, I will file a proper PR, etc.... However, shouldn't there be an easier way to do this? For example, shouldn't there be a sysctl for changing these sorts of things, perhaps something like: kern.cam.cd.changer.min_busy_seconds: 5 kern.cam.cd.changer.max_busy_seconds: 15 kern.cam.quirks.direct.fixed.quantum.XP39100*.*.mintags: 24 kern.cam.quirks.direct.fixed.quantum.XP39100*.*.maxtags: 32 kern.cam.quirks.direct.fixed.quantum.XP34550*.*.mintags: 24 kern.cam.quirks.direct.fixed.quantum.XP34550*.*.maxtags: 32 kern.cam.quirks.direct.fixed.quantum.XP32275*.*.mintags: 24 kern.cam.quirks.direct.fixed.quantum.XP32275*.*.maxtags: 32 This would make it very easy to add new quirks as they come along (just update your sysctl.conf), and without having to always file a PR so that /usr/src/sys/cam/cam_xpt.c gets modified so that you can have your quirk and track -CURRENT too (or -STABLE, for that matter). -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 6:18: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 9DB2137BD20 for ; Mon, 3 Apr 2000 06:18:00 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 23327 invoked from network); 3 Apr 2000 13:17:53 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 3 Apr 2000 13:17:53 -0000 Date: Mon, 3 Apr 2000 23:17:34 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: <200004021700.TAA01074@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2 Apr 2000, Gary Jennejohn wrote: > Bruce Evans writes: > >Big structs need to be malloced. > > Yes, but how does one know that a struct is too big ? Before the increase > in MLEN strucct sppp was not too big. All structs should be considered too big until proven otherwise :-). > >I think removing the unused bloat in `struct cstate' is the correct fix > >for this particular allocation. > > > > I think we should nuke csu_hdr since it's not used anywhere. Is that > what you really mean ? Yes. I'm trying the following patch. Only tested at compile time. diff -c2 slcompress.h~ slcompress.h *** slcompress.h~ Sun Aug 29 13:15:00 1999 --- slcompress.h Sun Apr 2 21:53:35 2000 *************** *** 41,46 **** #define _NET_SLCOMPRESS_H_ ! #define MAX_STATES 16 /* must be > 2 and < 256 */ ! #define MAX_HDR MLEN /* XXX 4bsd-ism: should really be 128 */ /* --- 41,46 ---- #define _NET_SLCOMPRESS_H_ ! #define MAX_STATES 16 /* must be > 2 and < 256 */ ! #define MAX_HDR 128 /* *************** *** 120,130 **** u_char cs_id; /* connection # associated with this state */ u_char cs_filler; ! union { ! char csu_hdr[MAX_HDR]; ! struct ip csu_ip; /* ip/tcp hdr from most recent packet */ ! } slcs_u; }; - #define cs_ip slcs_u.csu_ip - #define cs_hdr slcs_u.csu_hdr /* --- 120,125 ---- u_char cs_id; /* connection # associated with this state */ u_char cs_filler; ! struct ip cs_ip; /* ip/tcp hdr from most recent packet */ }; /* Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 6:18:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id D09A637BFB1 for ; Mon, 3 Apr 2000 06:18:04 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1946 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Mon, 3 Apr 2000 15:17:47 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 4F48238FA; Mon, 3 Apr 2000 15:17:57 +0200 (METDST) Subject: Re: MLEN and crashes In-Reply-To: <19865.954756081@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 3, 0 12:01:21 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 3 Apr 2000 15:17:57 +0200 (METDST) Cc: garyj@muc.de, bright@wintelcom.net, hm@hcs.de, freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 982 Message-Id: <20000403131757.4F48238FA@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Poul-Henning Kamp: > We need to be frugal about the kernel stack, for a lot of reasons, > that's just the way it is, and as far as I know it is the way > it will continue to be. Good. I'd like to learn something from it: Shall i avoid allocating structs on the kernel stack at all or is it just bad to allocate big structs ? If the latter is true, what number is big ? I've scanned a bit through the kernel sources to find the constant which defines the length of the kernel stack but i was not able to find anything (which then could be used at compile time to detect a potentially too large struct). > Get used to it. Will do ;-) hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 6:21:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 939D337BDDB for ; Mon, 3 Apr 2000 06:21:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA21187; Mon, 3 Apr 2000 15:20:57 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: hm@hcs.de Cc: garyj@muc.de, bright@wintelcom.net, freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-reply-to: Your message of "Mon, 03 Apr 2000 15:17:57 +0200." <20000403131757.4F48238FA@hcswork.hcs.de> Date: Mon, 03 Apr 2000 15:20:57 +0200 Message-ID: <21185.954768057@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000403131757.4F48238FA@hcswork.hcs.de>, Hellmuth Michaelis writes : >>From the keyboard of Poul-Henning Kamp: > >> We need to be frugal about the kernel stack, for a lot of reasons, >> that's just the way it is, and as far as I know it is the way >> it will continue to be. > >Good. I'd like to learn something from it: Shall i avoid allocating >structs on the kernel stack at all or is it just bad to allocate >big structs ? My own rule of thumb is "about 60 bytes or so", but it also depends on the lifetime of the function. If it is a leaf function which doesn't call anything else I'll let it use more stack, if it is a function which is burried at the bottom (top really) of the stack all the time I'm less tolerant. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 6:28:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from pr.infosec.ru (pr.infosec.ru [194.135.141.98]) by hub.freebsd.org (Postfix) with ESMTP id 65A7437BC63; Mon, 3 Apr 2000 06:28:10 -0700 (PDT) (envelope-from blaze@infosec.ru) Received: from blaze (200.0.0.51 [200.0.0.51]) by pr.infosec.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id H9Z764PT; Mon, 3 Apr 2000 17:28:37 +0400 Date: Mon, 3 Apr 2000 17:27:10 +0400 (MSD) From: Andrey Sverdlichenko X-Sender: blaze@blaze To: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: hostcache Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is net/hostcache.h interface obsoleted by other or developers just don't need them? There is no uses of them in kernel sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 6:44:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8D21237BDA1 for ; Mon, 3 Apr 2000 06:44:33 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 24150 invoked from network); 3 Apr 2000 13:44:30 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 3 Apr 2000 13:44:30 -0000 Date: Mon, 3 Apr 2000 23:44:11 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Alfred Perlstein Cc: Hellmuth Michaelis , garyj@muc.de, freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: <20000403023858.F21029@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Alfred Perlstein wrote: > * Hellmuth Michaelis [000403 02:12] wrote: > > >From the keyboard of Bruce Evans: > > > > > It's just a bug to allocate big structs on the kernel stack. > > > > Please specify "big"! :-) > > have a look at src/sys/nfs/nfs_vnops.c: > > line ~2787: > #ifndef NFS_COMMITBVECSIZ > #define NFS_COMMITBVECSIZ 20 > #endif > struct buf *bvec_on_stack[NFS_COMMITBVECSIZ]; > int bvecsize = 0, bveccount; > > I guess 80 bytes is pushing it, some routines are worse, but 2k > is totally out of line. This case is an array of pointers. Big arrays are just as bad as big structs, of course. Having a parameterized array size makes it hard to prove that the size is small enough. > If you're worried about such things happening then you can use > the pre-processor to catch things that may make your structures > too large. This won't work for dynamic arrays. E.g., vm_pageout_flush() uses "int pageout_status[count];". It is not immediately obvious that count < vm_pageout_page_count where vm_pageout_page_count is either 8 or VM_PAGEOUT_PAGE_COUNT = 16. Using a constant array size of VM_PAGEOUT_PAGE_COUNT would be simpler, faster, and wouldn't break K&R support. objdump(1) can be used to find struct sizes. E.g., "objdump --stabs kernel.debug | grep cstate" gives: 18052 LCSYM 0 120 c02b7a00 208921 escstate:V(0,1) 129365 LSYM 0 0 00000000 1929789 cstate:T(55,1)=s244cs_next:(55,2)=*(55,1),0,32;cs_hlen:(7,8),32,16;cs_id:(7,1),48,8;cs_filler:(7,1),56,8;slcs_u:(55,3)=u236csu_hdr:(35,14),0,1888;csu_ip:(54,1),0,160;;,64,1888;; This shows that the last struct member has size 64 bits and offset 1888 bits. The struct size is usually the sum of the last member offset and size. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 7:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 03E7937BE01 for ; Mon, 3 Apr 2000 07:33:50 -0700 (PDT) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id XAA04533; Mon, 3 Apr 2000 23:32:49 +0900 (JST) To: imp@village.org Cc: current@FreeBSD.ORG Subject: Re: Please review newbus patch for amd and adv In-Reply-To: <200004030613.AAA59095@harmony.village.org> References: <20000402230532V.nyan@dd.catv.ne.jp> <200004030103.TAA56398@harmony.village.org> <200004030613.AAA59095@harmony.village.org> From: Takahashi Yoshihiro X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000403233326V.nyan@dd.catv.ne.jp> Date: Mon, 03 Apr 2000 23:33:26 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200004030613.AAA59095@harmony.village.org> Warner Losh writes: > In message <20000403150908J.nyan@wyvern.cc.kogakuin.ac.jp> Takahashi Yoshihiro writes: > : Because, adv_isa.c is not required by PC-98, PC-98 requires only PCI > : frontend. Then it contains isa_dmacascade function which does not > : exist and is not needed for PC-98. > > Is that because there's not isa bus on a pc-98? Or that the adv_isa > cannot possibly work on the ISA bus that is in a pc-98? If there's no > isa on the pc98, then config should take care of not including it. So > I'm a little confused here. There is not ISA bus on PC-98. So, we can't use devices for ISA bus on PC-98. But, PC-98 has `Cbus' which is like ISA bus in software place. As most codes for ISA bus are useful for Cbus, the code for Cbus is based on the code for ISA bus. --- Takahashi Yoshihiro The Center for Information Science, Kogakuin Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 7:35:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs0.catv.ne.jp (cs0.catv.ne.jp [202.232.171.20]) by hub.freebsd.org (Postfix) with ESMTP id B771C37BD3C for ; Mon, 3 Apr 2000 07:35:43 -0700 (PDT) (envelope-from nyan@dd.catv.ne.jp) Received: from localhost by cs0.catv.ne.jp (8.9.1/3.7W) id XAA04695; Mon, 3 Apr 2000 23:33:22 +0900 (JST) In-Reply-To: <200004031159.MAA02751@hak.lan.Awfulhak.org> References: <200004031159.MAA02751@hak.lan.Awfulhak.org> Subject: Re: Please review newbus patch for amd and adv From: Takahashi Yoshihiro To: brian@Awfulhak.org Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000403233402K.nyan@dd.catv.ne.jp> Date: Mon, 03 Apr 2000 23:34:02 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200004031159.MAA02751@hak.lan.Awfulhak.org> Brian Somers writes: > I'm afraid this code fails in bus_alloc_resource(...SYS_RES_IOPORT...). > I know nothing about what that does, but notice that the old code > didn't even call pci_map_port() (which makes the compat code call > bus_alloc_resource)... > > I also added these patches - possibly worth leaving in the final > version of this code ? Your patches report more information if there is error. I agree to contain your patches. Thank you. --- Takahashi Yoshihiro The Center for Information Science, Kogakuin Univ. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 7:46:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by hub.freebsd.org (Postfix) with ESMTP id 0C17237BE1A for ; Mon, 3 Apr 2000 07:46:19 -0700 (PDT) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-02-160.nv.iinet.net.au [203.59.91.160]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id WAA26802; Mon, 3 Apr 2000 22:44:35 +0800 Message-ID: <38E8ADEC.794BDF32@elischer.org> Date: Mon, 03 Apr 2000 07:42:52 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: hm@hcs.de Cc: Poul-Henning Kamp , garyj@muc.de, bright@wintelcom.net, freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes References: <20000403131757.4F48238FA@hcswork.hcs.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hellmuth Michaelis wrote: > > >From the keyboard of Poul-Henning Kamp: > > > We need to be frugal about the kernel stack, for a lot of reasons, > > that's just the way it is, and as far as I know it is the way > > it will continue to be. > > Good. I'd like to learn something from it: Shall i avoid allocating > structs on the kernel stack at all or is it just bad to allocate > big structs ? If the latter is true, what number is big > The best rule is never allocate anything bigger than a few elements. One reason to not allocate struct on the stack is that under some OS's (e.g. originally freebsd too) the stack could have been 'unmapped' while the that process was not in core, tus access toteh struct by an interrupt routine or something could be 'bad'. In FreeBSD this is presently not the case but.. Also, when we switch to ASYNC IO as a normal means of operation, the stack may sometimes be rewound before the IO is completed, which might also be considered "not a good thing" (TM). > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 8: 0:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 522C937B68B for ; Mon, 3 Apr 2000 08:00:34 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id KAA22254 for ; Mon, 3 Apr 2000 10:59:56 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/) id HAA00414; Mon, 3 Apr 2000 07:59:53 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Apr 2000 07:59:53 -0700 (PDT) Message-Id: <200004031459.HAA00414@ix.netcom.com> From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Top, vmstat, systat, etc. Broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Apr 3 06:49:43 PDT 2000 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 cvsup'ed April 2 at 1230, make world April 2 2200. I think I missed something. Several things in /usr/bin are broken. # top top: nlist failed # ls -l `which top` -r-xr-sr-x 1 root kmem 32016 Apr 2 22:36 /usr/bin/top* # ldconfig -r | grep -i kvm 25:-lkvm.2 => /usr/lib/libkvm.so.2 # ls -l /usr/lib/libkvm.so.2 -r--r--r-- 1 root wheel 18164 Apr 2 22:21 /usr/lib/libkvm.so.2 # vmstat vmstat: undefined symbols: _kmemstatistics _bucket _zlist # systat systat: nlist: can't find following symbols: _ccpu _fscale tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 8: 1:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id EA00F37BED0 for ; Mon, 3 Apr 2000 08:01:20 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id QAA49076; Mon, 3 Apr 2000 16:59:25 +0200 (CEST) Message-Id: <200004031459.QAA49076@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 03 Apr 2000 15:18:03 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 16:59:25 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: >On Sun, 2 Apr 2000, Gary Jennejohn wrote: >> I think we should nuke csu_hdr since it's not used anywhere. Is that >> what you really mean ? > >Yes. I'm trying the following patch. Only tested at compile time. > [patch snipped] Thank you, Bruce ! This is pretty much the same patch I tested. So, should I commit it ? --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 8: 4:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B64A37B9D7; Mon, 3 Apr 2000 08:04:52 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA29053; Mon, 3 Apr 2000 08:03:06 -0700 Date: Mon, 3 Apr 2000 08:03:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Brad Knowles Cc: FreeBSD-CURRENT Mailing List , freebsd-scsi@FreeBSD.ORG Subject: Re: Sysctl for CAM SCSI quirks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG These aren't available at boot time when you need them, are they? On Mon, 3 Apr 2000, Brad Knowles wrote: > Folks, > > I just did a bit of searching on the website, and garnered enough > information from > b/text/1998/freebsd-questions/19981115.freebsd-questions> to be able > to add a new "quirk" in /usr/src/sys/cam/cam_xpt.c for a piece of > hardware I'm having some difficulty with. > > Assuming this works, I will file a proper PR, etc.... > > > However, shouldn't there be an easier way to do this? For > example, shouldn't there be a sysctl for changing these sorts of > things, perhaps something like: > > kern.cam.cd.changer.min_busy_seconds: 5 > kern.cam.cd.changer.max_busy_seconds: 15 > kern.cam.quirks.direct.fixed.quantum.XP39100*.*.mintags: 24 > kern.cam.quirks.direct.fixed.quantum.XP39100*.*.maxtags: 32 > kern.cam.quirks.direct.fixed.quantum.XP34550*.*.mintags: 24 > kern.cam.quirks.direct.fixed.quantum.XP34550*.*.maxtags: 32 > kern.cam.quirks.direct.fixed.quantum.XP32275*.*.mintags: 24 > kern.cam.quirks.direct.fixed.quantum.XP32275*.*.maxtags: 32 > > This would make it very easy to add new quirks as they come along > (just update your sysctl.conf), and without having to always file a > PR so that /usr/src/sys/cam/cam_xpt.c gets modified so that you can > have your quirk and track -CURRENT too (or -STABLE, for that matter). > > -- > These are my opinions -- not to be taken as official Skynet policy > ====================================================================== > Brad Knowles, || Belgacom Skynet SA/NV > Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 > Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels > http://www.skynet.be || Belgium > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 8:26:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id B371D37BEFD for ; Mon, 3 Apr 2000 08:26:24 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id IAA93336 for ; Mon, 3 Apr 2000 08:26:21 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id IAA37084 for freebsd-current@freebsd.org; Mon, 3 Apr 2000 08:26:20 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200004031526.IAA37084@realtime.exit.com> Subject: Re: MLEN and crashes In-Reply-To: <19865.954756081@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 3, 2000 12:01:21 pm" To: Poul-Henning Kamp Date: Mon, 3 Apr 2000 08:20:08 -0700 (PDT) Cc: Gary Jennejohn , Alfred Perlstein , Hellmuth Michaelis , freebsd-current@FreeBSD.ORGG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <200004030935.LAA48677@peedub.muc.de>, Gary Jennejohn writes: > > >Yes, but it was perfectly legal to put the structure on the stack > >_before_ MLEN was doubled. > > Just because it worked doesn't mean that it was correct. > > We need to be frugal about the kernel stack, for a lot of reasons, > that's just the way it is, and as far as I know it is the way > it will continue to be. To be a little less harsh about it (Poul, you could _really_ stand to work on your phrasing, this sounded unnecessarily harsh), kernel stack space is (in pretty much any kernel -- the one I work on is Unixware 7) a very scarce resource. You can put variables on the stack, but even that can make it run out for really long path lengths. If you have a structure or an array, the rule of thumb is to _always_ malloc it. This will save your bacon when the structure grows (as in this case) or the path gets a little longer, or something else happens that makes you run out of kernel stack. This is the way it is in kernel land. I won't say "get used to it," that's unnecessarily harsh, but it _is_ the way it is. Read, learn, evolve, as they say in talk.bizarre. And become a better kernel programmer thereby. -- Frank Mayhar frank@exit.com http://www.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 8:59:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id F030237BDD9 for ; Mon, 3 Apr 2000 08:59:38 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (intefix.ai [209.88.68.216]) by cypherpunks.ai (Postfix) with ESMTP id 2214549; Mon, 3 Apr 2000 11:59:35 -0400 (AST) Message-ID: <38E8BFD5.3E69DF2A@vangelderen.org> Date: Mon, 03 Apr 2000 11:59:17 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Hibma Cc: Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > Are there actually any good reasons why we _should_ upgrade in the first > place? Security fixes, added functionality we require, etc. The perl we > have is stable and the problems it has are well known, which is good > enough in 99% of the cases. PERL is not just used by the FreeBSD system, it's also used by many applications ran on top of FreeBSD. Those applications are more likely to require an up-to-date version of PERL. We for one need the (overly late) 64-bit support in PERL. You could of course force users to install the latest PERL locally and fiddle with $PATH but this would amount to hacking around a deficiency in FreeBSD. If FreeBSD needs an older version of PERL for it's own use, it should provide something like 'perl_freebsd' or 'system_perl' so that 'perl' can always be up2date. Later Anton Berezin wrote: > Historical evidence suggests there will be 5.6.1 *very* soon, and 5.6.2 > shortly after that. Let's wait a couple of months before jumping on > this vagon... :-) 5.6.0 will almost surely prove to have far too many > problems to include it into FreeBSD source tree. Problems in a dot-zero release are a very good argument against importing PERL 5.6.0 now. Of course it would be even better to just import PERL4 again and force everybody to use Python, but that's another religious war ;-/ Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:22:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7130F37B60A for ; Mon, 3 Apr 2000 09:22:14 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA15454; Mon, 3 Apr 2000 09:22:13 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA19715; Mon, 3 Apr 2000 09:22:09 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 3 Apr 2000 09:22:09 -0700 (PDT) Message-Id: <200004031622.JAA19715@vashon.polstra.com> To: bright@wintelcom.net Subject: Re: MLEN and crashes In-Reply-To: <20000403023858.F21029@fw.wintelcom.net> References: <20000403084330.6A6DC483D@hcswork.hcs.de> <20000403023858.F21029@fw.wintelcom.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000403023858.F21029@fw.wintelcom.net>, Alfred Perlstein wrote: > > If you're worried about such things happening then you can use > the pre-processor to catch things that may make your structures > too large. > > > I wonder how too "big" can be detected. The code in question is perfectly > > valid syntactically and semantically correct C-code. > > There's code that #error (maybe #warning?) when it can detect that the > size of a struct has been unreasonably grown, it's done via the > pre-processor. I doubt if it's possible to implement that at compile time. Remember, the preprocessor doesn't understand "sizeof". It doesn't recognize keywords in expressions at all. John -- John Polstra jdp@polstra.com 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-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:36: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 4AF0C37BB7B for ; Mon, 3 Apr 2000 09:35:53 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 1D3B719078; Mon, 3 Apr 2000 18:34:23 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 78F43412; Mon, 3 Apr 2000 18:34:19 +0200 (CEST) Date: Mon, 3 Apr 2000 18:34:18 +0200 To: John Polstra Cc: bright@wintelcom.net, current@freebsd.org Subject: Re: MLEN and crashes References: <20000403084330.6A6DC483D@hcswork.hcs.de> <20000403023858.F21029@fw.wintelcom.net> <200004031622.JAA19715@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004031622.JAA19715@vashon.polstra.com>; from jdp@polstra.com on Mon, Apr 03, 2000 at 09:22:09AM -0700 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-04-03-18-34-19+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3/04, John Polstra wrote: | I doubt if it's possible to implement that at compile time. Remember, | the preprocessor doesn't understand "sizeof". It doesn't recognize | keywords in expressions at all. Then don't use the preprocessor alone and use both the preprocessor and the compiler. I suppose something like this will work: struct foobar { ...; } #ifdef CHECK_STRUCT_SIZE #define MAX_FOOBAR_SIZE 8 static char dummy_foobar [MAX_FOOBAR_SIZE-sizeof(struct foobar)]; #undef MAX_FOOBAR_SIZE #endif If sizeof(struct foobar) is more than MAX_FOOBAR_SIZE, then the compiler will try to create an array with a negative size, which will not compile. Embed this in a macro and you're done: #ifdef CHECK_STRUCT_SIZE #define CSS(S,T,U) static char dummy_##T [U-sizeof(S)]; #else #define CSS(S,T,U) #endif Then use: CSS(struct foobar,foobar,8) Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:38:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8DF0937BB7B for ; Mon, 3 Apr 2000 09:38:25 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA59197; Mon, 3 Apr 2000 09:35:57 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 09:35:57 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031635.JAA59197@apollo.backplane.com> To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues References: <70590.954758102@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : : :On Sat, 01 Apr 2000 17:03:24 PST, Matthew Dillon wrote: : :> I've committed it into -current and will MFC it into :> -stable in a week if there aren't any problems. I :> do not intend to MFC it into 3.x. : :Hi Matt, : :I'd like to suggest that a week is not enough. Given that we seem to be :back on the bleeding edge in CURRENT, a lot of folks who might be able :to send valuable feedback are less likely to manage a system update :within the short space of 1 week. : -stable (4.x) is operating under different rules at the moment due to the theoretical BSDI code merge in -current. People are allowed to commit new work. However, in this particular instance the I/O performance fix was really nothing more then a simple bug fix, so it would be MFC'd quickly in any case. :Ciao, :Sheldon. : -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:38:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A01DF37B8B3 for ; Mon, 3 Apr 2000 09:38:43 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA14574; Mon, 3 Apr 2000 12:36:29 -0400 (EDT) (envelope-from wollman) Date: Mon, 3 Apr 2000 12:36:29 -0400 (EDT) From: Garrett Wollman Message-Id: <200004031636.MAA14574@khavrinen.lcs.mit.edu> To: Kevin Day Cc: dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG Subject: Re: Load average calculation? In-Reply-To: <200004030410.XAA75906@celery.dragondata.com> References: <200004030349.UAA52843@apollo.backplane.com> <200004030410.XAA75906@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > It's probably more accurate, but from a PR standpoint it makes it "look" > like FreeBSD is choking under the load, when it really isn't. Actually, you have it backwards -- it makes it look as if FreeBSD is *not* choking under what appears to be a very heavy load.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:39:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 27B8237B8B3 for ; Mon, 3 Apr 2000 09:39:20 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA14580; Mon, 3 Apr 2000 12:37:16 -0400 (EDT) (envelope-from wollman) Date: Mon, 3 Apr 2000 12:37:16 -0400 (EDT) From: Garrett Wollman Message-Id: <200004031637.MAA14580@khavrinen.lcs.mit.edu> To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Summer/winter time problems with daily/460 In-Reply-To: <20000402150817.C21619@daemon.ninth-circle.org> References: <20000402150817.C21619@daemon.ninth-circle.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Someone more acquainted with the daily scripts may want to > investigate/fix that. In the general case, it's hopeless. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 9:49:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 0BBA037B54F for ; Mon, 3 Apr 2000 09:49:36 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id LAA77005; Mon, 3 Apr 2000 11:48:23 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200004031648.LAA77005@celery.dragondata.com> Subject: Re: Load average calculation? To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Mon, 3 Apr 2000 11:48:22 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), dillon@apollo.backplane.com (Matthew Dillon), current@FreeBSD.ORG In-Reply-To: <200004031636.MAA14574@khavrinen.lcs.mit.edu> from "Garrett Wollman" at Apr 03, 2000 12:36:29 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > < said: > > > It's probably more accurate, but from a PR standpoint it makes it "look" > > like FreeBSD is choking under the load, when it really isn't. > > Actually, you have it backwards -- it makes it look as if FreeBSD is > *not* choking under what appears to be a very heavy load.... > > -GAWollman > Well, my first impression was "Well, before doing this task the load average was only 0.20, now it's 4.0, obviously it can't keep up now." Which could probably be extended to "Under Linux the load average for running my database is only 0.20, FreeBSD's is 4.0, Linux must be faster." Granted it's flawed logic, but it's all a matter of perception at times. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10: 0:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 30C2537BAFE for ; Mon, 3 Apr 2000 10:00:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA59566; Mon, 3 Apr 2000 10:00:30 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:00:30 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031700.KAA59566@apollo.backplane.com> To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Top, vmstat, systat, etc. Broken References: <200004031459.HAA00414@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It kinda looks like you've stripped your kernel binary. If you havn't, don't, certain programs need the kernel symbols to access kmem. -Matt Matthew Dillon :cvsup'ed April 2 at 1230, make world April 2 2200. : :I think I missed something. Several things in /usr/bin are broken. : :# top :top: nlist failed :# ls -l `which top` :-r-xr-sr-x 1 root kmem 32016 Apr 2 22:36 /usr/bin/top* :# ldconfig -r | grep -i kvm : 25:-lkvm.2 => /usr/lib/libkvm.so.2 :# ls -l /usr/lib/libkvm.so.2 :-r--r--r-- 1 root wheel 18164 Apr 2 22:21 /usr/lib/libkvm.so.2 : :# vmstat :vmstat: undefined symbols: : _kmemstatistics _bucket _zlist :# systat : systat: nlist: can't find following symbols: : _ccpu : _fscale : :tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 2EF8A37B6ED for ; Mon, 3 Apr 2000 10:01:15 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id NAA10274; Mon, 3 Apr 2000 13:00:55 -0400 (EDT) Message-ID: <20000403130055.A8685@netmonger.net> Date: Mon, 3 Apr 2000 13:00:55 -0400 From: Christopher Masto To: Nick Hibma Cc: Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? Mail-Followup-To: Nick Hibma , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current References: <20000403024241.A13365@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Mon, Apr 03, 2000 at 10:52:13AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 10:52:13AM +0100, Nick Hibma wrote: > Are there actually any good reasons why we _should_ upgrade in the first > place? Of course. We now have an obsolete version of Perl. That should be reason enough to upgrade. 5.6 is the first major release in over a year. It has significant new syntax that I intend to start using immediately, as will much of the rest of the Perl community. "Why haven't you upgraded yet?" is a rather traditional battle cry. I don't know whey they called it 5.6.0.. I'm dropping the .0, because it seems to inspire the usual "point-oh fear". This is not a "point-oh" release in the usual sense, and waiting for 5.6.1 would be a mistake. This message should not be construed as whining and prodding our Perl maintainer. Although I haven't looked at how it's done, I'm sure that integrating Perl with FreeBSD's build process is a difficult and tedious thing, and if I wanted it that badly, I would be offering patches. This is merely a rebuttal to the silly idea that FreeBSD should stick with an obsolete version of Perl indefinately. It needs to be updated in a timely manner, which probably means any time before the next FreeBSD release. (With allowances for going into current first, etc.). -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10: 7:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C918C37B692 for ; Mon, 3 Apr 2000 10:07:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA59737; Mon, 3 Apr 2000 10:07:40 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:07:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031707.KAA59737@apollo.backplane.com> To: Soren Schmidt Cc: vallo@matti.ee, ticso@cicely.de (Bernd Walter), freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 References: <200004030842.KAA63479@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system :> built from March 31 sources. First I used striping over two disks and :> put /usr filesystem onto it, did overnight testing and all was well. :> 2. Same system, same sources plus two same disks. Now I tried raid5 over :> four disks and failed to extract pax archive, got deadlock, not panic. :> 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I :> failed to extract pax archive, got panic. :> No softupdates. : :Same story here, but using softupdates or async mounts I can reproduce :the hang or panic in less than 60 secs.. : :Vinum with raid5 is plain broken, include INVARIANTS in the kernel :and see why... : :-Søren Hang on to that thought. As soon as this struct buf mess gets cleared up if Greg hasn't figured out where the bug is I'll throw my lot in to try to speed-up locating and fixing the problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 36FA237B88D for ; Mon, 3 Apr 2000 10:08:09 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id BDE98182A5; Mon, 3 Apr 2000 19:07:14 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <38E8BFD5.3E69DF2A@vangelderen.org> References: <38E8BFD5.3E69DF2A@vangelderen.org> Date: Mon, 3 Apr 2000 18:59:05 +0200 To: "Jeroen C. van Gelderen" , Nick Hibma From: Brad Knowles Subject: Re: Perl 5.6.0? Cc: Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:59 AM -0400 2000/4/3, Jeroen C. van Gelderen wrote: > PERL is not just used by the FreeBSD system, it's also used by many > applications ran on top of FreeBSD. Those applications are more likely > to require an up-to-date version of PERL. We for one need the (overly > late) 64-bit support in PERL. MMMkay. Try this: cd /usr/ports/lang/perl && make install This seems to me to be a much better solution, while we wait for Perl 5.6.x to stablize enough for it to actually be considered for inclusion in the FreeBSD base. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:10:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.usishealth.com (adsl-216-62-210-29.dsl.austtx.swbell.net [216.62.210.29]) by hub.freebsd.org (Postfix) with ESMTP id 3052037B760 for ; Mon, 3 Apr 2000 10:10:34 -0700 (PDT) (envelope-from erik@usishealth.com) Received: from usishealth.com (gargamel [192.168.1.2]) by ns.usishealth.com (Postfix) with ESMTP id F20F31AE86 for ; Mon, 3 Apr 2000 12:15:39 -0500 (CDT) Message-ID: <38E8DF04.7BCC5EBE@usishealth.com> Date: Mon, 03 Apr 2000 13:12:20 -0500 From: Erik de Zeeuw X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: HighPoint UDMA66 ICRC READ ERROR Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi to all the -current people, I'm running FreeBSD on an Abit BP6 motherboard, which uses the HighPoint UDMA 66 controller. This is a SMP machine, with the BP6 running two Celeron 500Mhz. The hard drive is a Western Digital 7200rpm/DMA66, plugged in the HPT66 controller. Here's what dmesg tells me : ... atapci1: port \ 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 \ irq 11 at device 19.0 on pci0 ata2: at 0xb000 on atapci1 atapci2: port \ 0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07 \ irq 11 at device 19.1 on pci0 ... ad4: 19574MB [39770/16/63] at ata2-master using UDMA66 ... I'm pretty satisfied with this, especially with the great support for the DMA66 controller. The only thing is I sometimes get messages like this : gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39566319 retrying gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39627167 retrying gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39628463 retrying If I'm not wrong, this has already been discussed a while ago, that such messages could show up using a -CURRENT 4.0, and that there was nothing to worry about. As I upgraded to 4.0-RELEASE since, I just wanted to make sure that there's still nothing to worry about or if this could come from a hard disk problem. Note that although getting such messages, everything seems to work great, and all the disk operations which makes the messages occurs seems to be done perfectly ( say I'm making a huge .tar.gz, which makes the messages show up, the .tar.gz is ok, not event the shadow of the tail of a CRC error in it ). I know this could have been sent to -questions, but I remind this has been discussed here, and I think the people in charge for that kind of obscure behavior might be found around -current :) Anyway, thanks for the great work, FreeBSD really is a great OS. Erik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:15:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C12CA37B88D; Mon, 3 Apr 2000 10:15:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA59798; Mon, 3 Apr 2000 10:15:20 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:15:20 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031715.KAA59798@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch References: <20937.954764918@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : http://phk.freebsd.dk/misc : :I belive the patch is now fundamentally ready for commit, I'm running :it here myself, and the delta in kernel warnings have been analyzed :and deemed mostly harmless. : :Some componenents are still not converted and use a cast from bio to :buf, prominently vinum and ccd, but they should work all the same :anyway. : :Poul-Henning Ripping up the buffer cache right smack in the middle of Greg trying to debug a serious vinum/bio problem is atrocious timing. I have no words to describe how following that up with even more commits, despite the complaints, should be categorized. I don't understand while you haven't backed these commits out and I doubly do not understand why you continue to make further commits. And this isn't even counting the fact that you've done all of this without word-1 to group discussion-wise. I'm all for separating the I/O from the buffer cache, but forcing it into the tree as a done-deal when two other people are also actively working in the VFS/BIO subsystem is unjustifiable (in the extreme). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:21: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1141037B54F for ; Mon, 3 Apr 2000 10:20:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA22317; Mon, 3 Apr 2000 19:20:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch In-reply-to: Your message of "Mon, 03 Apr 2000 10:15:20 PDT." <200004031715.KAA59798@apollo.backplane.com> Date: Mon, 03 Apr 2000 19:20:44 +0200 Message-ID: <22315.954782444@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004031715.KAA59798@apollo.backplane.com>, Matthew Dillon writes: > >: http://phk.freebsd.dk/misc >: >:I belive the patch is now fundamentally ready for commit, I'm running >:it here myself, and the delta in kernel warnings have been analyzed >:and deemed mostly harmless. >: >:Some componenents are still not converted and use a cast from bio to >:buf, prominently vinum and ccd, but they should work all the same >:anyway. >: >:Poul-Henning > > Ripping up the buffer cache right smack in the middle of Greg trying > to debug a serious vinum/bio problem is atrocious timing. Actually, it is the other way around, Greg finally started to look for the bug in vinum in the middle of my commits. How dare he do that ? :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:21:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 6990537BBA3 for ; Mon, 3 Apr 2000 10:21:01 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA23391 for ; Mon, 3 Apr 2000 13:20:47 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/) id KAA01094; Mon, 3 Apr 2000 10:20:44 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Apr 2000 10:20:44 -0700 (PDT) Message-Id: <200004031720.KAA01094@ix.netcom.com> From: Thomas Dean To: freebsd-current@FreeBSD.ORG In-reply-to: <200004031700.KAA59566@apollo.backplane.com> (message from Matthew Dillon on Mon, 3 Apr 2000 10:00:30 -0700 (PDT)) Subject: Re: Top, vmstat, systat, etc. Broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To build the kernel, I # cd sys/i386/conf # config -r # cd ../../compile/ # make depend # make -j36 # make install /etc/make.conf has no uncommented lines in it. # file /kernel /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:23:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3D04137BCD4 for ; Mon, 3 Apr 2000 10:23:55 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA00179; Mon, 3 Apr 2000 19:23:34 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004031723.TAA00179@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <200004031707.KAA59737@apollo.backplane.com> from Matthew Dillon at "Apr 3, 2000 10:07:40 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Mon, 3 Apr 2000 19:23:34 +0200 (CEST) Cc: vallo@matti.ee, ticso@cicely.de (Bernd Walter), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > :Same story here, but using softupdates or async mounts I can reproduce > :the hang or panic in less than 60 secs.. > : > :Vinum with raid5 is plain broken, include INVARIANTS in the kernel > :and see why... > : > :-Søren > > Hang on to that thought. As soon as this struct buf mess gets cleared > up if Greg hasn't figured out where the bug is I'll throw my lot in > to try to speed-up locating and fixing the problem. Well, there is no need to wait, RELENG_4 is _the_ perfect platform for this, and the problem has to be fixed there as well.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:27:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 6AC8537BC31 for ; Mon, 3 Apr 2000 10:27:35 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id NAA11766; Mon, 3 Apr 2000 13:27:25 -0400 (EDT) Message-ID: <20000403132725.B8685@netmonger.net> Date: Mon, 3 Apr 2000 13:27:25 -0400 From: Christopher Masto To: Nick Hibma , Paul Haddad Cc: FreeBSD CURRENT Mailing List Subject: Re: Another current crash (cvs-cur.6183 References: <008501bf9b84$ad365270$0bac2ac0@pth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Mon, Apr 03, 2000 at 10:57:46AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [formatting recovered] On Mon, Apr 03, 2000 at 10:57:46AM +0100, Nick Hibma wrote: > On Fri, 31 Mar 2000, Paul Haddad wrote: > > On Wed, 22 Mar 2000, Christopher Masto wrote: > > > I've been playing around with one of those iopener things and got > > > myself into a state I thought I could get out of with the help of a > > > USB Zip drive. Unfortunately, upon purchasing and connecting one, > > > I discovered that I can't access it without a panic, which I > > > point out here on the chance it's also related. > > > > Boy I wish I had read this message before I went out and bought a > > USB zip drive... I'm in the exact same situation IOPENER with 4.0 > > installed and screwed up to a point where I can boot but not mount > > the sandisk drive. I figured that I would get a zip drive and > > mount it instead. Anyways if you found some way around this please > > let me know, otherwise I've got to make another trip out and get a > > SuperDisk instead... > > > > BTW What state are you in? Mine will boot, but gets to the point > > where it tries to mount the sandisk and panics with a ffs_write > > panic. Booting in single user doesn't help. > > Where are you guys now as far as USB drives are concerned? I've been > looking a lot at the driver lately and would like to hear about any > problems you have. Well, as for the i-opener, I've gotten mine working. See http://www.kenseglerdesigns.com/cgi-bin/UltraBoard/UltraBoard.pl?Action=ShowPost&Board=technical&Post=115 I did not have a problem with a panic mounting the sandisk, I just didn't have a /boot/loader on it so I couldn't load my mfsroot.gz. I was eventually able to find a Y-E Data floppy drive and use it as a root filesystem by entering "ufs:/dev/da0" at the mount root prompt. If a 4.0 kernel is on there, I don't know what to say, as I don't know what worked at that point. SuperDisk is certainly out of the question, since it's not there even now. Regarding USB drives, I have been using the Orb "2.2GB" USB-SCSI version with some success. There do seem to be some serious filesystem corruption problems, but I haven't had time to determine where they're coming from. I often get corruption-related panics while trying to install packages, and fsck always finds a number of serious problems and removes about a dozen files (from /usr/lib mostly, so I'll eventually lose something important). When I download something large, such as XFree86, the file's checksum comes out wrong and gzip fails with errors. I need to have a few hours free to try it on a different machine, with different media, etc. to try to narrow this down. I have also been getting kue lockups, so there are a lot of possibilities. I really haven't played with the thing too much, partly because it's very slow and takes a good 15 minutes to fsck every time I crash it. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:30:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 239FD37B539 for ; Mon, 3 Apr 2000 10:30:30 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA09185; Mon, 3 Apr 2000 10:19:02 -0700 (PDT) Message-Id: <200004031719.KAA09185@implode.root.com> To: Matthew Dillon Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Load average calculation? In-reply-to: Your message of "Sun, 02 Apr 2000 20:49:10 PDT." <200004030349.UAA52843@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 03 Apr 2000 10:19:02 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:I'm not sure if this is -current fodder or not, but since it's still >:happening in -current, I'll ask. >: >:We recently upgraded a server from 2.2.8 to 4.0(the same behavior is shown >:on 5.0-current, too). Before, with the exact same load, we'd see load >:averages from between 0.20 and 0.30. Now, we're getting: >: >:load averages: 4.16, 4.23, 4.66 >: >:Top shows the same CPU percentages, just a much higher load average for the >:same work being done. Did the load average calculation change, or something >:with the scheduler differ? Customers are complaining that the load average >:is too high, which is kinda silly, since 4.0 seems noticably faster in some >:cases. >: >:Any ideas? >: >:Kevin > > I believe the load average was changed quite a while ago to reflect not > only runnable processes but also processes stuck in disk-wait. It's > a more accurate measure of load. It's always been that way in BSD. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:33:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CD75937BC43 for ; Mon, 3 Apr 2000 10:33:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60112; Mon, 3 Apr 2000 10:33:39 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:33:39 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031733.KAA60112@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch References: <22315.954782444@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Ripping up the buffer cache right smack in the middle of Greg trying :> to debug a serious vinum/bio problem is atrocious timing. : :Actually, it is the other way around, Greg finally started to look for :the bug in vinum in the middle of my commits. : :How dare he do that ? : ::-) : :-- :Poul-Henning Kamp FreeBSD coreteam member I don't find it funny at all. Your b_iocmd commits, which were done with virtually no testing broke vinum and Alfred had to go in and fix it. The 'vinum problems' thread turns into the 'deadlock with vinum raid5' thread on saturday and on sunday you start ripping the buffer cache up. No Poul, I don't find it funny at all. Your commits have created a serious disruption and wasted a lot of people's time and, frankly, I think vinum is a thousand times more important then ripping the buffer cache to shreds in an unplanned, undiscussed, unreviewed set of commits. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:38:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DDD3E37B539 for ; Mon, 3 Apr 2000 10:38:21 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA22450; Mon, 3 Apr 2000 19:38:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch In-reply-to: Your message of "Mon, 03 Apr 2000 10:33:39 PDT." <200004031733.KAA60112@apollo.backplane.com> Date: Mon, 03 Apr 2000 19:38:12 +0200 Message-ID: <22448.954783492@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, When I mailed arch@ about this change I got no response from anybody but Bruce. I talked to Kirk about it in Malmø and got his approval. This is not unplanned. This is also not untested, I have two complete prototypes behind me. It is regretable that vinum was broken, and I hope that it is fixed with Alfreds changes, one can't win 100% all the time. Your time would be more productively used by reviewing and testing the patch at http://phk.freebsd.dk/misc than by preaching. As to the debugging of the malloc/free issue in vinum, Sørens suggestion to use releng4 sounds downright sensible to me, and I suggest you do that. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:38:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 16EDB37BE14 for ; Mon, 3 Apr 2000 10:38:15 -0700 (PDT) (envelope-from khetan@uunet.co.za) Received: from bofh.ops.uunet.co.za (bofh.ops.uunet.co.za [196.31.1.35]) by kg.ops.uunet.co.za (Postfix) with ESMTP id AC7A316E88 for ; Mon, 3 Apr 2000 19:38:01 +0200 (SAST) Received: by bofh.ops.uunet.co.za (Postfix, from userid 1000) id B53275B83; Mon, 3 Apr 2000 19:37:55 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by bofh.ops.uunet.co.za (Postfix) with ESMTP id 9ACA11EE3 for ; Mon, 3 Apr 2000 19:37:55 +0200 (SAST) Date: Mon, 3 Apr 2000 19:37:55 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@bofh.ops.uunet.co.za To: current@freebsd.org Subject: OpenSSL and Apache+ModSSL Message-ID: X-Cell: +27 82 416 0160 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I've been having great unhappiness in trying to get Apache+modSSL and OpenSSL in 5-current to work. I do not have the RSA port installed (I'm a South African citizen residing outside the USA), and built-world today with USA_RESIDENT=no set. Basically, the combination of Apache 1.3.12 and modSSL 2.6.2 is not happy with OpenSSL 0.9.4 (as that combination stands in 5-current). Does any non-US citizen or person who has installed a FreeBSD 5 system as a non-US citizen gotten Apache+modSSL to work with a recentish -current ? I specifically used the apache13-php3 port, and enabled modSSL (if that makes any difference). I saw that Kris Kennaway discussed this the last time I brought this up, and there was a refernce to the RSA library mentioned, but the thread died shortly thereafter. It was working about two/three months before the laying down of the 4-release tag. I'm seeing this from the https server logs : [03/Apr/2000 19:22:43 20348] [info] Connection to child 5 established (server x xxx.xxx.xxxxx.xx.xx:443, client xxx.xxx.xxx.xxx) [03/Apr/2000 19:22:43 20348] [info] Seeding PRNG with 1160 bytes of entropy [03/Apr/2000 19:22:44 20348] [error] SSL handshake failed (server xxxx.xxx.xxxxx .xx.xx:443, client xxx.xxx.xxx.xxx) (OpenSSL library error follows) [03/Apr/2000 19:22:44 20348] [error] OpenSSL: error:140BB004:SSL routines:SSL_RS A_PRIVATE_DECRYPT:nested asn1 error [03/Apr/2000 19:22:44 20348] [error] OpenSSL: error:1407D071:SSL routines:SSL2_R EAD:bad mac decode [Hint: Browser still remembered details of a re-created serve r certificate?] and this in it's error logs : [Mon Apr 3 19:22:44 2000] [error] mod_ssl: SSL handshake failed (server xxxx.xx x.xxxxx.xx.xx:443, client xxx.xxx.xxx.xxx) (OpenSSL library error follows) [Mon Apr 3 19:22:44 2000] [error] OpenSSL: error:140BB004:SSL routines:SSL_RSA_ PRIVATE_DECRYPT:nested asn1 error [Mon Apr 3 19:22:44 2000] [error] OpenSSL: error:1407D071:SSL routines:SSL2_REA D:bad mac decode [Hint: Browser still remembered details of a re-created server certificate?] This is generated by an OpenSSL connection from the web server to itself : 6=[khetan@xxxxx] ~$ openssl s_client -connect xxxx.xxx.xxxxx.xx.xx:443 -ssl2 + openssl s_client -connect xxxx.xxx.xxxxx.xx.xx:443 -ssl2 CONNECTED(00000003) depth=0 /C=ZA/ST=Cape Province/L=Cape Town/O=OS Users Group/OU=System Administra tion/CN=xxx.xxx.xxx.xxx/Email=khetan@freebsd.os.org.za verify error:num=18:self signed certificate verify return:1 depth=0 /C=ZA/ST=Cape Province/L=Cape Town/O=OS Users Group/OU=System Administra tion/CN=xxx.xxx.xxx.xxx/Email=khetan@freebsd.os.org.za verify return:1 31281:error:1407D071:SSL routines:SSL2_READ:bad mac decode:/usr/src/secure/lib/l ibssl/../../../crypto/openssl/ssl/s2_pkt.c:217: The debugging output for this follows. (called with openssl s_client -connect xxx.xxx.xxx.xxx:443 -nbio_test -debug) CONNECTED(00000003) write to 0807F4C0 [0808F000] (103 bytes => 2 (0x2)) 0000 - 80 65 .e write to 0807F4C0 [0808F002] (101 bytes => 2 (0x2)) 0000 - 01 03 .. write to 0807F4C0 [0808F004] (99 bytes => 3 (0x3)) 0000 - 01 00 3c ..< write to 0807F4C0 [0808F007] (96 bytes => 1 (0x1)) 0001 - write to 0807F4C0 [0808F008] (95 bytes => 4 (0x4)) 0004 - write to 0807F4C0 [0808F00C] (91 bytes => 3 (0x3)) 0000 - 00 16 .. 0003 - write to 0807F4C0 [0808F00F] (88 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F00F] (88 bytes => 2 (0x2)) 0000 - 00 13 .. write to 0807F4C0 [0808F011] (86 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F011] (86 bytes => 7 (0x7)) 0000 - 00 00 0a 00 00 05 ...... 0007 - write to 0807F4C0 [0808F018] (79 bytes => 4 (0x4)) 0000 - 00 04 .. 0004 - write to 0807F4C0 [0808F01C] (75 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F01C] (75 bytes => 4 (0x4)) 0000 - 15 00 00 12 .... write to 0807F4C0 [0808F020] (71 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F020] (71 bytes => 5 (0x5)) 0000 - 00 00 09 07 .... 0005 - write to 0807F4C0 [0808F025] (66 bytes => 7 (0x7)) 0000 - c0 03 00 80 01 00 80 ....... write to 0807F4C0 [0808F02C] (59 bytes => 6 (0x6)) 0000 - 08 00 80 06 00 40 .....@ write to 0807F4C0 [0808F032] (53 bytes => 6 (0x6)) 0000 - 00 00 14 00 00 11 ...... write to 0807F4C0 [0808F038] (47 bytes => 7 (0x7)) 0000 - 00 00 08 00 00 06 ...... 0007 - write to 0807F4C0 [0808F03F] (40 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F03F] (40 bytes => 5 (0x5)) 0000 - 00 03 04 00 80 ..... write to 0807F4C0 [0808F044] (35 bytes => 1 (0x1)) 0000 - 02 . write to 0807F4C0 [0808F045] (34 bytes => 6 (0x6)) 0000 - 00 80 2d 14 bb 1b ..-... write to 0807F4C0 [0808F04B] (28 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F04B] (28 bytes => 1 (0x1)) 0000 - c3 . write to 0807F4C0 [0808F04C] (27 bytes => 5 (0x5)) 0000 - 71 65 46 c2 e7 qeF.. write to 0807F4C0 [0808F051] (22 bytes => 2 (0x2)) 0000 - f3 9b .. write to 0807F4C0 [0808F053] (20 bytes => -1 (0xFFFFFFFF)) write W BLOCK write to 0807F4C0 [0808F053] (20 bytes => 7 (0x7)) 0000 - 9a 24 57 aa 12 2e 97 .$W.... write to 0807F4C0 [0808F05A] (13 bytes => 7 (0x7)) 0000 - fb af a5 35 d5 fa 74 ...5..t write to 0807F4C0 [0808F061] (6 bytes => 2 (0x2)) 0000 - 91 42 .B write to 0807F4C0 [0808F063] (4 bytes => 1 (0x1)) 0000 - 86 . write to 0807F4C0 [0808F064] (3 bytes => 3 (0x3)) 0000 - 18 08 d9 ... read from 0807F4C0 [08095000] (7 bytes => 7 (0x7)) 0000 - 16 03 01 00 4a 02 ....J. 0007 - read from 0807F4C0 [08095007] (72 bytes => 72 (0x48)) 0000 - 00 46 03 01 38 e8 d6 5c-2f ce 90 77 ed ed 74 ac .F..8..\/..w..t. 0010 - ec 2e 06 f6 12 0b cd 0d-2f 0d 89 e4 df 11 23 ba ......../.....#. 0020 - 07 03 e1 da 20 7b b3 ca-70 97 d0 6e e2 df 83 9a .... {..p..n.... 0030 - f0 1f 77 47 21 9e e7 aa-d2 54 0e bc 0b 69 7f 9c ..wG!....T...i.. 0040 - f3 90 e5 12 c8 00 16 ....... 0048 - read from 0807F4C0 [08095000] (5 bytes => 5 (0x5)) 0000 - 16 03 01 04 17 ..... read from 0807F4C0 [08095005] (1047 bytes => 940 (0x3AC)) 0000 - 0b 00 04 13 00 04 10 00-04 0d 30 82 04 09 30 82 ..........0...0. 0010 - 03 72 a0 03 02 01 02 02-01 00 30 0d 06 09 2a 86 .r........0...*. 0020 - 48 86 f7 0d 01 01 04 05-00 30 81 ba 31 0b 30 09 H........0..1.0. 0030 - 06 03 55 04 06 13 02 5a-41 31 16 30 14 06 03 55 ..U....ZA1.0...U 0040 - 04 08 13 0d 43 61 70 65-20 50 72 6f 76 69 6e 63 ....Cape Provinc 0050 - 65 31 12 30 10 06 03 55-04 07 13 09 43 61 70 65 e1.0...U....Cape 0060 - 20 54 6f 77 6e 31 17 30-15 06 03 55 04 0a 13 0e Town1.0...U.... 0070 - 4f 53 20 55 73 65 72 73-20 47 72 6f 75 70 31 1e OS Users Group1. 0080 - 30 1c 06 03 55 04 0b 13-15 53 79 73 74 65 6d 20 0...U....System 0090 - 41 64 6d 69 6e 69 73 74-72 61 74 69 6f 6e 31 1d Administration1. 00a0 - 30 1b 06 03 55 04 03 13-14 62 6f 66 68 2e 6f 70 0...U....xxxx.xx 00b0 - 73 2e 75 75 6e 65 74 2e-63 6f 2e 7a 61 31 27 30 x.xxxxx.xx.xx1'0 00c0 - 25 06 09 2a 86 48 86 f7-0d 01 09 01 16 18 6b 68 %..*.H........kh 00d0 - 65 74 61 6e 40 66 72 65-65 62 73 64 2e 6f 73 2e etan@freebsd.os. 00e0 - 6f 72 67 2e 7a 61 30 1e-17 0d 30 30 30 33 31 36 org.za0...000316 00f0 - 31 33 35 33 35 37 5a 17-0d 30 31 30 33 31 36 31 135357Z..0103161 0100 - 33 35 33 35 37 5a 30 81-ba 31 0b 30 09 06 03 55 35357Z0..1.0...U 0110 - 04 06 13 02 5a 41 31 16-30 14 06 03 55 04 08 13 ....ZA1.0...U... 0120 - 0d 43 61 70 65 20 50 72-6f 76 69 6e 63 65 31 12 .Cape Province1. 0130 - 30 10 06 03 55 04 07 13-09 43 61 70 65 20 54 6f 0...U....Cape To 0140 - 77 6e 31 17 30 15 06 03-55 04 0a 13 0e 4f 53 20 wn1.0...U....OS 0150 - 55 73 65 72 73 20 47 72-6f 75 70 31 1e 30 1c 06 Users Group1.0.. 0160 - 03 55 04 0b 13 15 53 79-73 74 65 6d 20 41 64 6d .U....System Adm 0170 - 69 6e 69 73 74 72 61 74-69 6f 6e 31 1d 30 1b 06 inistration1.0.. 0180 - 03 55 04 03 13 14 62 6f-66 68 2e 6f 70 73 2e 75 .U....xxxx.xxx.x 0190 - 75 6e 65 74 2e 63 6f 2e-7a 61 31 27 30 25 06 09 xxxx.xx.xx1'0%.. 01a0 - 2a 86 48 86 f7 0d 01 09-01 16 18 6b 68 65 74 61 *.H........kheta 01b0 - 6e 40 66 72 65 65 62 73-64 2e 6f 73 2e 6f 72 67 n@freebsd.os.org 01c0 - 2e 7a 61 30 81 9f 30 0d-06 09 2a 86 48 86 f7 0d .za0..0...*.H... 01d0 - 01 01 01 05 00 03 81 8d-00 30 81 89 02 81 81 00 .........0...... 01e0 - c6 74 3d ee b5 6f 0a e0-25 6a 79 20 df ed 61 2f .t=..o..%jy ..a/ 01f0 - 6e 84 33 ec 26 8b 1d e4-d1 13 47 71 50 4a 21 ca n.3.&.....GqPJ!. 0200 - d4 e7 1b 09 9b a9 53 34-0d af 00 5b 2d c5 a4 4a ......S4...[-..J 0210 - 13 a8 d0 ea 72 43 3e fa-a1 26 a5 22 ab 38 0c 41 ....rC>..&.".8.A 0220 - 5e c4 be 69 0d ab 85 0f-3f 51 4b 5c fa f4 f0 80 ^..i....?QK\.... 0230 - 0d d6 7a 1e cd 89 36 32-c9 12 85 ec 8f 41 fe 7f ..z...62.....A.. 0240 - 26 74 89 4a 99 47 bd ec-18 31 78 ba af 59 21 41 &t.J.G...1x..Y!A 0250 - 7c e7 e4 8a b1 a3 86 69-a4 b9 e6 51 51 61 60 3d |......i...QQa`= 0260 - 02 03 01 00 01 a3 82 01-1b 30 82 01 17 30 1d 06 .........0...0.. 0270 - 03 55 1d 0e 04 16 04 14-3b 63 2e 78 2b 36 dd 15 .U......;c.x+6.. 0280 - 05 ea 73 6f b3 7d 24 10-2b 77 02 c5 30 81 e7 06 ..so.}$.+w..0... 0290 - 03 55 1d 23 04 81 df 30-81 dc 80 14 3b 63 2e 78 .U.#...0....;c.x 02a0 - 2b 36 dd 15 05 ea 73 6f-b3 7d 24 10 2b 77 02 c5 +6....so.}$.+w.. 02b0 - a1 81 c0 a4 81 bd 30 81-ba 31 0b 30 09 06 03 55 ......0..1.0...U 02c0 - 04 06 13 02 5a 41 31 16-30 14 06 03 55 04 08 13 ....ZA1.0...U... 02d0 - 0d 43 61 70 65 20 50 72-6f 76 69 6e 63 65 31 12 .Cape Province1. 02e0 - 30 10 06 03 55 04 07 13-09 43 61 70 65 20 54 6f 0...U....Cape To 02f0 - 77 6e 31 17 30 15 06 03-55 04 0a 13 0e 4f 53 20 wn1.0...U....OS 0300 - 55 73 65 72 73 20 47 72-6f 75 70 31 1e 30 1c 06 Users Group1.0.. 0310 - 03 55 04 0b 13 15 53 79-73 74 65 6d 20 41 64 6d .U....System Adm 0320 - 69 6e 69 73 74 72 61 74-69 6f 6e 31 1d 30 1b 06 inistration1.0.. 0330 - 03 55 04 03 13 14 62 6f-66 68 2e 6f 70 73 2e 75 .U....xxxx.xxx.x 0340 - 75 6e 65 74 2e 63 6f 2e-7a 61 31 27 30 25 06 09 xxxx.xx.xx1'0%.. 0350 - 2a 86 48 86 f7 0d 01 09-01 16 1820489:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s23_lib.c:215: 6b 68 65 74 61 *.H........kheta 0360 - 6e 40 66 72 65 65 62 73-64 2e 6f 73 2e 6f 72 67 n@freebsd.os.org 0370 - 2e 7a 61 82 01 00 30 0c-06 03 55 1d 13 04 05 30 .za...0...U....0 0380 - 03 01 01 ff 30 0d 06 09-2a 86 48 86 f7 0d 01 01 ....0...*.H..... 0390 - 04 05 00 03 81 81 00 62-00 38 25 f7 5d 35 4c b6 .......b.8%.]5L. 03a0 - 41 af 41 2f 46 57 90 a2-ae 19 a5 f8 A.A/FW...... read from 0807F4C0 [080953B1] (107 bytes => 0 (0x0)) Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * kg+details@uunet.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:51:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 570D937B539 for ; Mon, 3 Apr 2000 10:51:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA60287; Mon, 3 Apr 2000 10:51:49 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:51:49 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031751.KAA60287@apollo.backplane.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch References: <22448.954783492@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Matt, : :When I mailed arch@ about this change I got no response from anybody :but Bruce. : :I talked to Kirk about it in Malmø and got his approval. : :This is not unplanned. : :This is also not untested, I have two complete prototypes behind me. : :It is regretable that vinum was broken, and I hope that it is fixed :with Alfreds changes, one can't win 100% all the time. : :Your time would be more productively used by reviewing and testing :the patch at http://phk.freebsd.dk/misc than by preaching. : :As to the debugging of the malloc/free issue in vinum, Sørens suggestion :to use releng4 sounds downright sensible to me, and I suggest you do :that. : :-- :Poul-Henning Kamp FreeBSD coreteam member I don't think these excuses come close to justifying your commits or your timing. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 10:52:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 3A0A737B84D for ; Mon, 3 Apr 2000 10:52:26 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id KAA96024 for freebsd-current@freebsd.org; Mon, 3 Apr 2000 10:54:38 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200004031754.KAA96024@troutmask.apl.washington.edu> Subject: remove src/lib/libm from source tree To: FreeBSD Current Date: Mon, 3 Apr 2000 10:54:37 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any compelling reason for retaining src/lib/libm in the source tree? Yes, I realize that libm is the original libm from CSRG 4.4 BSD-lite. However, the errors noted below have been in the source since 1994 when rgrimes imported the initial sources. The only person that I can of that may have a working copy of libm is bde. Additionally, with Martin Craucer's recent FP work, I think PR i386/105 have become fixed: a [1995/01/11] i386/105 bde Distributed libm (msun) has \ non-standard error handling. -- Steve cd /usr/src/lib/libm make depend make cc -O -pipe -I/usr/src/lib/libm/common_source -Dnational -c /usr/src/lib/libm/common_source/lgamma. c -o lgamma.o /usr/src/lib/libm/common_source/lgamma.c:141: syntax error before `double' *** Error code 1 (continuing) /usr/src/lib/libm/ieee/support.c: In function `scalb': /usr/src/lib/libm/ieee/support.c:91: argument `N' doesn't match prototype /usr/include/math.h:153: prototype declaration *** Error code 1 (continuing) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 11:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.med.und.nodak.edu (smtp.med.und.NoDak.edu [134.129.166.20]) by hub.freebsd.org (Postfix) with ESMTP id F08E237B79B for ; Mon, 3 Apr 2000 11:13:44 -0700 (PDT) (envelope-from bpederson@geocities.com) Received: from accord.med.und.nodak.edu ([134.129.166.13] helo=geocities.com) by smtp.med.und.nodak.edu with esmtp (Exim 3.13 #3) id 12cBLm-000KFa-00 for current@freebsd.org; Mon, 03 Apr 2000 13:13:23 -0500 Message-ID: <38E8DEEF.7224C9A@geocities.com> Date: Mon, 03 Apr 2000 13:11:59 -0500 From: Barry Pederson X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Load average calculation? References: <200004030410.XAA75906@celery.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 11:10 PM -0500 2000/4/2, Kevin Day wrote: > > > It's probably more accurate, but from a PR standpoint it makes it "look" > > like FreeBSD is choking under the load, when it really isn't. Or am I the > > only one that even cares about this? :) > > It's also extremely confusing for Linux users/admins who are used > to the system rolling over and dying if the load average ever gets > over 2.0 (and panic'ing if the load average goes over 4.0), and who > see FreeBSD capable of surviving (if not necessarily performing very > well) with load averages as high as 100 or even 200. Won't this also goof up programs like Exim (an SMTP MTA), that have some settings available for how to handle messages under various loads (process now, queue for later, etc)? Barry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 11:39: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 4C95A37B680 for ; Mon, 3 Apr 2000 11:39:04 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 53F7ADBF2; Mon, 3 Apr 2000 20:38:50 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <38E8DEEF.7224C9A@geocities.com> References: <200004030410.XAA75906@celery.dragondata.com> <38E8DEEF.7224C9A@geocities.com> Date: Mon, 3 Apr 2000 20:31:03 +0200 To: Barry Pederson , current@FreeBSD.ORG From: Brad Knowles Subject: Re: Load average calculation? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:11 PM -0500 2000/4/3, Barry Pederson wrote: > Won't this also goof up programs like Exim (an SMTP MTA), that have some > settings available for how to handle messages under various loads > (process now, queue for later, etc)? If there has been an actual change in how the load average is calculated, then any program that changes it's behaviour based on the load average may have problems. This would certainly include SMTP MTAs such as sendmail, Exim, etc.... However, more recent comments lead me to question whether there actually has been a change in the way load is calculated. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 11:39:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 0602F37B5BE for ; Mon, 3 Apr 2000 11:39:23 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id UAA08751; Mon, 3 Apr 2000 20:39:45 +0200 (MET DST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 12cBlA-0002kD-00 for ; Mon, 03 Apr 2000 20:39:36 +0200 Date: Mon, 3 Apr 2000 20:39:36 +0200 From: Szilveszter Adam To: current@freebsd.org Subject: Re: OpenSSL and Apache+ModSSL Message-ID: <20000403203935.B7244@petra.hos.u-szeged.hu> Mail-Followup-To: current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from khetan@uunet.co.za on Mon, Apr 03, 2000 at 07:37:55PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 07:37:55PM +0200, Khetan Gajjar wrote: > Hi. > > I've been having great unhappiness in trying to get Apache+modSSL and > OpenSSL in 5-current to work. > > I do not have the RSA port installed (I'm a South African > citizen residing outside the USA), and built-world today with > USA_RESIDENT=no set. > > Basically, the combination of Apache 1.3.12 and modSSL 2.6.2 > is not happy with OpenSSL 0.9.4 (as that combination stands > in 5-current). Does any non-US citizen or person who has installed > a FreeBSD 5 system as a non-US citizen gotten Apache+modSSL to > work with a recentish -current ? I specifically used the > apache13-php3 port, and enabled modSSL (if that makes any > difference). [...] > > I saw that Kris Kennaway discussed this the last time I brought this > up, and there was a refernce to the RSA library mentioned, but the > thread died shortly thereafter. Hi! I had the same issues (I live in Hungary) and followed this thread closely. It didn't die, it just changed the ${SUBJECT} line:-). (It is now called: "RSA library problems" or somesuch) To sum it up: What you need to do is to add a line in /usr/src/secure/lib/librsaintl/Makefile. Diff follows: --- /usr/src/secure/lib/librsaintl/Makefile.old Tue Mar 14 00:25:58 2000 +++ /usr/src/secure/lib/librsaintl/Makefile Sun Apr 2 18:27:27 2000 @@ -10,6 +10,8 @@ CFLAGS+= -I${.OBJDIR} +LDADD+= -L${.OBJDIR}/../libcrypto -lcrypto + # rsaref SRCS+= rsa_err.c rsa_eay.c rsa_intlstubs.c This way, I have now a working Apache+modSSL combo from ports. Later, I will also rebuild the world with this, but I am waiting for somebody to actually commit this change to the tree. Note that although the Makefile has different revision # in RELENG_4 and HEAD, the patch should apply nevertheless. I think this error is due to the fact that not many developers had a chance to test international versions too. Hope this helps... Szilveszter ADAM Szeged University Szeged Hungary -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 11:50:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9E51137BE8E for ; Mon, 3 Apr 2000 11:50:02 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA21201; Mon, 3 Apr 2000 20:49:46 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004031849.UAA21201@freebsd.dk> Subject: Re: HighPoint UDMA66 ICRC READ ERROR In-Reply-To: <38E8DF04.7BCC5EBE@usishealth.com> from Erik de Zeeuw at "Apr 3, 2000 01:12:20 pm" To: erik@usishealth.com (Erik de Zeeuw) Date: Mon, 3 Apr 2000 20:49:46 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Erik de Zeeuw wrote: > atapci1: port \ > 0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 \ > irq 11 at device 19.0 on pci0 > ata2: at 0xb000 on atapci1 > atapci2: port \ > 0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07 \ > irq 11 at device 19.1 on pci0 > ... > ad4: 19574MB [39770/16/63] at ata2-master using UDMA66 > > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39566319 retrying > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39627167 retrying > gargamel /kernel: ad4: UDMA ICRC READ ERROR blk# 39628463 retrying This means that the system has problems getting data correctly over the interface from disk to controller, in most cases its a cable problem. Are you using the right 80pin ata66 cable for this ? is it at max 18" long ? Another thing is that if you have the cable running close to something like the PSU coils on most modern motherboards, that might cause trouble too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 11:57:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 510BC37BB7B for ; Mon, 3 Apr 2000 11:57:11 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 7873 invoked from network); 3 Apr 2000 18:57:00 -0000 Received: from acs-63-90-88-170.zbzoom.net (HELO cvzoom.net) (63.90.88.170) by ns.cvzoom.net with SMTP; 3 Apr 2000 18:57:00 -0000 Message-ID: <38E8E960.2C5A8FD5@cvzoom.net> Date: Mon, 03 Apr 2000 14:56:32 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: Barry Pederson , current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030410.XAA75906@celery.dragondata.com> <38E8DEEF.7224C9A@geocities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > If there has been an actual change in how the load average is > calculated, then any program that changes it's behaviour based on the > load average may have problems. This would certainly include SMTP > MTAs such as sendmail, Exim, etc.... I agree. IMO, the load avg. formula should stick as close as possible to those in previous releases of FreeBSD. OTOH, maybe those apps that need to query the load avg. are flawed anyways, as load avg. calculation tends to be system dependent. For example, FreeBSD, Linux, Solaris, SCO, etc. may all be running the exact same processes, but will the load avg. always be consistent across those platforms? I think not. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12: 8:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id D55EA37B579 for ; Mon, 3 Apr 2000 12:08:36 -0700 (PDT) (envelope-from freebsd@ewok.creative.net.au) Received: (qmail 60809 invoked by uid 1008); 3 Apr 2000 19:08:00 -0000 Date: Tue, 4 Apr 2000 03:07:59 +0800 From: Adrian Chadd To: Matthew Dillon Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch Message-ID: <20000404030757.A53939@ewok.creative.net.au> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.4i In-Reply-To: <200004031751.KAA60287@apollo.backplane.com>; from Matthew Dillon on Mon, Apr 03, 2000 at 10:51:49AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000, Matthew Dillon wrote: > > : > : > :Matt, > : > :When I mailed arch@ about this change I got no response from anybody > :but Bruce. > : > :I talked to Kirk about it in Malmø and got his approval. > : > :This is not unplanned. > : > :This is also not untested, I have two complete prototypes behind me. > : > :It is regretable that vinum was broken, and I hope that it is fixed > :with Alfreds changes, one can't win 100% all the time. > : > :Your time would be more productively used by reviewing and testing > :the patch at http://phk.freebsd.dk/misc than by preaching. > : > :As to the debugging of the malloc/free issue in vinum, Sørens suggestion > :to use releng4 sounds downright sensible to me, and I suggest you do > :that. > : > :-- > :Poul-Henning Kamp FreeBSD coreteam member > > I don't think these excuses come close to justifying your commits > or your timing. * His timing did suck * He's now doing the right thing, at least, instead of committing the second patchset without submitting them for peer review * breaking vinum did suck * RELENG_4 is a good place to play with vinum fixes too * You both have committed things that have broken other areas. :-) This really isn't constructive. I haven't looked at the patchset that phk has posted up but I think it'd be more useful if people gave comments about the changes and their usefulness rather than the bickering going on now. Please :) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:18:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EC7CB37BEA9; Mon, 3 Apr 2000 12:18:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA21664; Mon, 3 Apr 2000 12:18:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 3 Apr 2000 12:18:28 -0700 (PDT) From: Kris Kennaway To: Szilveszter Adam Cc: current@freebsd.org Subject: Re: OpenSSL and Apache+ModSSL In-Reply-To: <20000403203935.B7244@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Szilveszter Adam wrote: > --- /usr/src/secure/lib/librsaintl/Makefile.old Tue Mar 14 00:25:58 2000 > +++ /usr/src/secure/lib/librsaintl/Makefile Sun Apr 2 18:27:27 2000 > @@ -10,6 +10,8 @@ > CFLAGS+= -I${.OBJDIR} > +LDADD+= -L${.OBJDIR}/../libcrypto -lcrypto > + > # rsaref > SRCS+= rsa_err.c rsa_eay.c rsa_intlstubs.c I'll take a closer look at this tonight and try and commit it to internat (and freefall), lag willing (if it passes a world build). If someone can confirm the world build for me in the meantime, it would save me the trouble. > nevertheless. I think this error is due to the fact that not many developers > had a chance to test international versions too. Yep. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:20:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 07E5837B640 for ; Mon, 3 Apr 2000 12:20:34 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 1529 invoked from network); 3 Apr 2000 19:20:30 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 3 Apr 2000 19:20:30 -0000 Date: Tue, 4 Apr 2000 05:20:11 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Gary Jennejohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: <200004031459.QAA49076@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Gary Jennejohn wrote: > Bruce Evans writes: > >On Sun, 2 Apr 2000, Gary Jennejohn wrote: > >> I think we should nuke csu_hdr since it's not used anywhere. Is that > >> what you really mean ? > > > >Yes. I'm trying the following patch. Only tested at compile time. > > > [patch snipped] > > Thank you, Bruce ! This is pretty much the same patch I tested. > > So, should I commit it ? If you have tested it :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:33:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 845AB37B5BA for ; Mon, 3 Apr 2000 12:33:08 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 96AE3DDF8; Mon, 3 Apr 2000 21:32:25 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <38E8E960.2C5A8FD5@cvzoom.net> References: <200004030410.XAA75906@celery.dragondata.com> <38E8DEEF.7224C9A@geocities.com> <38E8E960.2C5A8FD5@cvzoom.net> Date: Mon, 3 Apr 2000 21:28:05 +0200 To: Donn Miller From: Brad Knowles Subject: Re: Load average calculation? Cc: Barry Pederson , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:56 PM -0400 2000/4/3, Donn Miller wrote: > For example, FreeBSD, > Linux, Solaris, SCO, etc. may all be running the exact same processes, > but will the load avg. always be consistent across those platforms? I > think not. That's not a problem. Other OSes really aren't our problem, and you would expect to have different configuration files on them anyway. What *may* be a potential problem is if we change the way we calculate load average on our own OS -- that we *are* responsible for. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:35: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 1E16037B5BE for ; Mon, 3 Apr 2000 12:34:55 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA23846; Mon, 3 Apr 2000 21:32:51 +0200 (CEST) Message-Id: <200004031932.VAA23846@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 03 Apr 2000 21:20:38 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 21:32:51 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: >On Mon, 3 Apr 2000, Gary Jennejohn wrote: > >> Bruce Evans writes: >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: >> >> I think we should nuke csu_hdr since it's not used anywhere. Is that >> >> what you really mean ? >> > >> >Yes. I'm trying the following patch. Only tested at compile time. >> > >> [patch snipped] >> >> Thank you, Bruce ! This is pretty much the same patch I tested. >> >> So, should I commit it ? > >If you have tested it :-). > I'm running with the change right now. No problems. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:44:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id CE94637BA2C for ; Mon, 3 Apr 2000 12:44:41 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 1470F2DC07; Mon, 3 Apr 2000 21:48:40 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 493B47811; Mon, 3 Apr 2000 21:44:39 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 44CBF10E17; Mon, 3 Apr 2000 21:44:39 +0200 (CEST) Date: Mon, 3 Apr 2000 21:44:37 +0200 (CEST) From: Andrzej Bialecki To: Matthew Jacob Cc: Brad Knowles , FreeBSD-CURRENT Mailing List Subject: Re: Sysctl for CAM SCSI quirks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Matthew Jacob wrote: > > These aren't available at boot time when you need them, are they? You will need probably the ability to create sysctls on the fly, which is still on my drawing board. If you can live with creating just completely separate subtrees (no overlap) this code is ready to use. Let me know if you want it. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 12:56:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 46BEF37B5AE for ; Mon, 3 Apr 2000 12:56:01 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA00192; Mon, 3 Apr 2000 20:47:47 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA00490; Mon, 3 Apr 2000 19:09:13 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004031809.TAA00490@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: Jeroen Ruigrok/Asmodai , current@freebsd.org, brian@hak.lan.awfulhak.org Subject: Re: Summer/winter time problems with daily/460 In-Reply-To: Message from Garrett Wollman of "Mon, 03 Apr 2000 12:37:16 EDT." <200004031637.MAA14580@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Apr 2000 19:09:13 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Someone more acquainted with the daily scripts may want to > > investigate/fix that. > > In the general case, it's hopeless. No, not if date -vblah DTRT. > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 13:13: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from astralblue.com (adsl-209-76-108-39.dsl.snfc21.pacbell.net [209.76.108.39]) by hub.freebsd.org (Postfix) with ESMTP id 8E27837B6D0 for ; Mon, 3 Apr 2000 13:11:43 -0700 (PDT) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by astralblue.com (8.9.3/8.9.3) with ESMTP id NAA01108; Mon, 3 Apr 2000 13:11:36 -0700 (PDT) (envelope-from ab@astralblue.com) Date: Mon, 3 Apr 2000 13:11:36 -0700 (PDT) From: "Eugene M. Kim" To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Top, vmstat, systat, etc. Broken In-Reply-To: <200004031720.KAA01094@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check if your /dev/null has been replaced by some stupid `real' file. The `nlist failed' problem bit me several weeks ago on two machines (one running 4-stable and the other running -current) and it turned out to be a /dev/null problem. You may want to remove /dev/null maually and do a `sh MAKEDEV std' to alleviate this problem. I don't have the vaguest idea how this happened, though. Hope this helped, Eugene On Mon, 3 Apr 2000, Thomas Dean wrote: | To build the kernel, I | | # cd sys/i386/conf | # config -r | # cd ../../compile/ | # make depend | # make -j36 | # make install | | /etc/make.conf has no uncommented lines in it. | | # file /kernel | /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), | dynamically linked, not stripped | | tomdean | | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe freebsd-current" in the body of the message | -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 13:14: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from oscar.dorf.wh.uni-dortmund.de (oscar.dorf.wh.uni-dortmund.de [129.217.244.216]) by hub.freebsd.org (Postfix) with ESMTP id 55B3137B630 for ; Mon, 3 Apr 2000 13:12:39 -0700 (PDT) (envelope-from patrick@oscar.dorf.wh.uni-dortmund.de) Received: from tony.dorf.wh.uni-dortmund.de (root@tony.dorf.wh.uni-dortmund.de [129.217.244.217]) by oscar.dorf.wh.uni-dortmund.de (8.9.3/8.9.3) with ESMTP id WAA33121 for ; Mon, 3 Apr 2000 22:12:29 +0200 (CEST) (envelope-from patrick@oscar.dorf.wh.uni-dortmund.de) Received: (from patrick@localhost) by tony.dorf.wh.uni-dortmund.de (8.9.3/8.9.3) id WAA02023 for current@FreeBSD.ORG; Mon, 3 Apr 2000 22:12:22 +0200 Date: Mon, 3 Apr 2000 22:12:22 +0200 From: Patrick Mau To: current@FreeBSD.ORG Subject: Re: Load average calculation? Message-ID: <20000403221222.A2019@tony.dorf.wh.uni-dortmund.de> Reply-To: Patrick Mau References: <200004030410.XAA75906@celery.dragondata.com> <38E8DEEF.7224C9A@geocities.com> <38E8E960.2C5A8FD5@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E8E960.2C5A8FD5@cvzoom.net>; from dmmiller@cvzoom.net on Mon, Apr 03, 2000 at 02:56:32PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 02:56:32PM -0400, Donn Miller wrote: > Brad Knowles wrote: > > > If there has been an actual change in how the load average is > > calculated, then any program that changes it's behaviour based on the > > load average may have problems. This would certainly include SMTP > > MTAs such as sendmail, Exim, etc.... > > I agree. IMO, the load avg. formula should stick as close as possible > to those in previous releases of FreeBSD. OTOH, maybe those apps that > need to query the load avg. are flawed anyways, as load avg. > calculation tends to be system dependent. On all Unix-like systems I know, the load average is the average mumber of processes running during a given time interval. I can't see what use it may have to count load for _waiting_ processes. I/O load is not process load, if a process waits for I/O completion it does not use up its timeslice. > For example, FreeBSD, > Linux, Solaris, SCO, etc. may all be running the exact same processes, > but will the load avg. always be consistent across those platforms? I > think not. I tend to disagree. > > - Donn cheers, Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 13:28:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 2087537BEF0 for ; Mon, 3 Apr 2000 13:27:33 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 10157 invoked from network); 3 Apr 2000 20:26:31 -0000 Received: from acs-63-90-88-170.zbzoom.net (HELO cvzoom.net) (63.90.88.170) by ns.cvzoom.net with SMTP; 3 Apr 2000 20:26:31 -0000 Message-ID: <38E8FE5B.CD2FD3E6@cvzoom.net> Date: Mon, 03 Apr 2000 16:26:03 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030410.XAA75906@celery.dragondata.com> <38E8DEEF.7224C9A@geocities.com> <38E8E960.2C5A8FD5@cvzoom.net> <20000403221222.A2019@tony.dorf.wh.uni-dortmund.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Mau wrote: > On all Unix-like systems I know, the load average is the average mumber > of processes running during a given time interval. I can't see what use > it may have to count load for _waiting_ processes. > > I/O load is not process load, if a process waits for I/O completion it does > not use up its timeslice. I think we ought to re-examine the definition of load average. By load, we mean an actual load on the cpu, and waiting processes aren't really exerting a cpu load. So, by that reasoning I say waiting processes don't count. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 13:48:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9385837B5FF; Mon, 3 Apr 2000 13:48:12 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA31396; Mon, 3 Apr 2000 13:47:35 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 3 Apr 2000 13:47:35 -0700 (PDT) From: Kris Kennaway To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Top, vmstat, systat, etc. Broken In-Reply-To: <200004031720.KAA01094@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Thomas Dean wrote: > # file /kernel > /kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > dynamically linked, not stripped I deleted the original, but are you booting through the loader, or loading the kernel directly? Doing the latter used to have problems similar to the ones you're seing, but I'm not sure if it's been fixed. Bruce had a patch which addressed it. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 13:59:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id C734837B668 for ; Mon, 3 Apr 2000 13:57:45 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA13953; Mon, 3 Apr 2000 16:42:00 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/) id NAA02472; Mon, 3 Apr 2000 13:41:57 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Apr 2000 13:41:57 -0700 (PDT) Message-Id: <200004032041.NAA02472@ix.netcom.com> From: Thomas Dean To: ab@astralblue.com Cc: freebsd-current@FreeBSD.ORG In-reply-to: (ab@astralblue.com) Subject: Re: Top, vmstat, systat, etc. Broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /dev/null was not the problem. I removed and remade it. I am using the latest MAKEDEV. # ls -l /dev/null crw-rw-rw- 1 root wheel 2, 2 Apr 3 13:40 /dev/null tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 14: 9:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id 7164637B787 for ; Mon, 3 Apr 2000 14:09:29 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Mon, 3 Apr 2000 16:08:47 -0500 From: Richard Wackerbarth To: dmmiller@cvzoom.net Subject: Re: Load average calculation? Date: Mon, 3 Apr 2000 16:08:46 -0500 X-Mailer: KMail [version 1.1.38] Content-Type: text/plain References: <200004030410.XAA75906@celery.dragondata.com> <20000403221222.A2019@tony.dorf.wh.uni-dortmund.de> <38E8FE5B.CD2FD3E6@cvzoom.net> In-Reply-To: <38E8FE5B.CD2FD3E6@cvzoom.net> Cc: current@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <00040316084601.08733@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 03 Apr 2000, Donn Miller wrote: > I think we ought to re-examine the definition of load average. By > load, we mean an actual load on the cpu, and waiting processes aren't > really exerting a cpu load. So, by that reasoning I say waiting > processes don't count. I think you have an incorrect (incomplete) definition. Traditionally, the load was the number of processes WANTING to run. Tasks which are waiting for "user" I/O are excluded. However, tasks waiting to be swapped in should be counted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 14:13:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 5AAE937B644 for ; Mon, 3 Apr 2000 14:13:27 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 432 invoked from network); 3 Apr 2000 21:13:08 -0000 Received: from acs-63-90-88-170.zbzoom.net (HELO cvzoom.net) (63.90.88.170) by ns.cvzoom.net with SMTP; 3 Apr 2000 21:13:08 -0000 Message-ID: <38E90947.6263CAA@cvzoom.net> Date: Mon, 03 Apr 2000 17:12:39 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: Load average calculation? References: <200004030410.XAA75906@celery.dragondata.com> <20000403221222.A2019@tony.dorf.wh.uni-dortmund.de> <38E8FE5B.CD2FD3E6@cvzoom.net> <00040316084601.08733@nomad.dataplex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Wackerbarth wrote: > > On Mon, 03 Apr 2000, Donn Miller wrote: > > > I think we ought to re-examine the definition of load average. By > > load, we mean an actual load on the cpu, and waiting processes aren't > > really exerting a cpu load. So, by that reasoning I say waiting > > processes don't count. > > I think you have an incorrect (incomplete) definition. > > Traditionally, the load was the number of processes WANTING to run. > Tasks which are waiting for "user" I/O are excluded. > However, tasks waiting to be swapped in should be counted. Hmmm... I wonder how Linux computes load average? Although FreeBSD has nothing to do with Linux et. al., it would be good, IMO, to maintain some consistency with how those other unix variants determine the load avg. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 14:34: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BBED837B630; Mon, 3 Apr 2000 14:34:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA61603; Mon, 3 Apr 2000 14:34:01 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 14:34:01 -0700 (PDT) From: Matthew Dillon Message-Id: <200004032134.OAA61603@apollo.backplane.com> To: Adrian Chadd Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: 2nd call for reviews and tests: buf->bio patch References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404030757.A53939@ewok.creative.net.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :* His timing did suck :* He's now doing the right thing, at least, instead of committing the : second patchset without submitting them for peer review I disagree. What Poul is doing is committing stuff first, then trying to get validation after the fact (and in a rather demanding way I might add) when people complain. He is willing to dig his feet in and spend weeks arguing over the issue until people get tired enough to either accept a compromise, or allow his commits to stay in the tree verbatim. Furthermore, whenever his commit breaks something, it is generally someone else who has to take up the ball and fix it. I may break the tree occassionally, but I damn well stay on the front lines and fix any problems ASAP rather then force other people to fix them for me. This is the third time this has happened. Every time it happens it creates a huge disruption and every time it happens we end up with a compromise that does absolute *nothing* to prevent a reoccurance of the problem. The commit should not have happened in the first place. My position is fairly simple: I am getting seriously tired of seeing this repetition occur every few months, and I would like something *REAL* to be done about it which will prevent the repetition from occuring in the future. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 14:36: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CB86737B559 for ; Mon, 3 Apr 2000 14:35:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA30648; Mon, 3 Apr 2000 14:35:43 -0700 Date: Mon, 3 Apr 2000 14:35:44 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrzej Bialecki Cc: Brad Knowles , FreeBSD-CURRENT Mailing List Subject: Re: Sysctl for CAM SCSI quirks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure I follow this. This subject has come up before in that tape quirks are really busted, etc.. I was going to implement a usage of getenv so that *something* would be available for 4.0- but I was talked out of it by a number of people (you know who you are) who said this was the wrong way to do this. But we're still left with the same problem. On Mon, 3 Apr 2000, Andrzej Bialecki wrote: > On Mon, 3 Apr 2000, Matthew Jacob wrote: > > > > > These aren't available at boot time when you need them, are they? > > You will need probably the ability to create sysctls on the fly, which is > still on my drawing board. If you can live with creating just completely > separate subtrees (no overlap) this code is ready to use. Let me know if > you want it. > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 14:42: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F39B137B5BE for ; Mon, 3 Apr 2000 14:41:59 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA16068; Mon, 3 Apr 2000 17:41:52 -0400 (EDT) (envelope-from wollman) Date: Mon, 3 Apr 2000 17:41:52 -0400 (EDT) From: Garrett Wollman Message-Id: <200004032141.RAA16068@khavrinen.lcs.mit.edu> To: mjacob@feral.com Cc: FreeBSD-CURRENT Mailing List Subject: Re: Sysctl for CAM SCSI quirks? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I'm not sure I follow this. > This subject has come up before in that tape quirks are really busted, etc.. I don't believe sysctl (at least in the form Brad suggested) is at all the right model. Rather, the kernel should accept a simply-formatted text blob which lists the quirks. This can then be linked into the kernel, or passed via the loader, or edited in place using sysctl. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 15:31: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 6564D37B55C; Mon, 3 Apr 2000 15:30:56 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA30640; Mon, 3 Apr 2000 18:30:43 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/) id PAA02657; Mon, 3 Apr 2000 15:30:40 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Apr 2000 15:30:40 -0700 (PDT) Message-Id: <200004032230.PAA02657@ix.netcom.com> From: Thomas Dean To: kris@FreeBSD.org Cc: freebsd-current@FreeBSD.org In-reply-to: (message from Kris Kennaway on Mon, 3 Apr 2000 13:47:35 -0700 (PDT)) Subject: Re: Top, vmstat, systat, etc. Broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aha! I am loading the kernel directly. 2:da(2,a)/kernel I looked in the archives, but, did not see anything. I am munging with a disk, da1. -current is on da2. 3.4 from the CD on da0. Next week I will have a boot manager again! tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 15:42: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 1477F37BFE7; Mon, 3 Apr 2000 15:41:54 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA05613; Mon, 3 Apr 2000 18:41:47 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/) id PAA00256; Mon, 3 Apr 2000 15:41:44 -0700 (PDT) (envelope-from tomdean) Date: Mon, 3 Apr 2000 15:41:44 -0700 (PDT) Message-Id: <200004032241.PAA00256@ix.netcom.com> From: Thomas Dean To: kris@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG In-reply-to: (message from Kris Kennaway on Mon, 3 Apr 2000 13:47:35 -0700 (PDT)) Subject: Re: Top, vmstat, systat, etc. Broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the reply. Booting directly was the problem. 2:da(2,a)/boot/loader cured the problem. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 15:43: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id BE9AD37B89E for ; Mon, 3 Apr 2000 15:42:48 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (intefix.ai [209.88.68.216]) by cypherpunks.ai (Postfix) with ESMTP id 074A649; Mon, 3 Apr 2000 18:42:47 -0400 (AST) Message-ID: <38E91E53.53547D8F@vangelderen.org> Date: Mon, 03 Apr 2000 18:42:27 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: Nick Hibma , Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? References: <38E8BFD5.3E69DF2A@vangelderen.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 11:59 AM -0400 2000/4/3, Jeroen C. van Gelderen wrote: > > > PERL is not just used by the FreeBSD system, it's also used by many > > applications ran on top of FreeBSD. Those applications are more likely > > to require an up-to-date version of PERL. We for one need the (overly > > late) 64-bit support in PERL. > > MMMkay. Try this: cd /usr/ports/lang/perl && make install Which either gives me two different versions of PERL to worry about or forces me to use an unsupported version for making the world. It's bad enough that I have to work around the sendmail bug in the base system ;-) > This seems to me to be a much better solution, while we wait for > Perl 5.6.x to stablize enough for it to actually be considered for > inclusion in the FreeBSD base. ;-) I don't mind waiting for PERL to stabilize, after all I wouldn't be able to use it myself if it were unstable. But that's a different argument... Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 16:30:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1A07837B516 for ; Mon, 3 Apr 2000 16:30:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA52715; Tue, 4 Apr 2000 08:59:59 +0930 (CST) Date: Tue, 4 Apr 2000 08:59:59 +0930 From: Greg Lehey To: Vallo Kallaste Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000404085959.Y42140@freebie.lemis.com> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> <20000402200254.A69811@myhakas.matti.ee> <20000402210733.A25516@cicely8.cicely.de> <20000403102308.A71481@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000403102308.A71481@myhakas.matti.ee> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 3 April 2000 at 10:23:08 +0200, Vallo Kallaste wrote: > On Sun, Apr 02, 2000 at 09:07:33PM +0200, Bernd Walter wrote: > >> Just to clearify the things... >> Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT? > > Here's the sequence of what I did: > > 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system > built from March 31 sources. First I used striping over two disks and > put /usr filesystem onto it, did overnight testing and all was well. > 2. Same system, same sources plus two same disks. Now I tried raid5 over > four disks and failed to extract pax archive, got deadlock, not panic. > 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I > failed to extract pax archive, got panic. Do you have dumps? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 16:30:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id CF87737B5A1 for ; Mon, 3 Apr 2000 16:30:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA52701; Tue, 4 Apr 2000 08:59:39 +0930 (CST) Date: Tue, 4 Apr 2000 08:59:39 +0930 From: Greg Lehey To: Soren Schmidt Cc: Matthew Dillon , vallo@matti.ee, Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000404085939.X42140@freebie.lemis.com> References: <200004031707.KAA59737@apollo.backplane.com> <200004031723.TAA00179@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004031723.TAA00179@freebsd.dk> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 3 April 2000 at 19:23:34 +0200, Søren Schmidt wrote: > It seems Matthew Dillon wrote: >>> Same story here, but using softupdates or async mounts I can reproduce >>> the hang or panic in less than 60 secs.. >>> >>> Vinum with raid5 is plain broken, include INVARIANTS in the kernel >>> and see why... >> >> Hang on to that thought. As soon as this struct buf mess gets cleared >> up if Greg hasn't figured out where the bug is I'll throw my lot in >> to try to speed-up locating and fixing the problem. > > Well, there is no need to wait, RELENG_4 is _the_ perfect platform > for this, and the problem has to be fixed there as well.... If I can't get a relatively stable -CURRENT Real Soon Now I'll do just that. But it'll take a couple of days to get a RELENG_4 machine built. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 17:39:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 201DE37B74A for ; Mon, 3 Apr 2000 17:39:29 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA53513; Tue, 4 Apr 2000 10:09:11 +0930 (CST) Date: Tue, 4 Apr 2000 10:09:11 +0930 From: Greg Lehey To: Alfred Perlstein Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c Message-ID: <20000404100911.C53037@freebie.lemis.com> References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> <200004022338.QAA51565@apollo.backplane.com> <20000402172349.T21029@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000402172349.T21029@fw.wintelcom.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 2 April 2000 at 17:23:49 -0700, Alfred Perlstein wrote: > * Matthew Dillon [000402 17:04] wrote: >> >> :I did look at the code, struct proc is allocated from a zone, >> :meaning it won't "go away" once allocated, there's no danger in >> :dereferencing p_pptr, I don't get it. >> : >> :-- >> :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] >> :"I have the heart of a child; I keep it in a jar on my desk." >> >> What happens when the parent process exits and the system must >> reassign the parent to process 1? Now think about what happens >> when it occurs on one cpu while another is trying to access the >> ppid. >> >> cpu#1: cpu#2: >> >> read p->p_pptr >> indirect through to get ppid >> (stalls on a cache miss plus, >> due to heavy DMA, stalls on main memory) >> parent process finishes >> exiting, replaces p_pptr >> of children, releases >> struct proc. >> >> struct proc is reused, >> pid is reallocated >> read completes, wrong ppid is returned >> (neither the original ppid nor ppid 1 >> is returned). >> >> In an SMP system you have to assume the worst case, and the worst case >> is that a cpu can stall INDEFINITELY between instructions. > > Good call. > > Ugh, I should think about this more, but i'll just grasp at straws > and suggest that p_pptr is set to volatile variable, and we re-read > it after we snarf the pid from the pointer and make sure it hasn't > changed out from under us. > > Either that or store it in the child's proc struct as well. This seems the obvious solution. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 17:55:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 7AEC137B545 for ; Mon, 3 Apr 2000 17:55:37 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [149.173.6.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id UAA21960; Mon, 3 Apr 2000 20:52:03 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA05915; Mon, 3 Apr 2000 20:51:32 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id UAA06845; Mon, 3 Apr 2000 20:51:32 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <200004040051.UAA06845@dean.pc.sas.com> Subject: Re: Load average calculation? In-Reply-To: <38E8FE5B.CD2FD3E6@cvzoom.net> from Donn Miller at "Apr 3, 2000 04:26:03 pm" To: Donn Miller , Patrick Mau Date: Mon, 3 Apr 2000 20:51:32 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donn Miller wrote: > Patrick Mau wrote: > > On all Unix-like systems I know, the load average is the average mumber > > of processes running during a given time interval. I can't see what use > > it may have to count load for _waiting_ processes. > > > > I/O load is not process load, if a process waits for I/O completion it does > > not use up its timeslice. > > I think we ought to re-examine the definition of load average. By > load, we mean an actual load on the cpu, and waiting processes aren't > really exerting a cpu load. So, by that reasoning I say waiting > processes don't count. In this case, the "waiting" refers to the processes waiting in the _run_ queue, i.e., if the system wasn't so busy, they'd be running more often instead of waiting. In a uniprocessor system, only one process can be running at a time. When that currently running process is swapped away from the cpu, another process from the run queue is selected to run (which is actually an array of queues, lower indexes meaning higher priority). Load average is the average number of processes that are runnable, i.e., sitting in the run queue, over a certain period of time, usually computed for the most recent 1 minute, 5 minute, and 15 minute intervals. I think you guys are mixing up I/O wait with the run queue. The processes are indeed waiting, but they are waiting for a chance to get the CPU, not for someone to press a key on the keyboard or some other external event, without which, the process could not correctly continue until that event occurs. There is a _huge_ difference between the two. And yes, it is a pretty good, simple indicator of system load, and that is all it is really meant to be. If you need something fancier, or more specific to a particular load type, you'd need to roll your own using the abundant statistics that the kernel keeps and makes available. -Brian -- Brian Dean brdean@unx.sas.com SAS Institute Inc. bsd@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 19: 0:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158]) by hub.freebsd.org (Postfix) with ESMTP id E69AA37B758 for ; Mon, 3 Apr 2000 19:00:36 -0700 (PDT) (envelope-from wkt@henry.cs.adfa.edu.au) Received: (from wkt@localhost) by henry.cs.adfa.edu.au (8.9.2/8.9.3) id MAA00911 for freebsd-current@freebsd.org; Tue, 4 Apr 2000 12:00:29 +1000 (EST) From: Warren Toomey Message-Id: <200004040200.MAA00911@henry.cs.adfa.edu.au> Subject: ATA & 82C596 bug in 4.0-RELEASE? To: freebsd-current@freebsd.org Date: Tue, 4 Apr 2000 12:00:29 +1000 (EST) Reply-To: wkt@cs.adfa.edu.au X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Hope this is the right mailing list. I'm expecting I need some patches in - current to fix my problem. ] I tried to install 4.0-RELEASE on a completely new PC system, but the install failed with ATA write errors and resets. I moved the disk to another PC and installed 4.0 via manual disklabels, newfs, bin + src extraction. 4.0 booted fine on this system (a Dell Optiplex GX1). Back on the new system, a 993AS motherboard with VIA 82C596 ATA33 controller, and [25232/16/63] 13Gig disk at ata0-master using UDMA33. It boots and then takes out the root partition, again with ATA write errors and resets. I searched through the -current mailing list archives, rebuilt /, and added this command near the top of /etc/rc: # Ensure stupid IDE controller doesn't do DMA and stuff the filesystem /sbin/sysctl -w hw.atamodes="pio,dma" I see that Soren added some 89C596 support to ata/ata-disk.c on Jan 3, 2000. It looks like this code is in the 4.0-RELEASE support tree. Can anybody tell me if this 89C596 support is still experimental, or alternatively are there any recent patches/changes which I should pick up? I'm happy to cvsup either from 4.0-stable or 4.0-current if it would help to fix this problem. Many thanks in advance for any suggestions! Warren P.S Attached is the dmesg from a successful boot where I set pio mode in /etc/rc. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 root@monster.cdrom.com:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 67043328 (65472K bytes) avail memory = 61100032 (59668K bytes) Preloaded elf kernel "kernel" at 0xc03c0000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 7.2 irq 11 fxp0: port 0xe800-0xe83f mem 0xdd000000-0xdd0fffff,0xdd100000-0xdd100fff irq 10 at device 9.0 on pci0 fxp0: Ethernet address 00:90:27:a4:6a:d2 fxp0: supplying EUI64: 00:90:27:ff:fe:a4:6a:d2 pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 12419MB [25232/16/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0a fxp0: starting DAD for fe80:0001::0290:27ff:fea4:6ad2 fxp0: DAD complete for fe80:0001::0290:27ff:fea4:6ad2 - no duplicates found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 21:20:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 9F57E37B771 for ; Mon, 3 Apr 2000 21:20:05 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id GAA58585; Tue, 4 Apr 2000 06:19:36 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004040419.GAA58585@zibbi.mikom.csir.co.za> Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? In-Reply-To: <200004040200.MAA00911@henry.cs.adfa.edu.au> from Warren Toomey at "Apr 4, 2000 12:00:29 pm" To: wkt@cs.adfa.edu.au Date: Tue, 4 Apr 2000 06:19:36 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I tried to install 4.0-RELEASE on a completely new PC system, but the > install failed with ATA write errors and resets. I moved the disk to another > PC and installed 4.0 via manual disklabels, newfs, bin + src extraction. > 4.0 booted fine on this system (a Dell Optiplex GX1). > > Back on the new system, a 993AS motherboard with VIA 82C596 ATA33 controller, > and [25232/16/63] 13Gig disk at ata0-master using UDMA33. It > boots and then takes out the root partition, again with ATA write errors and > resets. ... > Can anybody tell me if this 89C596 support is still experimental, or > alternatively are there any recent patches/changes which I should pick up? > I'm happy to cvsup either from 4.0-stable or 4.0-current if it would help > to fix this problem. Your question should include the VIA 82C586. :-) The answer will depend on who answer it. If it is Soren or one of the lucky ones that have it working, they will say everything is fine. For the rest of us with machines that don't want to install or that want to eat your disk if you install it somewhere else first, the answer is probably different. :-( John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 22:43:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5781B37B9DF; Mon, 3 Apr 2000 22:43:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA84668; Mon, 3 Apr 2000 22:43:25 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 3 Apr 2000 22:43:24 -0700 (PDT) From: Kris Kennaway To: "Jeroen C. van Gelderen" Cc: Brad Knowles , Nick Hibma , Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: <38E91E53.53547D8F@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Jeroen C. van Gelderen wrote: > Which either gives me two different versions of PERL to worry about or > forces me to use an unsupported version for making the world. It's bad > enough that I have to work around the sendmail bug in the base system > ;-) The issue with perl, that I'm not sure has been made clear during this thread, is that it's a bitch to mangle (or demangle, depending on POV) the build process into one that is compatible with the FreeBSD build infrastructure (namely, building with 'make'). Probably enough has changed with the new version as to invalidate a lot of the current build magic, meaning it would take a significant amount of work to integrate and test (and even then I'm sure it would have lots of annoying "corner cases" which break the build for various people and have to be worked around). If anyone is willing to take on this annoying task, go over to Mark Murray who is probably hiding in the corner over there and make yourself known :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:22:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id AEEFF37B512 for ; Mon, 3 Apr 2000 23:22:18 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id IAA04424; Tue, 4 Apr 2000 08:22:41 +0200 (MET DST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 12cMjA-0004z5-00 for ; Tue, 04 Apr 2000 08:22:16 +0200 Date: Tue, 4 Apr 2000 08:22:16 +0200 From: Szilveszter Adam To: current@freebsd.org Subject: Re: OpenSSL and Apache+ModSSL Message-ID: <20000404082216.A19074@petra.hos.u-szeged.hu> Mail-Followup-To: current@freebsd.org References: <20000403203935.B7244@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from kris@FreeBSD.org on Mon, Apr 03, 2000 at 12:18:28PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 12:18:28PM -0700, Kris Kennaway wrote: > On Mon, 3 Apr 2000, Szilveszter Adam wrote: > > > --- /usr/src/secure/lib/librsaintl/Makefile.old Tue Mar 14 00:25:58 2000 > > +++ /usr/src/secure/lib/librsaintl/Makefile Sun Apr 2 18:27:27 2000 > > @@ -10,6 +10,8 @@ > > CFLAGS+= -I${.OBJDIR} > > +LDADD+= -L${.OBJDIR}/../libcrypto -lcrypto > > + > > # rsaref > > SRCS+= rsa_err.c rsa_eay.c rsa_intlstubs.c > > I'll take a closer look at this tonight and try and commit it to internat > (and freefall), lag willing (if it passes a world build). If someone can > confirm the world build for me in the meantime, it would save me the > trouble. Hi Kris! Are you still there?:-) A succesful make world finished here on RELENG_4. Sorry, no -CURRENT machines to test on:-( I hope it also works for other people... BTW I never figured a 'make buildworld' would last 4 hours on a PII-233 w/ 64M of RAM (all IDE)... but such was the situation yesterday. > > nevertheless. I think this error is due to the fact that not many developers > > had a chance to test international versions too. > > Yep. Well then we, international users should be more active in testing out new changes in /secure and /crypto stuff... I will be paying closer attention then:-) Cheers: Szilveszter ADAM Szeged University Szeged Hungary -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id DCE1A37B982 for ; Mon, 3 Apr 2000 23:24:04 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (ipc379e018.dial.wxs.nl [195.121.224.24]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FSHB4603.250; Tue, 4 Apr 2000 08:24:06 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA61271; Tue, 4 Apr 2000 08:23:52 +0200 (CEST) (envelope-from asmodai) Date: Tue, 4 Apr 2000 08:23:52 +0200 From: Jeroen Ruigrok/Asmodai To: Matthew Dillon Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch Message-ID: <20000404082352.G21619@daemon.ninth-circle.org> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <200004031751.KAA60287@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Apr 03, 2000 at 10:51:49AM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000403 20:05], Matthew Dillon (dillon@apollo.backplane.com) wrote: > >:When I mailed arch@ about this change I got no response from anybody >:but Bruce. >: >:I talked to Kirk about it in Malmø and got his approval. >: >:This is not unplanned. >: >:This is also not untested, I have two complete prototypes behind me. >: >:It is regretable that vinum was broken, and I hope that it is fixed >:with Alfreds changes, one can't win 100% all the time. >: >:Your time would be more productively used by reviewing and testing >:the patch at http://phk.freebsd.dk/misc than by preaching. >: >:As to the debugging of the malloc/free issue in vinum, Sørens suggestion >:to use releng4 sounds downright sensible to me, and I suggest you do >:that. > > I don't think these excuses come close to justifying your commits > or your timing. With all due respect, in some cases it does. -arch: This list was SUPPOSED to be used for this sorta thing. That only bde mailed him and commented, well, tough luck, that's your loss guys. That's what peer review is about. -Kirk: You paraded often enough about Kirk's approval to do things Matt, that point is not valid IMHO. -prototype: I looked at the prototypes and they looked, in my novice eyes, more sane then what we have now. -vinum: with all respect, but with newbus, almost ALL driver-writers had to bite the sour apple in order to get their drivers ready for the changes. And like Poul-Henning and Soren say, use a source tree that isn't cvsupped with these changes to chase your bugs and fix them and then look at the future again. Also, when IS the right time? Judging time and again when somebody does some earthshaking thing with some old existing API's everybody shouts nay and boo and hiss, whilst in fact providing little if nothing productive output in order to substantiate why people are against that change. Like I said in another mail, this is CURRENT, things are expected to break. You want stability of API's, go 3-STABLE. You want a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have your bandages ready. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Veni, Vidi, Vici... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:24:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 5518637B9C1; Mon, 3 Apr 2000 23:24:06 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (ipc379e018.dial.wxs.nl [195.121.224.24]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FSHB4803.252; Tue, 4 Apr 2000 08:24:08 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA61257; Tue, 4 Apr 2000 08:14:41 +0200 (CEST) (envelope-from asmodai) Date: Tue, 4 Apr 2000 08:14:40 +0200 From: Jeroen Ruigrok/Asmodai To: Matthew Dillon Cc: Adrian Chadd , Poul-Henning Kamp , current@freebsd.org Subject: Re: 2nd call for reviews and tests: buf->bio patch Message-ID: <20000404081440.E21619@daemon.ninth-circle.org> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404030757.A53939@ewok.creative.net.au> <200004032134.OAA61603@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200004032134.OAA61603@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, Apr 03, 2000 at 02:34:01PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000404 04:02], Matthew Dillon (dillon@apollo.backplane.com) wrote: >: >:* His timing did suck >:* He's now doing the right thing, at least, instead of committing the >: second patchset without submitting them for peer review > > I disagree. What Poul is doing is committing stuff first, then trying > to get validation after the fact (and in a rather demanding way I might > add) when people complain. He is willing to dig his feet in and spend > weeks arguing over the issue until people get tired enough to either > accept a compromise, or allow his commits to stay in the tree verbatim. > Furthermore, whenever his commit breaks something, it is generally > someone else who has to take up the ball and fix it. I may break the > tree occassionally, but I damn well stay on the front lines and fix > any problems ASAP rather then force other people to fix them for me. In all honesty, this seems to go more about the person Poul-Henning, then his code. Besides, CURRENT does allow for the tree to be broken. I guess Bleeding Edge lost its meaning within the FreeBSD ranks. > This is the third time this has happened. Every time it happens it > creates a huge disruption and every time it happens we end up with > a compromise that does absolute *nothing* to prevent a reoccurance of > the problem. Ehm. Not as if your VM stuff wasn't causing disruption. Needed, granted, but disruptive as well. And ucd-snmp has been broken quite some time (still is?) due to the work. And I know of a lot of people who actively use it. > The commit should not have happened in the first place. My position is > fairly simple: I am getting seriously tired of seeing this repetition > occur every few months, and I would like something *REAL* to be done about > it which will prevent the repetition from occuring in the future. I agree that Poul-Henning could be more subtle at times, but I also understand his motives for doing so. CURRENT is about progress. If we don't start something, we have no chance to every modify it. Every change in a DEVELOPMENT tree thus far has been met by anguish, shouting and calling for the thing to remain, even when the change is for the better or made things more clear and sane. If people want stability, go 3-STABLE or 4-STABLE. 5 is were we break stuff and try to get everything back together in more sane and justified ways. This is not PRODUCTION level stuff, it could one day be, but at the moment it is not. That doesn't mean of course that peer review isn't necessary, in fact its good, becase it will catch pitfalls you probably wouldn't have thought of. But in all honesty, I see ego's getting more and more in the way of code. Saddening. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Veni, Vidi, Vici... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:24:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 609E737B9A3; Mon, 3 Apr 2000 23:24:05 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (ipc379e018.dial.wxs.nl [195.121.224.24]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FSHB4703.251; Tue, 4 Apr 2000 08:24:07 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA61264; Tue, 4 Apr 2000 08:15:53 +0200 (CEST) (envelope-from asmodai) Date: Tue, 4 Apr 2000 08:15:53 +0200 From: Jeroen Ruigrok/Asmodai To: Adrian Chadd Cc: Matthew Dillon , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch Message-ID: <20000404081552.F21619@daemon.ninth-circle.org> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404030757.A53939@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000404030757.A53939@ewok.creative.net.au>; from adrian@freebsd.org on Tue, Apr 04, 2000 at 03:07:59AM +0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000404 04:01], Adrian Chadd (adrian@freebsd.org) wrote: >This really isn't constructive. I haven't looked at the patchset that >phk has posted up but I think it'd be more useful if people gave >comments about the changes and their usefulness rather than the bickering >going on now. Agreed. That's what peer review is about. Commenting on those changes/patchsets in technical justified ways. Don't forget to leave ego at home... =) -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Veni, Vidi, Vici... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:25:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id AF6FA37BF8B for ; Mon, 3 Apr 2000 23:25:06 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0BE021CD7; Mon, 3 Apr 2000 23:25:05 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: Message from Gary Jennejohn of "Mon, 03 Apr 2000 21:32:51 +0200." <200004031932.VAA23846@peedub.muc.de> Date: Mon, 03 Apr 2000 23:25:05 -0700 From: Peter Wemm Message-Id: <20000404062505.0BE021CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Jennejohn wrote: > Bruce Evans writes: > >On Mon, 3 Apr 2000, Gary Jennejohn wrote: > > > >> Bruce Evans writes: > >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: > >> >> I think we should nuke csu_hdr since it's not used anywhere. Is that > >> >> what you really mean ? > >> > > >> >Yes. I'm trying the following patch. Only tested at compile time. > >> > > >> [patch snipped] > >> > >> Thank you, Bruce ! This is pretty much the same patch I tested. > >> > >> So, should I commit it ? > > > >If you have tested it :-). > > > > I'm running with the change right now. No problems. I would prefer that we did this: #define MAX_LEN (min(128, MLEN)) or something like that. This should stop Bad Things happening if somebody recompiles with MLEN set specifically to 128 (and is an ideal MFC candidate for 4.x for when people set MLEN to 256 over there). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:40:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from kg.ops.uunet.co.za (kg.ops.uunet.co.za [196.31.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 2131237B813; Mon, 3 Apr 2000 23:40:22 -0700 (PDT) (envelope-from khetan@uunet.co.za) Received: from bofh.ops.uunet.co.za (bofh.ops.uunet.co.za [196.31.1.35]) by kg.ops.uunet.co.za (Postfix) with ESMTP id 60EAC16E7A; Tue, 4 Apr 2000 08:40:18 +0200 (SAST) Received: by bofh.ops.uunet.co.za (Postfix, from userid 1000) id D05CE5BCE; Tue, 4 Apr 2000 08:40:17 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by bofh.ops.uunet.co.za (Postfix) with ESMTP id BDC351EE3; Tue, 4 Apr 2000 08:40:17 +0200 (SAST) Date: Tue, 4 Apr 2000 08:40:16 +0200 (SAST) From: Khetan Gajjar X-Sender: khetan@bofh.ops.uunet.co.za To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: OpenSSL and Apache+ModSSL In-Reply-To: Message-ID: X-Cell: +27 82 416 0160 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around Yesterday, "Kris Kennaway" wrote : KK> I'll take a closer look at this tonight and try and commit it to internat KK> (and freefall), lag willing (if it passes a world build). If someone can KK> confirm the world build for me in the meantime, it would save me the KK> trouble. I didn't apply the patch, but hand pasted the line, and it survived a make world -DNOCLEAN and more importantly, works! Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za * http://www.freebsd.org * information at System Administration * http://office.os.org.za * kg+details@uunet.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 3 23:46:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1AC4137B9DF for ; Mon, 3 Apr 2000 23:46:06 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA94288; Tue, 4 Apr 2000 08:45:11 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004040645.IAA94288@freebsd.dk> Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? In-Reply-To: <200004040419.GAA58585@zibbi.mikom.csir.co.za> from John Hay at "Apr 4, 2000 06:19:36 am" To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 4 Apr 2000 08:45:11 +0200 (CEST) Cc: wkt@cs.adfa.edu.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John Hay wrote: > > > > I tried to install 4.0-RELEASE on a completely new PC system, but the > > install failed with ATA write errors and resets. I moved the disk to another > > PC and installed 4.0 via manual disklabels, newfs, bin + src extraction. > > 4.0 booted fine on this system (a Dell Optiplex GX1). > > > > Back on the new system, a 993AS motherboard with VIA 82C596 ATA33 controller, > > and [25232/16/63] 13Gig disk at ata0-master using UDMA33. It > > boots and then takes out the root partition, again with ATA write errors and > > resets. > ... > > Can anybody tell me if this 89C596 support is still experimental, or > > alternatively are there any recent patches/changes which I should pick up? > > I'm happy to cvsup either from 4.0-stable or 4.0-current if it would help > > to fix this problem. Yup VIA has a new version of the 82C596 chip, in their usual visdom they change the interface, but not the chip ID (I'll nominate VIA for the way they do versioning). However I have worked out the solution with Chris Wiener , that had this problem also and kindly helped testing. Se the patch belowm try it and let me know.. > Your question should include the VIA 82C586. :-) The answer will depend > on who answer it. If it is Soren or one of the lucky ones that have it > working, they will say everything is fine. For the rest of us with > machines that don't want to install or that want to eat your disk if you > install it somewhere else first, the answer is probably different. :-( Woa! I havn't seen any reports of the '586 not working, please point me at them. I've seen a couble of cases where it was other known bad HW that caused trouble. So by all means please forward any problem to me, together with verbose boot logs etc and I'll take a look at it, if there is a problem it should be fixed. However if it is on HW I dont have access to here, I need someone that has a box that can be used for testing, ie with filesystems that can be restored/ reinstalled etc etc and have the time and patience to work with me one the problem. Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.50.2.2 diff -u -r1.50.2.2 ata-all.c --- ata-all.c 2000/03/18 22:26:28 1.50.2.2 +++ ata-all.c 2000/04/03 09:50:43 @@ -211,8 +211,8 @@ int32_t irqcnt; }; -static int32_t -ata_find_dev(device_t dev, int32_t type) +int32_t +ata_find_dev(device_t dev, int32_t type, int32_t revid) { device_t *children, child; int nchildren, i; @@ -226,7 +226,8 @@ /* check that it's on the same silicon and the device we want */ if (pci_get_slot(dev) == pci_get_slot(child) && pci_get_vendor(child) == (type & 0xffff) && - pci_get_device(child) == ((type & 0xffff0000) >> 16)) { + pci_get_device(child) == ((type & 0xffff0000) >> 16) && + pci_get_revid(child) >= revid) { free(children, M_TEMP); return 1; } @@ -263,11 +264,13 @@ return "AcerLabs Aladdin ATA33 controller"; case 0x05711106: - if (ata_find_dev(dev, 0x05861106)) + if (ata_find_dev(dev, 0x05861106, 0)) return "VIA 82C586 ATA33 controller"; - if (ata_find_dev(dev, 0x05961106)) + if (ata_find_dev(dev, 0x05961106, 0x12)) + return "VIA 82C596B ATA66 controller"; + if (ata_find_dev(dev, 0x05961106, 0)) return "VIA 82C596 ATA33 controller"; - if (ata_find_dev(dev, 0x06861106)) + if (ata_find_dev(dev, 0x06861106, 0)) return "VIA 82C686 ATA66 controller"; return "VIA Apollo ATA controller"; @@ -428,8 +431,9 @@ pci_write_config(dev, 0x60, DEV_BSIZE, 2); pci_write_config(dev, 0x68, DEV_BSIZE, 2); - /* prepare for ATA-66 on the 82C686 */ - if (ata_find_dev(dev, 0x06861106)) { + /* prepare for ATA-66 on the 82C686 and rev 0x12 and newer 82C596's */ + if (ata_find_dev(dev, 0x06861106, 0) || + ata_find_dev(dev, 0x05961106, 0x12)) { pci_write_config(dev, 0x50, pci_read_config(dev, 0x50, 4) | 0x070f070f, 4); } @@ -697,11 +701,11 @@ scp->unit = (uintptr_t) device_get_ivars(dev); /* set the chiptype to the hostchip ID, makes life easier */ - if (ata_find_dev(device_get_parent(dev), 0x05861106)) + if (ata_find_dev(device_get_parent(dev), 0x05861106, 0)) scp->chiptype = 0x05861106; - else if (ata_find_dev(device_get_parent(dev), 0x05961106)) + else if (ata_find_dev(device_get_parent(dev), 0x05961106, 0)) scp->chiptype = 0x05961106; - else if (ata_find_dev(device_get_parent(dev), 0x06861106)) + else if (ata_find_dev(device_get_parent(dev), 0x06861106, 0)) scp->chiptype = 0x06861106; else scp->chiptype = pci_get_devid(device_get_parent(dev)); Index: ata-all.h =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.h,v retrieving revision 1.26 diff -u -r1.26 ata-all.h --- ata-all.h 2000/03/05 16:52:23 1.26 +++ ata-all.h 2000/04/02 20:00:47 @@ -326,6 +326,9 @@ int ata_pmode(struct ata_params *); int ata_wmode(struct ata_params *); int ata_umode(struct ata_params *); +#if NPCI > 0 +int32_t ata_find_dev(device_t, int32_t, int32_t); +#endif void ata_dmainit(struct ata_softc *, int32_t, int32_t, int32_t, int32_t); int32_t ata_dmasetup(struct ata_softc *, int32_t, int8_t *, int32_t, int32_t); Index: ata-dma.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v retrieving revision 1.35 diff -u -r1.35 ata-dma.c --- ata-dma.c 2000/03/05 16:52:24 1.35 +++ ata-dma.c 2000/04/03 10:00:30 @@ -280,7 +280,24 @@ /* we could set PIO mode timings, but we assume the BIOS did that */ break; + case 0x74091022: /* AMD 756 */ + if (udmamode >= 4) { + error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, + ATA_UDMA4, ATA_C_F_SETXFER, ATA_WAIT_READY); + if (bootverbose) + ata_printf(scp, device, + "%s setting up UDMA4 mode on AMD chip\n", + (error) ? "failed" : "success"); + if (!error) { + pci_write_config(parent, 0x53 - devno, 0xc3, 1); + scp->mode[ATA_DEV(device)] = ATA_UDMA4; + return; + } + } + goto via_82c586; + case 0x06861106: /* VIA 82C686 */ +via_82c686: if (udmamode >= 4) { error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, ATA_UDMA4, ATA_C_F_SETXFER, ATA_WAIT_READY); @@ -309,25 +326,14 @@ } goto via_generic; - case 0x74091022: /* AMD 756 */ - if (udmamode >= 4) { - error = ata_command(scp, device, ATA_C_SETFEATURES, 0, 0, 0, - ATA_UDMA4, ATA_C_F_SETXFER, ATA_WAIT_READY); - if (bootverbose) - ata_printf(scp, device, - "%s setting up UDMA4 mode on AMD chip\n", - (error) ? "failed" : "success"); - if (!error) { - pci_write_config(parent, 0x53 - devno, 0xc3, 1); - scp->mode[ATA_DEV(device)] = ATA_UDMA4; - return; - } - } + case 0x05961106: /* VIA 82C596 */ + /* 82c596 revision >= 0x12 is like the 82c686 */ + if (ata_find_dev(parent, 0x05961106, 0x12)) + goto via_82c686; /* FALLTHROUGH */ - case 0x05961106: /* VIA 82C596 */ case 0x05861106: /* VIA 82C586 */ - +via_82c586: /* UDMA2 mode only on 82C586 > rev1, 82C596, AMD 756 */ if ((udmamode >= 2 && scp->chiptype == 0x05861106 && pci_read_config(scp->dev, 0x08, 1) >= 0x01) || -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 0: 3:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 7BC1237B512 for ; Tue, 4 Apr 2000 00:03:29 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id IAA25879; Tue, 4 Apr 2000 08:59:41 +0200 (CEST) Message-Id: <200004040659.IAA25879@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Peter Wemm Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 04 Apr 2000 08:25:51 +0200." <20000404062505.0BE021CD7@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 08:59:41 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: >Gary Jennejohn wrote: >> Bruce Evans writes: >> >On Mon, 3 Apr 2000, Gary Jennejohn wrote: >> > >> >> Bruce Evans writes: >> >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: >> >> >> I think we should nuke csu_hdr since it's not used anywhere. Is that >> >> >> what you really mean ? >> >> > >> >> >Yes. I'm trying the following patch. Only tested at compile time. >> >> > >> >> [patch snipped] >> >> >> >> Thank you, Bruce ! This is pretty much the same patch I tested. >> >> >> >> So, should I commit it ? >> > >> >If you have tested it :-). >> > >> >> I'm running with the change right now. No problems. > >I would prefer that we did this: > >#define MAX_LEN (min(128, MLEN)) > >or something like that. This should stop Bad Things happening if >somebody recompiles with MLEN set specifically to 128 (and is an ideal >MFC candidate for 4.x for when people set MLEN to 256 over there). > This is a pretty good idea, too. But I already deleted csu_hdr in -current. It would be easy enough to back out the change if there's consensus. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 0:16:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id E919037B57A for ; Tue, 4 Apr 2000 00:16:51 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 841C31CD7; Tue, 4 Apr 2000 00:16:51 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: MLEN and crashes In-Reply-To: Message from Gary Jennejohn of "Tue, 04 Apr 2000 08:59:41 +0200." <200004040659.IAA25879@peedub.muc.de> Date: Tue, 04 Apr 2000 00:16:51 -0700 From: Peter Wemm Message-Id: <20000404071651.841C31CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Jennejohn wrote: > Peter Wemm writes: > >Gary Jennejohn wrote: > >> Bruce Evans writes: > >> >On Mon, 3 Apr 2000, Gary Jennejohn wrote: > >> > > >> >> Bruce Evans writes: > >> >> >On Sun, 2 Apr 2000, Gary Jennejohn wrote: > >> >> >> I think we should nuke csu_hdr since it's not used anywhere. Is that > >> >> >> what you really mean ? > >> >> > > >> >> >Yes. I'm trying the following patch. Only tested at compile time. > >> >> > > >> >> [patch snipped] > >> >> > >> >> Thank you, Bruce ! This is pretty much the same patch I tested. > >> >> > >> >> So, should I commit it ? > >> > > >> >If you have tested it :-). > >> > > >> > >> I'm running with the change right now. No problems. > > > >I would prefer that we did this: > > > >#define MAX_LEN (min(128, MLEN)) > > > >or something like that. This should stop Bad Things happening if > >somebody recompiles with MLEN set specifically to 128 (and is an ideal > >MFC candidate for 4.x for when people set MLEN to 256 over there). > > > > This is a pretty good idea, too. But I already deleted csu_hdr in -current. > It would be easy enough to back out the change if there's consensus. No, leave csu_hdr deleted. I am only talking about also changing the #define MAX_LEN to something that's safe even if MLEN is overridden. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 1:16:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 73D9637B6FE; Tue, 4 Apr 2000 01:16:30 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-31.iptelecom.net.ua [212.9.227.95]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA15846; Tue, 4 Apr 2000 11:22:55 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id LAA18542; Tue, 4 Apr 2000 11:14:59 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38E9A486.9186FDC4@altavista.net> Date: Tue, 04 Apr 2000 11:15:02 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org, brian@freebsd.org Subject: PPP segfaulting Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The ppp built from the just cvsup'ed -current sources segfaulting. Following is backtrace. Please contact me of some additional debugging info will be necessary. -Maxim PPP ON vega> Program received signal SIGSEGV, Segmentation fault. 0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, slstat=0x808900c, compress_cid=0) at slcompress.c:177 177 if (ip->ip_src.s_addr != cs->cs_ip.ip_src.s_addr || (gdb) bt #0 0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, slstat=0x808900c, compress_cid=0) at slcompress.c:177 #1 0x8071f70 in vj_LayerPush (bundle=0x80853a0, l=0x8093000, bp=0x809e000, pri=0, proto=0xbfbff41e) at vjcomp.c:73 #2 0x8064e0f in link_PushPacket (l=0x8093000, bp=0x809e000, b=0x80853a0, pri=0, proto=33) at link.c:225 #3 0x805fe46 in ip_PushPacket (l=0x8093000, bundle=0x80853a0) at ip.c:733 #4 0x804bf5e in bundle_FillQueues (bundle=0x80853a0) at bundle.c:414 #5 0x804bfc7 in bundle_UpdateSet (d=0x80853a0, r=0xbfbff5e8, w=0xbfbff568, e=0xbfbff4e8, n=0xbfbff4e0) at bundle.c:437 #6 0x80670af in DoLoop (bundle=0x80853a0) at main.c:517 #7 0x8067028 in main (argc=2, argv=0xbfbff804) at main.c:495 #8 0x804a85d in _start () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 1:39: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id BDF2C37B733 for ; Tue, 4 Apr 2000 01:38:48 -0700 (PDT) (envelope-from oogali@intranova.net) Received: (qmail 85127 invoked from network); 4 Apr 2000 08:42:45 -0000 Received: from localhost.abuselabs.com (HELO localhost) (missnglnk@127.0.0.1) by localhost.abuselabs.com with SMTP; 4 Apr 2000 08:42:45 -0000 Date: Tue, 4 Apr 2000 04:42:44 -0400 (EDT) From: Omachonu Ogali To: freebsd-current@freebsd.org Subject: Sysctl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know whether to hand this to -doc or here, so I'll take the risk of here, patch simply adds comments to sysctl variables. Started work on netinet, hopefully I'll have more later on in the day. (It's 4:40am right now). -- snip -- --- if_ether.c.orig Tue Apr 4 04:14:02 2000 +++ if_ether.c Tue Apr 4 04:18:55 2000 @@ -72,3 +72,3 @@ SYSCTL_DECL(_net_link_ether); -SYSCTL_NODE(_net_link_ether, PF_INET, inet, CTLFLAG_RW, 0, ""); +SYSCTL_NODE(_net_link_ether, PF_INET, inet, CTLFLAG_RW, 0, "Ethernet Link Level"); @@ -80,7 +80,7 @@ SYSCTL_INT(_net_link_ether_inet, OID_AUTO, prune_intvl, CTLFLAG_RW, - &arpt_prune, 0, ""); + &arpt_prune, 0, "Seconds before ARP cache is cleaned."); SYSCTL_INT(_net_link_ether_inet, OID_AUTO, max_age, CTLFLAG_RW, - &arpt_keep, 0, ""); + &arpt_keep, 0, "Seconds a resolved ARP entry is valid."); SYSCTL_INT(_net_link_ether_inet, OID_AUTO, host_down_time, CTLFLAG_RW, - &arpt_down, 0, ""); + &arpt_down, 0, "Seconds an unresolved ARP entry is valid."); @@ -106,7 +106,7 @@ SYSCTL_INT(_net_link_ether_inet, OID_AUTO, maxtries, CTLFLAG_RW, - &arp_maxtries, 0, ""); + &arp_maxtries, 0, "Maximum ARP requests generated for one destination."); SYSCTL_INT(_net_link_ether_inet, OID_AUTO, useloopback, CTLFLAG_RW, - &useloopback, 0, ""); + &useloopback, 0, "Use loopback interface for local traffic."); SYSCTL_INT(_net_link_ether_inet, OID_AUTO, proxyall, CTLFLAG_RW, - &arp_proxyall, 0, ""); + &arp_proxyall, 0, "Enable ARP Proxying."); --- in_gif.c.orig Tue Apr 4 04:24:36 2000 +++ in_gif.c Tue Apr 4 04:25:00 2000 @@ -84,3 +84,3 @@ SYSCTL_INT(_net_inet_ip, IPCTL_GIF_TTL, gifttl, CTLFLAG_RW, - &ip_gif_ttl, 0, ""); + &ip_gif_ttl, 0, "GIF tunnel default time-to-live setting."); --- ip_icmp.c.orig Tue Apr 4 03:59:05 2000 +++ ip_icmp.c Tue Apr 4 04:26:16 2000 @@ -81,3 +81,3 @@ SYSCTL_INT(_net_inet_icmp, ICMPCTL_MASKREPL, maskrepl, CTLFLAG_RW, - &icmpmaskrepl, 0, ""); + &icmpmaskrepl, 0, "Allow transmission of ICMP mask replies."); @@ -85,3 +85,3 @@ SYSCTL_INT(_net_inet_icmp, OID_AUTO, drop_redirect, CTLFLAG_RW, - &drop_redirect, 0, ""); + &drop_redirect, 0, "Discard all received ICMP redirects."); @@ -89,3 +89,3 @@ SYSCTL_INT(_net_inet_icmp, OID_AUTO, log_redirect, CTLFLAG_RW, - &log_redirect, 0, ""); + &log_redirect, 0, "Log all received ICMP redirects"); @@ -100,3 +100,3 @@ SYSCTL_INT(_net_inet_icmp, ICMPCTL_ICMPLIM, icmplim, CTLFLAG_RW, - &icmplim, 0, ""); + &icmplim, 0, "ICMP error responses allowed per second."); #else @@ -105,3 +105,3 @@ SYSCTL_INT(_net_inet_icmp, ICMPCTL_ICMPLIM, icmplim, CTLFLAG_RD, - &icmplim, 0, ""); + &icmplim, 0, "ICMP error responses allowed per second."); @@ -115,3 +115,3 @@ SYSCTL_INT(_net_inet_icmp, OID_AUTO, bmcastecho, CTLFLAG_RW, - &icmpbmcastecho, 0, ""); + &icmpbmcastecho, 0, "Reply to ICMP echoes sent to broadcast addresses."); --- in.c.orig Tue Apr 4 04:21:07 2000 +++ in.c Tue Apr 4 04:21:29 2000 @@ -72,3 +72,3 @@ SYSCTL_INT(_net_inet_ip, OID_AUTO, subnets_are_local, CTLFLAG_RW, - &subnetsarelocal, 0, ""); + &subnetsarelocal, 0, "All subnets of the local network are considered local."); --- ip_input.c.orig Tue Apr 4 04:28:23 2000 +++ ip_input.c Tue Apr 4 04:28:52 2000 @@ -169,3 +169,3 @@ SYSCTL_INT(_net_inet_ip, OID_AUTO, stealth, CTLFLAG_RW, - &ipstealth, 0, ""); + &ipstealth, 0, "Allow forwarding of packets without TTL modification."); #endif --- udp_usrreq.c.orig Tue Apr 4 04:31:24 2000 +++ udp_usrreq.c Tue Apr 4 04:32:24 2000 @@ -91,3 +91,3 @@ SYSCTL_INT(_net_inet_udp, UDPCTL_CHECKSUM, checksum, CTLFLAG_RW, - &udpcksum, 0, ""); + &udpcksum, 0, "Send UDP checksums."); -- snip -- -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 1:55:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from crucian.comset.net (crucian.comset.net [213.172.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A04C37B65C for ; Tue, 4 Apr 2000 01:55:16 -0700 (PDT) (envelope-from kong@comset.net) Received: from localhost (kong@localhost) by crucian.comset.net (8.9.3/8.8.7) with ESMTP id MAA65205 for ; Tue, 4 Apr 2000 12:55:12 +0400 (MSD) Date: Tue, 4 Apr 2000 12:55:12 +0400 (MSD) From: Hostas Red To: current@freebsd.org Subject: world broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Is the world broken or I've missed something important? ===> gnu/usr.bin/groff/lkbib cc -O -pipe -I/usr/src/gnu/usr.bin/groff/lkbib/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/lkbib/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/i386/usr/include -o lkbib lkbib.o /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libgroff/libgroff.a -lm lkbib.o: In function `main': lkbib.o(.text+0x5a): undefined reference to `search_list::search_list(void)' lkbib.o(.text+0x9a): undefined reference to `linear_ignore_fields' lkbib.o(.text+0xfe): undefined reference to `linear_truncate_len' lkbib.o(.text+0x140): undefined reference to `search_list::add_file(char const *, int)' lkbib.o(.text+0x1bf): undefined reference to `search_list::add_file(char const *, int)' lkbib.o(.text+0x1ce): undefined reference to `search_list::nfiles(void) const' lkbib.o(.text+0x286): undefined reference to `search_list_iterator::search_list_iterator(search_list *, char const *)' lkbib.o(.text+0x35e): undefined reference to `search_list_iterator::next(char const **, int *, reference_id *)' lkbib.o(.text+0x37f): undefined reference to `search_list_iterator::~search_list_iterator(void)' lkbib.o(.text+0x38d): undefined reference to `search_list::~search_list(void)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(index.o): In function `index_search_item::index_search_item(char const *, int)': index.o(.text+0x15): undefined reference to `search_item::search_item(char const *, int)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(index.o): In function `index_search_item::~index_search_item(void)': index.o(.text+0x171): undefined reference to `search_item::~search_item(void)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(index.o): In function `index_search_item_iterator::~index_search_item_iterator(void)': index.o(.text+0x8c7): undefined reference to `search_item_iterator::~search_item_iterator(void)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(index.o): In function `index_search_item::add_out_of_date_file(int, char const *, int)': index.o(.text+0x1457): undefined reference to `search_item::is_named(char const *) const' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(linear.o): In function `linear_search_item::linear_search_item(char const *, int)': linear.o(.text+0xaa1): undefined reference to `search_item::search_item(char const *, int)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(linear.o): In function `linear_search_item::~linear_search_item(void)': linear.o(.text+0xae9): undefined reference to `search_item::~search_item(void)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(linear.o): In function `linear_search_item_iterator::~linear_search_item_iterator(void)': linear.o(.text+0xb6c): undefined reference to `search_item_iterator::~search_item_iterator(void)' /usr/obj/usr/src/gnu/usr.bin/groff/lkbib/../libbib/libbib.a(linear.o)(.gnu.linkonce.d._vt$18linear_search_item+0x1c): undefined reference to `search_item::next_filename_id(void) const' *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff/lkbib. *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Adios, /KONG ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || UNiX Systems Administrator, ComSet ISP ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 2: 0:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.nildram.co.uk (mercury.nildram.co.uk [195.112.4.37]) by hub.freebsd.org (Postfix) with ESMTP id 9B57B37BA09 for ; Tue, 4 Apr 2000 02:00:22 -0700 (PDT) (envelope-from freebsd@unix-consult.com) Received: from nermal.unix-consult.com (tgeusch.dial.nildram.co.uk [195.149.29.39]) by mercury.nildram.co.uk (8.10.0.Beta12/8.10.0.Beta10) with ESMTP id e3493dt28440 for ; Tue, 4 Apr 2000 10:03:43 +0100 Received: (qmail 42635 invoked from network); 4 Apr 2000 06:41:47 -0000 Received: from odie.unix-consult.com (192.168.0.2) by nermal.unix-consult.com with SMTP; 4 Apr 2000 06:41:47 -0000 Received: (qmail 320 invoked by uid 1002); 4 Apr 2000 06:40:34 -0000 Date: Tue, 4 Apr 2000 07:40:34 +0100 From: Timo Geusch To: current@freebsd.org Subject: UNIONFS Message-ID: <20000404074034.A290@odie.unix-consult.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here be dragons, I know :-). Got myself a nice juicy & reproducable crash here, so I thought I might as well try to track down this problem. But before I start,is anyone else working on this one? I'd hate to waste my not exactly ample time trying to duplicate somebody else's work. Regards, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 2: 3:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id C2F7E37B5B2; Tue, 4 Apr 2000 02:03:35 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA26278; Tue, 4 Apr 2000 11:01:32 +0200 (CEST) Message-Id: <200004040901.LAA26278@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Maxim Sobolev Cc: current@FreeBSD.ORG, brian@FreeBSD.ORG Subject: Re: PPP segfaulting Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 04 Apr 2000 11:15:02 +0300." <38E9A486.9186FDC4@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 11:01:32 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Sobolev writes: >Hi, > >The ppp built from the just cvsup'ed -current sources segfaulting. Following i >s >backtrace. Please contact me of some additional debugging info will be >necessary. > >-Maxim > >PPP ON vega> >Program received signal SIGSEGV, Segmentation fault. >0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, > slstat=0x808900c, compress_cid=0) at slcompress.c:177 >177 if (ip->ip_src.s_addr != cs->cs_ip.ip_src.s_addr || >(gdb) bt >#0 0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, > slstat=0x808900c, compress_cid=0) at slcompress.c:177 >#1 0x8071f70 in vj_LayerPush (bundle=0x80853a0, l=0x8093000, bp=0x809e000, > pri=0, proto=0xbfbff41e) at vjcomp.c:73 >#2 0x8064e0f in link_PushPacket (l=0x8093000, bp=0x809e000, b=0x80853a0, > pri=0, proto=33) at link.c:225 >#3 0x805fe46 in ip_PushPacket (l=0x8093000, bundle=0x80853a0) at ip.c:733 >#4 0x804bf5e in bundle_FillQueues (bundle=0x80853a0) at bundle.c:414 >#5 0x804bfc7 in bundle_UpdateSet (d=0x80853a0, r=0xbfbff5e8, w=0xbfbff568, > e=0xbfbff4e8, n=0xbfbff4e0) at bundle.c:437 >#6 0x80670af in DoLoop (bundle=0x80853a0) at main.c:517 >#7 0x8067028 in main (argc=2, argv=0xbfbff804) at main.c:495 >#8 0x804a85d in _start () > Sorry, it looks like removing csu_hdr wasn't such a good idea after all. Apparently the m_pullup of the mbuf makes it necessary to have at least 128 bytes available in cspace. My bad :( I'll back out my changes. Try this patch, which basically reverts my modification: --- /usr/src/usr.sbin/ppp/slcompress.h.orig Tue Apr 4 10:48:59 2000 +++ /u8/tmp/src/usr.sbin/ppp/slcompress.h Sat Aug 28 03:18:44 1999 @@ -16,7 +16,7 @@ * IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED * WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. * - * $FreeBSD: src/usr.sbin/ppp/slcompress.h,v 1.14 2000/04/03 19:54:33 gj Exp $ + * $FreeBSD: src/usr.sbin/ppp/slcompress.h,v 1.13 1999/08/28 01:18:44 peter Exp $ * * Van Jacobson (van@helios.ee.lbl.gov), Dec 31, 1989: * - Initial distribution. @@ -102,8 +102,14 @@ u_short cs_hlen; /* size of hdr (receive only) */ u_char cs_id; /* connection # associated with this state */ u_char cs_filler; - struct ip cs_ip; /* ip/tcp hdr from most recent packet */ + union { + char csu_hdr[MAX_HDR]; + struct ip csu_ip; /* ip/tcp hdr from most recent packet */ + } slcs_u; }; + +#define cs_ip slcs_u.csu_ip +#define cs_hdr slcs_u.csu_hdr /* * all the state data for one serial line (we need one of these --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 2:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9628337B6C0; Tue, 4 Apr 2000 02:14:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA04166; Tue, 4 Apr 2000 02:14:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 4 Apr 2000 02:14:15 -0700 (PDT) From: Kris Kennaway To: Timo Geusch Cc: current@freebsd.org Subject: Re: UNIONFS In-Reply-To: <20000404074034.A290@odie.unix-consult.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Timo Geusch wrote: > Here be dragons, I know :-). Got myself a nice juicy & reproducable > crash here, so I thought I might as well try to track down this > problem. But before I start,is anyone else working on this one? I'd > hate to waste my not exactly ample time trying to duplicate somebody > else's work. Frankly, unless you have the time to fix unionfs completely I wouldn't bother. We know it's broken, whats needed is someone with a good handle on the VFS code to sit down and spend a week or so to fix it. On the other hand, if that's you then go for it (you'd certainly learn a lot of useful things in the process) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 2:27:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id A942E37B740 for ; Tue, 4 Apr 2000 02:27:15 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id CF5802CE5C; Tue, 4 Apr 2000 11:27:11 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 56F6C1C562B; Tue, 4 Apr 2000 11:27:13 +0200 (EET) Date: Tue, 4 Apr 2000 11:27:13 +0200 From: Vallo Kallaste To: Greg Lehey Cc: Bernd Walter , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000404112713.A75374@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de> <20000402200254.A69811@myhakas.matti.ee> <20000402210733.A25516@cicely8.cicely.de> <20000403102308.A71481@myhakas.matti.ee> <20000404085959.Y42140@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000404085959.Y42140@freebie.lemis.com>; from grog@lemis.com on Tue, Apr 04, 2000 at 08:59:59AM +0930 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000 at 08:59:59AM +0930, Greg Lehey wrote: > Do you have dumps? No, for obvious reasons explained earlier. I'll spend some time today afternoon and set up suitable environment for getting dumps and debugging. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 2:47:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ferret.lmh.ox.ac.uk (ferret.lmh.ox.ac.uk [163.1.138.204]) by hub.freebsd.org (Postfix) with SMTP id 11B6537B5EF for ; Tue, 4 Apr 2000 02:47:15 -0700 (PDT) (envelope-from xelah@ferret.lmh.ox.ac.uk) Received: (qmail 10089 invoked by uid 2036); 4 Apr 2000 09:47:02 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Apr 2000 09:47:02 -0000 Date: Tue, 4 Apr 2000 10:47:02 +0100 (BST) From: Alex Hayward To: current@FreeBSD.ORG Subject: Re: Load average calculation? In-Reply-To: <00040316084601.08733@nomad.dataplex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Richard Wackerbarth wrote: > On Mon, 03 Apr 2000, Donn Miller wrote: > > > I think we ought to re-examine the definition of load average. By > > load, we mean an actual load on the cpu, and waiting processes aren't > > really exerting a cpu load. So, by that reasoning I say waiting > > processes don't count. > > I think you have an incorrect (incomplete) definition. > > Traditionally, the load was the number of processes WANTING to run. > Tasks which are waiting for "user" I/O are excluded. > However, tasks waiting to be swapped in should be counted. This sounds to me like the right approach from point of view of a program like sendmail that reacts to load average. If you get in to a position in which the system is spending all of its time accessing the disc (so that the number of processes actually USING the CPU is quite low 'cos they are all waiting for pages to be swapped back in) is launching off yet more work /really/ the right thing to do? If all it does is result in even more thrashing then couldn't that actually *cut* the load average as calculated using the first of those definitions and push the system even further into the quagmire? OK, so you could easily argue that load average is a far from perfect measure for something of this sort but the second definition does sound more useful IMHO...it gives a better measure of the number of processes which can't yet complete their next chunk of work because of limited system resources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 3:20: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 84E8F37B740 for ; Tue, 4 Apr 2000 03:19:46 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA65929; Tue, 4 Apr 2000 12:19:03 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004041019.MAA65929@zibbi.mikom.csir.co.za> Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? In-Reply-To: <200004040645.IAA94288@freebsd.dk> from Soren Schmidt at "Apr 4, 2000 08:45:11 am" To: sos@freebsd.dk (Soren Schmidt) Date: Tue, 4 Apr 2000 12:19:03 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > I tried to install 4.0-RELEASE on a completely new PC system, but the > > > install failed with ATA write errors and resets. I moved the disk to another > > > PC and installed 4.0 via manual disklabels, newfs, bin + src extraction. > > > 4.0 booted fine on this system (a Dell Optiplex GX1). > > > > > > Back on the new system, a 993AS motherboard with VIA 82C596 ATA33 controller, > > > and [25232/16/63] 13Gig disk at ata0-master using UDMA33. It > > > boots and then takes out the root partition, again with ATA write errors and > > > resets. > > ... > > > Can anybody tell me if this 89C596 support is still experimental, or > > > alternatively are there any recent patches/changes which I should pick up? > > > I'm happy to cvsup either from 4.0-stable or 4.0-current if it would help > > > to fix this problem. > > Yup VIA has a new version of the 82C596 chip, in their usual visdom they > change the interface, but not the chip ID (I'll nominate VIA for the > way they do versioning). However I have worked out the solution with > Chris Wiener , that had this problem also and > kindly helped testing. Se the patch belowm try it and let me know.. Is it possible that something like that is happening with the 82C586 too? The chip on our boards are all marked VT82C586B. I'll try the patch although it seems to be for the 596? > > > Your question should include the VIA 82C586. :-) The answer will depend > > on who answer it. If it is Soren or one of the lucky ones that have it > > working, they will say everything is fine. For the rest of us with > > machines that don't want to install or that want to eat your disk if you > > install it somewhere else first, the answer is probably different. :-( > > Woa! I havn't seen any reports of the '586 not working, please point I did report it to -current about the 9th of March and you did respond to that message. I do seem to remember others complaining too, but when I tried to look for them through the mailing list search engine I couldn't find any because it seems that the search engine stopped indexing in December. :-( > me at them. I've seen a couble of cases where it was other known bad > HW that caused trouble. So by all means please forward any problem > to me, together with verbose boot logs etc and I'll take a look at > it, if there is a problem it should be fixed. However if it is on > HW I dont have access to here, I need someone that has a box that > can be used for testing, ie with filesystems that can be restored/ > reinstalled etc etc and have the time and patience to work with me > one the problem. I have a machine that can be trashed. The trouble is that it cannot install 4.x or -current because of the problem with the ata driver. During installation it just go in a loop during newfs and keep on spitting out errors. Should I just install 3.X and then copy a newer kernel over? 3.4 install perfectly and dma also works without a problem if enabled with flags 0xa0ff. (Although that is probably a slower dma?) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 3:35:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3E14E37B6B9 for ; Tue, 4 Apr 2000 03:35:23 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA48408; Tue, 4 Apr 2000 12:34:52 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004041034.MAA48408@freebsd.dk> Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? In-Reply-To: <200004041019.MAA65929@zibbi.mikom.csir.co.za> from John Hay at "Apr 4, 2000 12:19:03 pm" To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 4 Apr 2000 12:34:52 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John Hay wrote: > > > > Yup VIA has a new version of the 82C596 chip, in their usual visdom they > > change the interface, but not the chip ID (I'll nominate VIA for the > > way they do versioning). However I have worked out the solution with > > Chris Wiener , that had this problem also and > > kindly helped testing. Se the patch belowm try it and let me know.. > > Is it possible that something like that is happening with the 82C586 > too? The chip on our boards are all marked VT82C586B. I'll try the > patch although it seems to be for the 596? Well I wouldn't be surpriced at that :) > Should I just install 3.X and then copy a newer kernel over? 3.4 > install perfectly and dma also works without a problem if enabled > with flags 0xa0ff. (Although that is probably a slower dma?) I need a verbose boot log from the machine so I can see if VIA changed the chip ID or at least the revision on it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 3:51:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id D015537B7DE for ; Tue, 4 Apr 2000 03:51:27 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 035BD190A8; Tue, 4 Apr 2000 12:51:23 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 2FDF9506; Tue, 4 Apr 2000 12:51:17 +0200 (CEST) Date: Tue, 4 Apr 2000 12:51:17 +0200 To: John Hay Cc: Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? References: <200004040645.IAA94288@freebsd.dk> <200004041019.MAA65929@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004041019.MAA65929@zibbi.mikom.csir.co.za>; from jhay@mikom.csir.co.za on Tue, Apr 04, 2000 at 12:19:03PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-04-04-12-51-17+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4/04, John Hay wrote: | I have a machine that can be trashed. The trouble is that it cannot | install 4.x or -current because of the problem with the ata driver. | During installation it just go in a loop during newfs and keep on | spitting out errors. You are lucky, you go further than I do :) It stops after printing "Probing devices", with the HD led on, on my Compaq Armada V300. Using DDB, I can see that sysinstall is in bioread state. I haven't had time to continue serial remote debugging yet, and I do not know where to break in the kernel. A question for hackers: from within GDB, you can call subprograms on the target. Is there any "helper" subprogram in the kernel that can print a list of processes (as in DDB) and display the context of a particular process given its PID? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 6:21:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id BB2CC37B821; Tue, 4 Apr 2000 06:21:04 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id 330391F20F; Tue, 4 Apr 2000 15:24:38 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000404081440.E21619@daemon.ninth-circle.org> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404030757.A53939@ewok.creative.net.au> <200004032134.OAA61603@apollo.backplane.com> <20000404081440.E21619@daemon.ninth-circle.org> Date: Tue, 4 Apr 2000 14:13:39 +0200 To: Jeroen Ruigrok/Asmodai , Matthew Dillon From: Brad Knowles Subject: Re: 2nd call for reviews and tests: buf->bio patch Cc: Adrian Chadd , Poul-Henning Kamp , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:14 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > Besides, CURRENT does allow for the tree to be broken. I guess Bleeding > Edge lost its meaning within the FreeBSD ranks. Yes, but RELENG_4 is no longer -CURRENT. Therefore, different procedures need to be applied to it, now that it is -STABLE. > Ehm. Not as if your VM stuff wasn't causing disruption. Needed, > granted, but disruptive as well. And ucd-snmp has been broken quite > some time (still is?) due to the work. > And I know of a lot of people who actively use it. We use it quite heavily here. In what way is it broken with 4.0-STABLE? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 6:21:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 5B70837B821 for ; Tue, 4 Apr 2000 06:21:15 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id B07231F212; Tue, 4 Apr 2000 15:24:46 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000404082352.G21619@daemon.ninth-circle.org> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404082352.G21619@daemon.ninth-circle.org> Date: Tue, 4 Apr 2000 14:15:56 +0200 To: Jeroen Ruigrok/Asmodai , Matthew Dillon From: Brad Knowles Subject: Re: 2nd call for reviews and tests: buf->bio patch Cc: Poul-Henning Kamp , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > Like I said in another mail, this is CURRENT, things are > expected to break. You want stability of API's, go 3-STABLE. You want > a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have > your bandages ready. Like I said in a previous message, Poul broke vinum (among other things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't have been affected. But he didn't, and it was. This is what needs to be fixed. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 6:31:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7C31A37B974 for ; Tue, 4 Apr 2000 06:31:10 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA89789; Tue, 4 Apr 2000 15:31:00 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004041331.PAA89789@freebsd.dk> Subject: Re: 2nd call for reviews and tests: buf->bio patch In-Reply-To: from Brad Knowles at "Apr 4, 2000 02:15:56 pm" To: blk@skynet.be (Brad Knowles) Date: Tue, 4 Apr 2000 15:31:00 +0200 (CEST) Cc: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai), dillon@apollo.backplane.com (Matthew Dillon), phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Brad Knowles wrote: > > Like I said in a previous message, Poul broke vinum (among other > things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul > had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't > have been affected. But he didn't, and it was. Where the fsck did you get the idea that RELENG_4 was broken by Poul's commits to -CURRENT ?? Poul has nothing to do with vinum being broken in RELENG_4... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 6:34: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8A18337B8A6 for ; Tue, 4 Apr 2000 06:34:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA27237; Tue, 4 Apr 2000 15:33:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Brad Knowles Cc: Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch In-reply-to: Your message of "Tue, 04 Apr 2000 14:15:56 +0200." Date: Tue, 04 Apr 2000 15:33:43 +0200 Message-ID: <27235.954855223@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brad Knowles writes: >At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > >> Like I said in another mail, this is CURRENT, things are >> expected to break. You want stability of API's, go 3-STABLE. You want >> a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have >> your bandages ready. > > Like I said in a previous message, Poul broke vinum (among other >things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul >had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't >have been affected. But he didn't, and it was. Brad, You are confused. I have not made one single commit to 4.0-STABLE which even comes close to vinum. The problem in vinum/releng4 is the problem greg has been blaming on CAM since at least FreeBSDcon and indications seems to be that it is actually a malloc/free gottcha in vinum. I have nothing to do with that, apart from being releived that we don't seem to have a random stack-smasher bug in the system. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 7: 5:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 06E5537BA49 for ; Tue, 4 Apr 2000 07:05:46 -0700 (PDT) (envelope-from freebsd@ewok.creative.net.au) Received: (qmail 66040 invoked by uid 1008); 4 Apr 2000 14:05:32 -0000 Date: Tue, 4 Apr 2000 22:05:32 +0800 From: Adrian Chadd To: Kris Kennaway Cc: Timo Geusch , current@freebsd.org Subject: Re: UNIONFS Message-ID: <20000404220530.B53939@ewok.creative.net.au> References: <20000404074034.A290@odie.unix-consult.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Tue, Apr 04, 2000 at 02:14:15AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000, Kris Kennaway wrote: > On Tue, 4 Apr 2000, Timo Geusch wrote: > > > Here be dragons, I know :-). Got myself a nice juicy & reproducable > > crash here, so I thought I might as well try to track down this > > problem. But before I start,is anyone else working on this one? I'd > > hate to waste my not exactly ample time trying to duplicate somebody > > else's work. > > Frankly, unless you have the time to fix unionfs completely I wouldn't > bother. We know it's broken, whats needed is someone with a good handle on > the VFS code to sit down and spend a week or so to fix it. On the other > hand, if that's you then go for it (you'd certainly learn a lot of useful > things in the process) > I'm starting VFS hacking again :) Throw up a PR, I'll assign it to myself and I'll look at it for you. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 7:14:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id C783E37B778; Tue, 4 Apr 2000 07:14:12 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id PAA68337; Tue, 4 Apr 2000 15:14:07 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA04021; Tue, 4 Apr 2000 14:59:24 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200004041359.OAA04021@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: Maxim Sobolev , current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPP segfaulting In-Reply-To: Message from Gary Jennejohn of "Tue, 04 Apr 2000 11:01:32 +0200." <200004040901.LAA26278@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 14:59:24 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I should have done more than a few greps when reviewing this. The slcompress code is diving into the TCP header that comes after the IP header.... There's some nasty stuff going on here between vjcomp.c and slcompress.c - namely, the pointer passed into sl_uncompress_tcp is expected to have MAX_HDR bytes preceeding it (for compressed packets) and slcs_u::csu_ip therefore needs to be more than just an IP header. > Maxim Sobolev writes: > >Hi, > > > >The ppp built from the just cvsup'ed -current sources segfaulting. Following i > >s > >backtrace. Please contact me of some additional debugging info will be > >necessary. > > > >-Maxim > > > >PPP ON vega> > >Program received signal SIGSEGV, Segmentation fault. > >0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, > > slstat=0x808900c, compress_cid=0) at slcompress.c:177 > >177 if (ip->ip_src.s_addr != cs->cs_ip.ip_src.s_addr || > >(gdb) bt > >#0 0x806e98e in sl_compress_tcp (m=0x809e000, ip=0x809e01c, comp=0x808583c, > > slstat=0x808900c, compress_cid=0) at slcompress.c:177 > >#1 0x8071f70 in vj_LayerPush (bundle=0x80853a0, l=0x8093000, bp=0x809e000, > > pri=0, proto=0xbfbff41e) at vjcomp.c:73 > >#2 0x8064e0f in link_PushPacket (l=0x8093000, bp=0x809e000, b=0x80853a0, > > pri=0, proto=33) at link.c:225 > >#3 0x805fe46 in ip_PushPacket (l=0x8093000, bundle=0x80853a0) at ip.c:733 > >#4 0x804bf5e in bundle_FillQueues (bundle=0x80853a0) at bundle.c:414 > >#5 0x804bfc7 in bundle_UpdateSet (d=0x80853a0, r=0xbfbff5e8, w=0xbfbff568, > > e=0xbfbff4e8, n=0xbfbff4e0) at bundle.c:437 > >#6 0x80670af in DoLoop (bundle=0x80853a0) at main.c:517 > >#7 0x8067028 in main (argc=2, argv=0xbfbff804) at main.c:495 > >#8 0x804a85d in _start () > > > > Sorry, it looks like removing csu_hdr wasn't such a good idea after all. > Apparently the m_pullup of the mbuf makes it necessary to have at least > 128 bytes available in cspace. My bad :( I'll back out my changes. > > Try this patch, which basically reverts my modification: > > --- /usr/src/usr.sbin/ppp/slcompress.h.orig Tue Apr 4 10:48:59 2000 > +++ /u8/tmp/src/usr.sbin/ppp/slcompress.h Sat Aug 28 03:18:44 1999 > @@ -16,7 +16,7 @@ > * IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED > * WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. > * > - * $FreeBSD: src/usr.sbin/ppp/slcompress.h,v 1.14 2000/04/03 19:54:33 gj Exp $ > + * $FreeBSD: src/usr.sbin/ppp/slcompress.h,v 1.13 1999/08/28 01:18:44 peter Exp $ > * > * Van Jacobson (van@helios.ee.lbl.gov), Dec 31, 1989: > * - Initial distribution. > @@ -102,8 +102,14 @@ > u_short cs_hlen; /* size of hdr (receive only) */ > u_char cs_id; /* connection # associated with this state */ > u_char cs_filler; > - struct ip cs_ip; /* ip/tcp hdr from most recent packet */ > + union { > + char csu_hdr[MAX_HDR]; > + struct ip csu_ip; /* ip/tcp hdr from most recent packet */ > + } slcs_u; > }; > + > +#define cs_ip slcs_u.csu_ip > +#define cs_hdr slcs_u.csu_hdr > > /* > * all the state data for one serial line (we need one of these > > --- > Gary Jennejohn / garyj@muc.de gj@freebsd.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 8:13:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 0F4F837B66C for ; Tue, 4 Apr 2000 08:13:43 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id D3CAE1F366; Tue, 4 Apr 2000 17:17:13 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <27235.954855223@critter.freebsd.dk> References: <27235.954855223@critter.freebsd.dk> Date: Tue, 4 Apr 2000 16:27:03 +0200 To: Poul-Henning Kamp From: Brad Knowles Subject: Re: 2nd call for reviews and tests: buf->bio patch Cc: Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:33 PM +0200 2000/4/4, Poul-Henning Kamp wrote: > I have not made one single commit to 4.0-STABLE which even comes > close to vinum. My apologies. I must have misread/misremembered what was being said with regards to the commits breaking vinum, and somehow gotten that crossed with vinum being broken under RELENG_4. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 8:50:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.telemere.net (shell.telemere.net [63.224.9.3]) by hub.freebsd.org (Postfix) with ESMTP id 4BE1137B62C for ; Tue, 4 Apr 2000 08:49:55 -0700 (PDT) (envelope-from visigoth@telemere.net) Received: by shell.telemere.net (Postfix, from userid 1001) id 8E23D70601; Tue, 4 Apr 2000 10:57:39 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by shell.telemere.net (Postfix) with ESMTP id 782146C801 for ; Tue, 4 Apr 2000 10:57:39 -0500 (CDT) Date: Tue, 4 Apr 2000 10:57:39 -0500 (CDT) From: Visigoth To: current@freebsd.org Subject: current.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that current.freebsd.org has been not working for a while now, and I was wondering if there is a better place to get the new snapshots, as well as install -current. I brief search of the mail archives tells me nothing ( i may have missed it, searching for current.freebsd.org on -current kind of pulls up a lot.. ;) ) From current.freebsd.org I recieve: Name (current.freebsd.org:visigoth): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 530 Can't set guest privileges. ftp: Login failed. and releng3 is refusing ftp... Ahhh!!! must... find.... snapshots.... visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net ____________________________________________________________________________ | - M$ Win 2K was built for the internet. | - Unix _BUILT_ the internet. | FreeBSD - The POWER to serve | http://www.freebsd.org your call... | | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 10:42:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4291C37BA71 for ; Tue, 4 Apr 2000 10:42:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA93215; Tue, 4 Apr 2000 11:42:55 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA70015; Tue, 4 Apr 2000 11:42:11 -0600 (MDT) Message-Id: <200004041742.LAA70015@harmony.village.org> To: John Hay Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? Cc: sos@freebsd.dk (Soren Schmidt), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 04 Apr 2000 12:19:03 +0200." <200004041019.MAA65929@zibbi.mikom.csir.co.za> References: <200004041019.MAA65929@zibbi.mikom.csir.co.za> Date: Tue, 04 Apr 2000 11:42:11 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004041019.MAA65929@zibbi.mikom.csir.co.za> John Hay writes: : > Woa! I havn't seen any reports of the '586 not working, please point : : I did report it to -current about the 9th of March and you did respond : to that message. I do seem to remember others complaining too, but when : I tried to look for them through the mailing list search engine I : couldn't find any because it seems that the search engine stopped : indexing in December. :-( I've had about 10 people contact me asking that I add something to UPDATING about the problems with the Apollo MPV3 chipset. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 10:56:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 74ECF37B882 for ; Tue, 4 Apr 2000 10:56:23 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id TAA75436; Tue, 4 Apr 2000 19:55:55 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004041755.TAA75436@zibbi.mikom.csir.co.za> Subject: Re: ATA & 82C596 bug in 4.0-RELEASE? In-Reply-To: <200004041034.MAA48408@freebsd.dk> from Soren Schmidt at "Apr 4, 2000 12:34:52 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Tue, 4 Apr 2000 19:55:55 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > Yup VIA has a new version of the 82C596 chip, in their usual visdom they > > > change the interface, but not the chip ID (I'll nominate VIA for the > > > way they do versioning). However I have worked out the solution with > > > Chris Wiener , that had this problem also and > > > kindly helped testing. Se the patch belowm try it and let me know.. > > > > Is it possible that something like that is happening with the 82C586 > > too? The chip on our boards are all marked VT82C586B. I'll try the > > patch although it seems to be for the 596? > > Well I wouldn't be surpriced at that :) > > > Should I just install 3.X and then copy a newer kernel over? 3.4 > > install perfectly and dma also works without a problem if enabled > > with flags 0xa0ff. (Although that is probably a slower dma?) > > I need a verbose boot log from the machine so I can see if VIA > changed the chip ID or at least the revision on it... > Ok, here is it. John -- John Hay -- John.Hay@mikom.csir.co.za machdep.msgbuf: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Tue Apr 4 18:31:56 SAST 2000 jhay@angel.cids.org.za:/a/releng_4/usr/src/sys/compile/TOBY Calibrating clock(s) ... TSC clock: 400878590 Hz, i8254 clock: 1193091 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 400912253 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 33488896 (32704K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x002ac000 - 0x01fe7fff, 30654464 bytes (7484 pages) avail memory = 30142464 (29436K bytes) bios32: Found BIOS32 Service Directory header at 0xc00face0 bios32: Entry = 0xfb160 (c00fb160) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb190 pnpbios: Found PnP BIOS data at 0xc00fbda0 pnpbios: Entry = f0000:bdc8 Rev = 1.0 Other BIOS signatures found: ACPI: 000f6d60 Preloaded elf kernel "kernel.v4" at 0xc0293000. Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=06911106) devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=06911106) pcib0: on motherboard found-> vendor=0x1106, dev=0x0691, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e0000000, size 26 found-> vendor=0x1106, dev=0x8598, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x1106, dev=0x0586, revid=0x47 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1106, dev=0x0571, revid=0x06 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000e000, size 4 found-> vendor=0x1106, dev=0x3038, revid=0x02 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=15 map[20]: type 1, range 32, base 0000e400, size 5 found-> vendor=0x1106, dev=0x3040, revid=0x10 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x5333, dev=0x8901, revid=0x16 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e4000000, size 26 found-> vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base eb180000, size 12 map[14]: type 1, range 32, base 0000e800, size 6 map[18]: type 1, range 32, base eb000000, size 20 found-> vendor=0x114f, dev=0x5012, revid=0x00 class=07-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base eb181000, size 7 map[14]: type 1, range 32, base 0000ec00, size 7 map[18]: type 1, range 32, base eb100000, size 19 pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xe000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xe008 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed pci0: (vendor=0x1106, dev=0x3038) at 7.2 irq 15 pci0: (vendor=0x5333, dev=0x8901) at 15.0 irq 11 fxp0: port 0xe800-0xe83f mem 0xeb000000-0xeb0fffff,0xeb180000-0xeb180fff irq 10 at device 16.0 on pci0 fxp0: Ethernet address 00:90:27:8b:32:6d fxp0: supplying EUI64: 00:90:27:ff:fe:8b:32:6d bpf: fxp0 attached pci0: (vendor=0x114f, dev=0x5012) at 19.0 irq 12 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=06911106) devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) <7>kbdc: RESET_KBD return code:00fa <7>kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0067 <7>kbdc: TEST_AUX_PORT status:0000 <7>kbdc: RESET_AUX return code:00fe <7>kbdc: RESET_AUX return code:00fe <7>kbdc: RESET_AUX return code:00fe <7>kbdc: DIAGNOSE status:0055 <7>kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:022bef3f 0..555=556 cylinders, 0..239=240 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 40084040, tty 4003009a, net 4007049a bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached ata0-master: success setting up UDMA2 mode on VIA chip ad0: ATA-3 disk at ata0 as master ad0: 4104MB (8406720 sectors), 8896 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 Mounting root from ufs:wd0s1a wd0s1: type 0xa5, start 63, end = 8405774, size 8405712 : OK start_init: trying /sbin/init ata0-master: success setting up PIO4 mode on generic chip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 10:57:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id BE26D37BC3D for ; Tue, 4 Apr 2000 10:57:29 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup1-14.iptelecom.net.ua [212.9.226.14]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id VAA10666 for ; Tue, 4 Apr 2000 21:03:49 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id UAA01433 for ; Tue, 4 Apr 2000 20:56:38 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EA2CD6.24636F65@altavista.net> Date: Tue, 04 Apr 2000 20:56:38 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Dangerously looking glitch (4.0-STABLE) Content-Type: multipart/mixed; boundary="------------3D64CAE46133EFA188180FFD" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3D64CAE46133EFA188180FFD Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hi, I've tried to track down why my own script which is cleaning non-matching distfiles from time to time produce incorrect results (just cvsup'ed 4.0). After some digging I've found that this bug could be easily reproduced by doing "find -exec md5" on large set of files several times consequiently, and then comparing results. You can see that md5 checksum of the one of the files is different in the run #3. Most often this happens with big distfiles, like XFree, jdk etc and only after some amount of previous activity. Memory/CPU/HDD bug is highly unlikely, as this box often up and running w/o reboot from release to release, so it looks like glitch in disk cache, fs, soft-updates or md5. -Maxim root@vega# find -H /usr/ports/distfiles -type f -exec md5 {} \; | sort > /tmp/1 root@vega# find -H /usr/ports/distfiles -type f -exec md5 {} \; | sort > /tmp/2 root@vega# find -H /usr/ports/distfiles -type f -exec md5 {} \; | sort > /tmp/3 root@vega# md5 /tmp/1 /tmp/2 /tmp/3 MD5 (/tmp/1) = 8ca51e2ce47c49f8a58776ca4b3567a2 MD5 (/tmp/2) = 8ca51e2ce47c49f8a58776ca4b3567a2 MD5 (/tmp/3) = 61f7ef39f30783d42c9b93dab4695398 root@vega# diff /tmp/2 /tmp/3 129c129 < MD5 (/usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz) = 07992302128f36c7f802b579e041604c --- > MD5 (/usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz) = a78b523bcc2875a5d0fa8be1e1b73ac3 root@vega# md5 /usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz MD5 (/usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz) = 07992302128f36c7f802b579e041604c root@vega# md5 /usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz MD5 (/usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz) = 07992302128f36c7f802b579e041604c root@vega# md5 /usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz MD5 (/usr/ports/distfiles/jdk1.1.8_ELF.V1999-11-9.tar.gz) = 07992302128f36c7f802b579e041604c root@vega# mount [...] /dev/ad0s1f on /usr (ufs, NFS exported, local, noatime, soft-updates, writes: sync 2 async 63, reads: sync 4977 async 13395) [...] root@vega# du -d1 /usr/ports/distfiles/ 7392 /usr/ports/distfiles/mpich 1 /usr/ports/distfiles/amaya 145 /usr/ports/distfiles/wdm 3513 /usr/ports/distfiles/python 69860 /usr/ports/distfiles/xc 20465 /usr/ports/distfiles/pm3 199 /usr/ports/distfiles/unroff 1841 /usr/ports/distfiles/povray31 949 /usr/ports/distfiles/squid2.3 1 /usr/ports/distfiles/timidity 13 /usr/ports/distfiles/xengine 341295 /usr/ports/distfiles/ --------------3D64CAE46133EFA188180FFD Content-Type: text/plain; charset=koi8-r; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #9: Tue Apr 4 17:32:40 EEST 2000 root@vega.vega.com:/usr/src/sys/compile/VEGA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 100227617 Hz CPU: Pentium/P54C (100.23-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x524 Stepping = 4 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 38395904 (37496K bytes) Preloaded elf kernel "kernel" at 0xc0287000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 7.2 irq 11 chip1: port 0x5000-0x500f at device 7.3 on pci0 ed0: port 0x6500-0x651f irq 10 at device 17.0 on pci0 ed0: address 00:40:05:3b:1c:23, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 6187MB [13410/15/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s1a --------------3D64CAE46133EFA188180FFD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 12:38:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D7E2C37B77C; Tue, 4 Apr 2000 12:38:30 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 09C641C4A; Tue, 4 Apr 2000 15:38:29 -0400 (EDT) Date: Tue, 4 Apr 2000 15:38:29 -0400 From: Bill Fumerola To: Jeroen Ruigrok/Asmodai Cc: Matthew Dillon , Adrian Chadd , Poul-Henning Kamp , current@freebsd.org Subject: Re: 2nd call for reviews and tests: buf->bio patch Message-ID: <20000404153828.E23367@jade.chc-chimes.com> References: <22448.954783492@critter.freebsd.dk> <200004031751.KAA60287@apollo.backplane.com> <20000404030757.A53939@ewok.creative.net.au> <200004032134.OAA61603@apollo.backplane.com> <20000404081440.E21619@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000404081440.E21619@daemon.ninth-circle.org>; from asmodai@wxs.nl on Tue, Apr 04, 2000 at 08:14:40AM +0200 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000 at 08:14:40AM +0200, Jeroen Ruigrok/Asmodai wrote: > Ehm. Not as if your VM stuff wasn't causing disruption. Needed, > granted, but disruptive as well. And ucd-snmp has been broken quite > some time (still is?) due to the work. > And I know of a lot of people who actively use it. Not that it matters, but I fixed the code and submitted back a patch to ucd-snmp maintainers and its part of the snmp codebase now. Most of it was taken directly from the matching changes to vmstat, I believe. That is unless I missed something, or something else changed recently. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 13:19:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (peedub.muc.de [193.149.49.109]) by hub.freebsd.org (Postfix) with ESMTP id 1920637B77C for ; Tue, 4 Apr 2000 13:19:45 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id VAA01184; Tue, 4 Apr 2000 21:49:10 +0200 (CEST) Message-Id: <200004041949.VAA01184@peedub.muc.de> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Somers Cc: current@FreeBSD.ORG Subject: Re: PPP segfaulting Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 04 Apr 2000 16:14:27 +0200." <200004041359.OAA04021@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 21:49:10 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: >Sorry, I should have done more than a few greps when reviewing this. While we're in self-castigation mode here ;), _I_ should have done more than a few greps before *committing* this. My first pointy hat in 5 years, not bad (of course, I don't do all that much committing). --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 13:50:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from queeg.ludd.luth.se (queeg.ludd.luth.se [130.240.16.109]) by hub.freebsd.org (Postfix) with ESMTP id 9B28237BC81 for ; Tue, 4 Apr 2000 13:50:17 -0700 (PDT) (envelope-from pantzer@ludd.luth.se) Received: from speedy.ludd.luth.se (pantzer@speedy.ludd.luth.se [130.240.16.164]) by queeg.ludd.luth.se (8.9.3/8.9.3) with ESMTP id WAA06304; Tue, 4 Apr 2000 22:49:53 +0200 (CEST) Message-Id: <200004042049.WAA06304@queeg.ludd.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Load average calculation? In-Reply-To: Message from Donn Miller of "Mon, 03 Apr 2000 16:26:03 EDT." <38E8FE5B.CD2FD3E6@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 22:49:52 +0200 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Patrick Mau wrote: > > > On all Unix-like systems I know, the load average is the average mumber > > of processes running during a given time interval. I can't see what use > > it may have to count load for _waiting_ processes. > > > > I/O load is not process load, if a process waits for I/O completion it does > > not use up its timeslice. > > I think we ought to re-examine the definition of load average. By > load, we mean an actual load on the cpu, and waiting processes aren't > really exerting a cpu load. So, by that reasoning I say waiting > processes don't count. The load average number is not a measure of the CPU load. It is a measure of _system_ load. Processes in short term wait count so that the load on the disks is accounted for. The load on the disks is often the most important factor. Use vmstat if you need the CPU load. Use iostat for the disk load. Use the load average to get both. (No, this is not a new thing in FreeBSD, this is how it works in all the operating systems that are based on BSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 14:48:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id B092637B85C for ; Tue, 4 Apr 2000 14:48:46 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id D5890C0; Tue, 4 Apr 2000 17:41:05 -0400 (EDT) Date: Tue, 4 Apr 2000 17:41:05 -0400 From: Ben Rosengart To: current@freebsd.org Subject: sshd library problems Message-ID: <20000404174105.A302@narcissus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is not working for me. When I try to start it, I get the following: ** RSA_PKCS1: Unable to find an RSA implemenation shared library. ** Install either the USA (librsaINTL.so) or International (librsaUSA.so) ** RSA library on your system and run this program again. Then a pointer to a doc (which I read), then it receives signal 11 and dumps core. (BTW, "implementation" is misspelled there.) I have rsaref-2.0 installed from ports, and I have USA_RESIDENT=YES and RSAREF=YES defined in /etc/make.conf. I've cvsupped from a new vanilla standard-supfile, using the cvs-crypto collection. Here are two lines from the output of "truss sshd": access("/usr/lib/librsaINTL.so",0) = 0 (0x0) open("/usr/lib/librsaINTL.so",0,027757770600) = 4 (0x4) Needless to say, I find this slightly confusing. What am I doing wrong? Thanks in advance. -- Ben "I didn't order any WOO-WOO... Maybe a YUBBA... But no WOO-WOO!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 14:58:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id A041037BA63; Tue, 4 Apr 2000 14:58:34 -0700 (PDT) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.251.72] by wcn4.wcnet.net with ESMTP (SMTPD32-6.00) id A587117701F8; Tue, 04 Apr 2000 16:58:31 -0500 Message-ID: <38EA6651.1F003673@wcnet.net> Date: Tue, 04 Apr 2000 17:01:53 -0500 From: John Estess X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Adrian Chadd Cc: current@freebsd.org Subject: Re: UNIONFS References: <20000404074034.A290@odie.unix-consult.com> <20000404220530.B53939@ewok.creative.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm starting VFS hacking again :) Throw up a PR, I'll assign it to myself > and I'll look at it for you. Mind if I tag along for the ride? I just finished a "code walkthrough" class and vfs_ is somewhat fresh. Painfully fresh, I may add. I'll gladly sanity check patches. I was looking for a excuse to peruse the union code... -- John Estess C: God's Programming Language -> OpenGL Programming Guide To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 15: 0:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 652C937B907 for ; Tue, 4 Apr 2000 15:00:36 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA19349; Tue, 4 Apr 2000 15:01:01 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brad Knowles Cc: Jeroen Ruigrok/Asmodai , Matthew Dillon , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch In-reply-to: Your message of "Tue, 04 Apr 2000 14:15:56 +0200." Date: Tue, 04 Apr 2000 15:01:01 -0700 Message-ID: <19346.954885661@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Like I said in a previous message, Poul broke vinum (among other > things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul I'd actually consider it a really good idea if you could back this up since I have not seen anything to suggest that phk's changes have affected 4.0-STABLE in any way. Cite exact revisions to files on the RELENG_4 branch please. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 15: 3:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id 3CBF037B961; Tue, 4 Apr 2000 15:03:06 -0700 (PDT) (envelope-from kvindeservice@netscum.dk) Received: from localhost (kvindeservice@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id AAA07668; Wed, 5 Apr 2000 00:02:49 +0200 (CEST) (envelope-from kvindeservice@netscum.dk) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: kvindeservice owned process doing -bs Date: Wed, 5 Apr 2000 00:02:49 +0200 (CEST) From: tele danmarQ kvindeservice X-Sender: kvindeservice@fLuFFy.iNt.tElE.dK Reply-To: freebsd-guinea-pigs@netscum.dk To: Matthew Dillon Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-Reply-To: Message-ID: Organization: Department of Weird so-called Music and Stuff X-Pedophile: BARRY BOUWSMA HAS A PEDO FILE MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Mar 19100 (not like I'm slow or anything), Matthew Dillon wrote: [regarding random-access database files, such as are used for the INN history files, and FreeBSD 4.0...] > For INN there are several things you can tune in 4.0. First and > foremost you can try turning off the write-behind code, > sysctl -w vfs.write_behind=0. Secondly you can mess around with > the vfs.hidirtybuffers sysctl (generally lower it) in order to > force out dirty pages earlier and thus reduce the number that > fsync has to deal with. Thanks for the tips. A few days ago, I rebuilt one of my transit peering boxen to use the 4.0-RELENG k0deZ and then proceeded to tune the above, after letting it run for a while to get a feel for how it was acting, as well as to let accumulated backlogs clear out. Now, the history file I'm dealing with contains some 14 million entries, so there's about 200 megabytes of goods to be scribbled over the disks (or at least the pages for some 12-18 entries per second over the 30- second intervals). It's just a single disk, so it takes a while to dump the data, and much more so when taking in backlogs at several dozen message IDs per second (limited mostly by the time blocked waiting for the disk writes to complete). After first firing things up, it almost seemed to be taking anywhere from 25 to 55 seconds to dump to the disks every so often, with an available cycle time of perhaps 10 to 15%. After a bit of time, as the backlogs were cleared out, things seemed to settle down to somewhere around 15 seconds blocked, plus or minus a bit, followed by around 25 seconds of activity. Toggling the sysctl knob and tweaking the limits might have trimmed a couple seconds from the unresponsive times, although it's difficult to say just what was an improvement, and what was due to natural fluctuation in the flow of incoming news. It was nothing to write home about. So, while I did tune things, the results weren't quite what I hoped for. > I believe that INN also messes around with > shared/R+W mmap()'s - it may be possible to add MAP_NOSYNC to those > maps to turn off the 30 second fsync on pages dirtied through the VM > system (for those maps), though this may increase the amount of stale > (unwritten) data after a crash. If this is the MMAP_SYNC in the (INN 1.5) config.data file, this is set to `DONT' on these boxes. I have noticed that our 2.2-RELENG box, which had the time between sync disk dumps tweaked up to an hour, always seemed to sync the disks when it would crash (except when the truck delivering a new UPS ran into the electric pole), and as long as the text file (only appended to) is in a consistent state, one can recreate the database files, so the risk of losing data hasn't concerned me too much. Now, I did notice with great joy that you committed some k0deZ a few days ago that might help this problem, and as soon as I unearth that announcement, I'll followup to that and describe the results on our history database files. thanks, barry (not a fluffy, oh no) bouwsma, teledanmorkinternet -- *** This was posted with the express permission of *** ****************************************************** ** HIS HIGHNESS KAAZMANN LORD AND MASTER OF USENET ** ****************************************************** ********* We are simple servants of his will ********* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 15:29: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 0030037B5E6 for ; Tue, 4 Apr 2000 15:28:56 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA20767; Tue, 4 Apr 2000 17:28:52 -0500 (CDT) Date: Tue, 4 Apr 2000 17:28:52 -0500 From: "Matthew D. Fuller" To: Ben Rosengart Cc: current@FreeBSD.ORG Subject: Re: sshd library problems Message-ID: <20000404172852.C1916@futuresouth.com> References: <20000404174105.A302@narcissus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000404174105.A302@narcissus.net> X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Ben :) On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me that Ben Rosengart remarked > Hello all, > I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is > not working for me. When I try to start it, I get the following: > > ** RSA_PKCS1: Unable to find an RSA implemenation shared library. > ** Install either the USA (librsaINTL.so) or International (librsaUSA.so) > ** RSA library on your system and run this program again. (Aren't those filenames reversed? Just a hunch...) > I have rsaref-2.0 installed from ports, and I have USA_RESIDENT=YES and > RSAREF=YES defined in /etc/make.conf. I've cvsupped from a new vanilla > standard-supfile, using the cvs-crypto collection. Hm. Don't know how much I can say beyond that. I've put together a few post-ssh systems (4.0-R, -CURRENT), and haven't had any trouble after I remembered to install the crypto dists. FreeBSD mortis.sighup.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Mar 14 03:49:39 CST 2000 fullermd@mortis.sighup.org:/usr/src/sys/compile/MORTIS i386 (ttypb):{54}% ll /usr/lib/librs* -r--r--r-- 1 root wheel 6358 Mar 14 04:03 /usr/lib/librsaUSA.a lrwxr-xr-x 1 root wheel 14 Mar 14 04:03 /usr/lib/librsaUSA.so@ -> librsaUSA.so.1 -r--r--r-- 1 root wheel 8080 Mar 14 04:03 /usr/lib/librsaUSA.so.1 -r--r--r-- 1 root wheel 7122 Mar 14 04:03 /usr/lib/librsaUSA_p.a -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 15:36:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 8B9A837B7B9 for ; Tue, 4 Apr 2000 15:36:33 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id CC10F57; Tue, 4 Apr 2000 18:28:56 -0400 (EDT) Date: Tue, 4 Apr 2000 18:28:56 -0400 From: Ben Rosengart To: "Matthew D. Fuller" Cc: current@FreeBSD.ORG Subject: Re: sshd library problems Message-ID: <20000404182856.A27543@narcissus.net> References: <20000404174105.A302@narcissus.net> <20000404172852.C1916@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000404172852.C1916@futuresouth.com>; from fullermd@futuresouth.com on Tue, Apr 04, 2000 at 05:28:52PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000 at 05:28:52PM -0500, Matthew D. Fuller wrote: > Hi Ben :) Hello Matthew, always nice to "see" you. > On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me > that Ben Rosengart remarked > > Hello all, > > I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is > > not working for me. When I try to start it, I get the following: > > > > ** RSA_PKCS1: Unable to find an RSA implemenation shared library. > > ** Install either the USA (librsaINTL.so) or International (librsaUSA.so) > > ** RSA library on your system and run this program again. > > (Aren't those filenames reversed? Just a hunch...) Hmm. As you can see in my truss output, it's librsaINTL.so that's getting picked up. > (ttypb):{54}% ll /usr/lib/librs* > -r--r--r-- 1 root wheel 6358 Mar 14 04:03 /usr/lib/librsaUSA.a > lrwxr-xr-x 1 root wheel 14 Mar 14 04:03 /usr/lib/librsaUSA.so@ -> librsaUSA.so.1 > -r--r--r-- 1 root wheel 8080 Mar 14 04:03 /usr/lib/librsaUSA.so.1 > -r--r--r-- 1 root wheel 7122 Mar 14 04:03 /usr/lib/librsaUSA_p.a I moved /usr/lib/librsaINTL* to a backup location, and now the ssh programs no longer complain or dump core. I apparently shot myself in the foot by building the world with USA_RESIDENT set to "NO" at some point. Thank you, Matthew! -- Ben "I didn't order any WOO-WOO... Maybe a YUBBA... But no WOO-WOO!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 15:40:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id E873037B8B7 for ; Tue, 4 Apr 2000 15:40:34 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA16054; Tue, 4 Apr 2000 18:40:22 -0400 (EDT) Message-ID: <20000404184022.A15164@netmonger.net> Date: Tue, 4 Apr 2000 18:40:22 -0400 From: Christopher Masto To: Nick Hibma , Paul Haddad Cc: FreeBSD CURRENT Mailing List Subject: USB/Orb/kue/iopener/filesystem corruption References: <008501bf9b84$ad365270$0bac2ac0@pth.com> <20000403132725.B8685@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <20000403132725.B8685@netmonger.net>; from Christopher Masto on Mon, Apr 03, 2000 at 01:27:25PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 03, 2000 at 01:27:25PM -0400, Christopher Masto wrote: > Regarding USB drives, I have been using the Orb "2.2GB" USB-SCSI > version with some success. There do seem to be some serious > filesystem corruption problems, but I haven't had time to determine > where they're coming from. I often get corruption-related panics > while trying to install packages, and fsck always finds a number of > serious problems and removes about a dozen files (from /usr/lib > mostly, so I'll eventually lose something important). When I > download something large, such as XFree86, the file's checksum > comes out wrong and gzip fails with errors. I tried this again last night. I bought some new cartridges for the Orb drive, and installed -current on one, built a kernel, and installed quite a few packages by chrooting to it and pkg_adding them. Big things, like XFree86. I then built a kernel and booted it on my laptop, using the Orb as a root filesystem. Everything seemed to go well, and fsck found no errors. I then took it home and did the same thing on my i-opener. It seemed to work well, and I spent quite a bit of time trying to get X configured properly (at which I didn't quite succeed, but that's another story). After a couple of hours, I plugged in a D-Link 650 (kue) ethernet, and ssh'd to another machine, on which I started to FTP a few things. After a couple of minutes, I got "kue0: watchdog timeout" and seemed to stop transmitting packets. I unplugged the kue, plugged it back in, and got a panic (unfortunately I don't have the details at the moment.. I'll try to record them tonight). Upon rebooting, the filesystem was corrupted. I brought it back today to the same machine that I installed everything from yesterday, and confirmed it: ** /dev/da0a (NO WRITE) ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes UNKNOWN FILE TYPE I=55632 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? no UNKNOWN FILE TYPE I=222216 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? no UNKNOWN FILE TYPE I=285768 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? no ** Phase 2 - Check Pathnames DUP/BAD I=55632 OWNER=root MODE=100644 SIZE=2623 MTIME=Nov 5 22:14 1994 FILE=/usr/local/share/bx/translation/CP437 UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no BAD TYPE VALUE I=55632 OWNER=root MODE=100644 SIZE=2623 MTIME=Nov 5 22:14 1994 FILE=/usr/local/share/bx/translation/CP437 UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no DUP/BAD I=222216 OWNER=root MODE=40755 SIZE=2560 MTIME=Apr 3 22:03 2000 DIR=/usr/share/zoneinfo/America UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no fsck: cannot find inode 222216 It happens with or without soft updates, by the way. This time I happened to have them on. I can conclude from this that it's not the drive or the media, and it doesn't appear to be the USB stack or umass driver. I think that something, when using the kue driver at the same time, is causing the damage. That's very odd, because I'm using the same D-Link ethernet adapter that I've used for months with my laptop, and didn't have any problems. The only difference may be that they're compiled in to the kernel now. Next time I get a chance, I'll try: Filesystem-intensive activity without using kue at all, then a reboot and fsck. Loading kue as a module. Simulating the i-opener situation with my laptop. Getting more details on the kernel panic. This is bizzare. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 16:11: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id A8AAD37B92D for ; Tue, 4 Apr 2000 16:10:54 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12ccTE-0002WR-0C; Tue, 4 Apr 2000 23:10:53 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id AAA31776; Wed, 5 Apr 2000 00:13:20 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Wed, 5 Apr 2000 00:07:55 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Christopher Masto Cc: Paul Haddad , FreeBSD CURRENT Mailing List Subject: Re: USB/Orb/kue/iopener/filesystem corruption In-Reply-To: <20000404184022.A15164@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why does this sound like the warning that is written in the manual of the Iomega Zip drive: do not connect more than one Zip drive to the same USB host data might corrupted. Or something similar... Nick On Tue, 4 Apr 2000, Christopher Masto wrote: > On Mon, Apr 03, 2000 at 01:27:25PM -0400, Christopher Masto wrote: > > Regarding USB drives, I have been using the Orb "2.2GB" USB-SCSI > > version with some success. There do seem to be some serious > > filesystem corruption problems, but I haven't had time to determine > > where they're coming from. I often get corruption-related panics > > while trying to install packages, and fsck always finds a number of > > serious problems and removes about a dozen files (from /usr/lib > > mostly, so I'll eventually lose something important). When I > > download something large, such as XFree86, the file's checksum > > comes out wrong and gzip fails with errors. > > I tried this again last night. I bought some new cartridges for the > Orb drive, and installed -current on one, built a kernel, and > installed quite a few packages by chrooting to it and pkg_adding them. > Big things, like XFree86. I then built a kernel and booted it on > my laptop, using the Orb as a root filesystem. Everything seemed > to go well, and fsck found no errors. > > I then took it home and did the same thing on my i-opener. It seemed > to work well, and I spent quite a bit of time trying to get X > configured properly (at which I didn't quite succeed, but that's > another story). After a couple of hours, I plugged in a D-Link 650 > (kue) ethernet, and ssh'd to another machine, on which I started to > FTP a few things. After a couple of minutes, I got "kue0: watchdog > timeout" and seemed to stop transmitting packets. I unplugged the > kue, plugged it back in, and got a panic (unfortunately I don't have > the details at the moment.. I'll try to record them tonight). > > Upon rebooting, the filesystem was corrupted. I brought it back today > to the same machine that I installed everything from yesterday, and > confirmed it: > > ** /dev/da0a (NO WRITE) > ** Last Mounted on / > ** Phase 1 - Check Blocks and Sizes > UNKNOWN FILE TYPE I=55632 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=222216 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > UNKNOWN FILE TYPE I=285768 > UNEXPECTED SOFT UPDATE INCONSISTENCY > > CLEAR? no > > ** Phase 2 - Check Pathnames > DUP/BAD I=55632 OWNER=root MODE=100644 > SIZE=2623 MTIME=Nov 5 22:14 1994 > FILE=/usr/local/share/bx/translation/CP437 > > UNEXPECTED SOFT UPDATE INCONSISTENCY > > REMOVE? no > > BAD TYPE VALUE I=55632 OWNER=root MODE=100644 > SIZE=2623 MTIME=Nov 5 22:14 1994 > FILE=/usr/local/share/bx/translation/CP437 > > UNEXPECTED SOFT UPDATE INCONSISTENCY > > FIX? no > > DUP/BAD I=222216 OWNER=root MODE=40755 > SIZE=2560 MTIME=Apr 3 22:03 2000 > DIR=/usr/share/zoneinfo/America > > UNEXPECTED SOFT UPDATE INCONSISTENCY > > REMOVE? no > > fsck: cannot find inode 222216 > > It happens with or without soft updates, by the way. This time I > happened to have them on. > > I can conclude from this that it's not the drive or the media, and it > doesn't appear to be the USB stack or umass driver. I think that > something, when using the kue driver at the same time, is causing the > damage. That's very odd, because I'm using the same D-Link ethernet > adapter that I've used for months with my laptop, and didn't have any > problems. The only difference may be that they're compiled in to the > kernel now. > > Next time I get a chance, I'll try: > > Filesystem-intensive activity without using kue at all, then a > reboot and fsck. > > Loading kue as a module. > > Simulating the i-opener situation with my laptop. > > Getting more details on the kernel panic. > > This is bizzare. > -- > Christopher Masto Senior Network Monkey NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 16:23:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id C8F2737B578 for ; Tue, 4 Apr 2000 16:23:34 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.0/8.10.0) with ESMTP id e34NNXk27089 for ; Tue, 4 Apr 2000 18:23:33 -0500 (CDT) Date: Tue, 4 Apr 2000 18:23:33 -0500 (CDT) From: Steve Price To: current@freebsd.org Subject: signal mask from jmp_buf Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, What is the proper way for obtaining the signal mask from within the jmp_buf struct on 4.x or -current? Previously with the JDK port for < 3.x we did something like this: signalMask = jmpbuf[0]._sjb[6]; This no longer works now that we support >32 signals. Is there a better, more portable way that will work for all versions of FreeBSD? Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 18:13:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 07A3A37B972 for ; Tue, 4 Apr 2000 18:13:46 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA23895; Tue, 4 Apr 2000 21:13:42 -0400 (EDT) Message-ID: <20000404211341.E28658@netmonger.net> Date: Tue, 4 Apr 2000 21:13:41 -0400 From: Christopher Masto To: Nick Hibma Cc: Paul Haddad , FreeBSD CURRENT Mailing List Subject: Re: USB/Orb/kue/iopener/filesystem corruption References: <20000404184022.A15164@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Wed, Apr 05, 2000 at 12:07:55AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 12:07:55AM +0100, Nick Hibma wrote: > > Why does this sound like the warning that is written in the manual of > the Iomega Zip drive: > > do not connect more than one Zip drive to the same USB host data > might corrupted. > > Or something similar... But.. but.. I only have the one drive connected. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 18:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id BE76F37B9C3; Tue, 4 Apr 2000 18:28:50 -0700 (PDT) (envelope-from freebeer@fluffy.gets.an.analprobe.dk) Received: from localhost (freebeer@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id DAA07903; Wed, 5 Apr 2000 03:28:45 +0200 (CEST) (envelope-from freebeer@fluffy.gets.an.analprobe.dk) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: freebeer owned process doing -bs Date: Wed, 5 Apr 2000 03:28:45 +0200 (CEST) From: Kun Limfjordsporter X-Sender: freebeer@fLuFFy.iNt.tElE.dK Reply-To: FreeBSD-guineapigs@netscum.dk To: Matthew Dillon Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-Reply-To: Message-ID: Organization: Freenix is STILL OVERRATED X-Pedophile: Yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 2406 Sep 1993, Matthew Dillon wrote: > I've committed an 80% fix for the random seek / write > performance issue. The rest of the fix will come later > when Kirk commits his shared-lock-buffer-cache idea. > > I've committed it into -current and will MFC it into > -stable in a week if there aren't any problems. I Woo. Okay, so I took the bait and snarfed the k0deZ from midday GMT 02.April, and have built a suitable SMP kernel and world, and that's what I've been running for one news peering swerver for a spell. > This should solve most of the random-I/O latency issues > with read-after-write on buffers. Basically what > had to be done was to continue to call the clustering > code as before (so reallocblks still gets called), but > only issue write_behind I/O if the writes are > generally sequential. If the writes are random, even > big writes, we do not issue write-behind I/O. As I noted in the earlier message I just sent, disabling the write- behind via the sysctl knob didn't make an outstanding difference in performance -- innd was still unresponsive during the time that the random history database files needed updating for somewhere around 10 to 15 seconds when handling a full feed. Unfortunately, as I was hoping these latest hacks would fix the read/write locking, it looks like I'll have to wait for the remaining 20% of the fix, since I still see innd blocking during the time the light on the drive with history is lit. I did notice earlier with 4.0-STABLE that I had not enabled softupdates on the /news disk (with the history files), so I enabled it and tried looking at numbers again. There was no improvement -- if anything, it almost seemed like the time that INN was spending in history-related activity (writing or lookups) increased somewhat. I don't see any problems with the latest code changes (of 2 1/2 days ago), as the machine has been running without problems for more than a day now. I just don't see the improvement I am hoping for. This machine isn't taking a full feed, but 2/3 of one, and it spends on the order of 6 seconds blocked with disk activity every 30 secs. I'm not quite sure, but it also seems like any access to this disk (such as `ls -l /news') is blocked during the time the history files on the disk are being updated -- similarly a seek with `less' within /news/log/news.notice. `expire' also causes things to grind to a crawl -- even when `nice'd, the incoming article rate drops to about one third of normal. I won't say there's no improvement, since it's hard to tell with the variable flow of news, but so far I don't see the improvement that is needed for me to be able to keep up with a full incoming news feed, which I do see on the companion box using NetBSD and trickle sync, where the time INN spends on history file access drops to just over a second out of every 5 minutes, compared with more than 100 seconds using the current FreeBSD k0deZ. More importantly, I haven't seen any problems with it yet, and I'm eagerly looking forward to the best 20% of the fix to come... (I haven't tried tweaking any sysctl knobs to see if they make any difference, this is pretty much a standard installation with the same old INN k0deZ as on the other test machines) barry bouwsma, newsmangler & netscum -- *** This was posted with the express permission of *** ****************************************************** ** HIS HIGHNESS KAAZMANN LORD AND MASTER OF USENET ** ****************************************************** ********* We are simple servants of his will ********* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 19:12:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CE23737B6E1 for ; Tue, 4 Apr 2000 19:12:42 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115273>; Wed, 5 Apr 2000 12:13:04 +1000 Content-return: prohibited From: Peter Jeremy Subject: Re: Neat kernel development environment. In-reply-to: <200003311831.KAA30865@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Apr 01, 2000 at 04:32:36AM +1000 To: Matthew Dillon Cc: current@FreeBSD.ORG Message-Id: <00Apr5.121304est.115273@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003311831.KAA30865@apollo.backplane.com> Date: Wed, 5 Apr 2000 12:13:03 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 01, 2000 at 04:32:36AM +1000, Matthew Dillon wrote: > I can just see all the coolness seeping out. Now guys, we have to > have as a goal something at least as comparable as what IBM did > with one of their mainframes. Oh, say, lets shoot for being able to > run 4000 copies or so of linux under VMWare on FreeBSD :-) Since VMWare is our equivalent of IBM VM/CMS's CP, how about being able to run 4000 _nested_ copies of FreeBSD :-). (Run FreeBSD on real H/W, start VMWare, run FreeBSD under VMware and recurse). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 19:20: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id BB0BC37B8D1; Tue, 4 Apr 2000 19:19:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA72439; Tue, 4 Apr 2000 19:19:00 -0700 (PDT) (envelope-from dillon) Date: Tue, 4 Apr 2000 19:19:00 -0700 (PDT) From: Matthew Dillon Message-Id: <200004050219.TAA72439@apollo.backplane.com> To: Kun Limfjordsporter Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Woo. Okay, so I took the bait and snarfed the k0deZ from midday GMT :02.April, and have built a suitable SMP kernel and world, and that's :what I've been running for one news peering swerver for a spell. : :... : :As I noted in the earlier message I just sent, disabling the write- :behind via the sysctl knob didn't make an outstanding difference in :performance -- innd was still unresponsive during the time that the :random history database files needed updating for somewhere around :10 to 15 seconds when handling a full feed. I would have been very surprised if these changes made innd work better :-) These changes fix a case that innd does not usually generate. Even though innd's history files are hash-based, they are large enough that I would not expect one to typically hit the read-after-write case that the commit fixed. The innd problem is a different issue entirely, one related either to dirtying pages via mmap() or to excessive dirty pages in the buffer cache. You might be able to mitigate the problem somewhat by lowering the 'vfs.hidirtybuffers' sysctl, or maybe not. :I don't see any problems with the latest code changes (of 2 1/2 days :ago), as the machine has been running without problems for more than :a day now. I just don't see the improvement I am hoping for. This :machine isn't taking a full feed, but 2/3 of one, and it spends :on the order of 6 seconds blocked with disk activity every 30 secs. That's good. I didn't expect any problems with the write-behind fixes, they are fairly trivial. :I'm not quite sure, but it also seems like any access to this disk :(such as `ls -l /news') is blocked during the time the history files :on the disk are being updated -- similarly a seek with `less' within This is a different issue -- this is an issue of the disk write queues getting too long and/or the buffer cache getting starved and blocking other I/O while draining. :variable flow of news, but so far I don't see the improvement that :is needed for me to be able to keep up with a full incoming news :feed, which I do see on the companion box using NetBSD and trickle :sync, where the time INN spends on history file access drops to just :over a second out of every 5 minutes, compared with more than 100 :seconds using the current FreeBSD k0deZ. :... : :barry bouwsma, newsmangler & netscum -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 19:20:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 190E637BD9B for ; Tue, 4 Apr 2000 19:20:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA72492; Tue, 4 Apr 2000 19:20:40 -0700 (PDT) (envelope-from dillon) Date: Tue, 4 Apr 2000 19:20:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200004050220.TAA72492@apollo.backplane.com> To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: signal mask from jmp_buf References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi all, : :What is the proper way for obtaining the signal mask from :within the jmp_buf struct on 4.x or -current? Previously :with the JDK port for < 3.x we did something like this: : : signalMask = jmpbuf[0]._sjb[6]; : :This no longer works now that we support >32 signals. Is :there a better, more portable way that will work for all :versions of FreeBSD? : :Thanks. : :-steve The only portable way I can think of is to create super-jump-buf structure --- one containing the standard jmpbuf plus a signal mask, and then make an extra system call to populate the signal mask portion of the structure. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 19:45:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from fuggle.veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id A043D37BCBF for ; Tue, 4 Apr 2000 19:45:16 -0700 (PDT) (envelope-from veldy@veldy.net) Received: from veldy (cascade.veldy.net [192.168.0.1]) by fuggle.veldy.net (Postfix) with SMTP id C31D618E5 for ; Tue, 4 Apr 2000 21:49:04 -0500 (CDT) Message-ID: <002e01bf9ea9$2e343be0$0100a8c0@veldy.net> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Is current.freebsd.org running Linux? Date: Tue, 4 Apr 2000 21:46:42 -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.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is this machine (current.freebsd.org) always rejecting guest privileges and why won't ANYBODY answer the question? Thanks in advance, Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 19:50:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id 3062937BCE9 for ; Tue, 4 Apr 2000 19:50:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA03464; Tue, 4 Apr 2000 19:55:35 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004050255.TAA03464@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current" Subject: Re: Is current.freebsd.org running Linux? In-reply-to: Your message of "Tue, 04 Apr 2000 21:46:42 CDT." <002e01bf9ea9$2e343be0$0100a8c0@veldy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Apr 2000 19:55:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why is this machine (current.freebsd.org) always rejecting guest privileges > and why won't ANYBODY answer the question? Because it's been answered about a dozen times already; it's down with hardware problems, and the people responsible are trying to do something about it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 20:52: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from gate.keisu.t.u-tokyo.ac.jp (gate.keisu.t.u-tokyo.ac.jp [133.11.68.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B04437BCFE for ; Tue, 4 Apr 2000 20:51:56 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from sylph.sat.t.u-tokyo.ac.jp (sylph.sat.t.u-tokyo.ac.jp [10.6.1.20]) by gate.keisu.t.u-tokyo.ac.jp (Postfix) with ESMTP id A8CBF3DDA; Wed, 5 Apr 2000 12:51:53 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by sylph.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id AFD072DAA9; Wed, 5 Apr 2000 12:51:52 +0900 (JST) Received: from ett.sat.t.u-tokyo.ac.jp by ett.sat.t.u-tokyo.ac.jp (8.9.3/sat-V0.6) id MAA67826; Wed, 5 Apr 2000 12:51:52 +0900 (JST) Date: Wed, 05 Apr 2000 12:51:51 +0900 Message-ID: From: Hidetoshi Shimokawa To: veldy@veldy.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is current.freebsd.org running Linux? In-Reply-To: In your message of "Tue, 4 Apr 2000 21:46:42 -0500" <002e01bf9ea9$2e343be0$0100a8c0@veldy.net> References: <002e01bf9ea9$2e343be0$0100a8c0@veldy.net> User-Agent: Wanderlust/2.2.9 (Gonna Make You Sweat) SEMI/1.13.6 (Komatsu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.2 (beta19) (Shinjuku) (i386-unknown-freebsd3.2) X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX; Tue, 4 Apr 2000 21:07:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA94910; Tue, 4 Apr 2000 22:07:54 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA73183; Tue, 4 Apr 2000 22:07:09 -0600 (MDT) Message-Id: <200004050407.WAA73183@harmony.village.org> To: Takahashi Yoshihiro Subject: Re: Please review newbus patch for amd and adv Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Apr 2000 23:33:26 +0900." <20000403233326V.nyan@dd.catv.ne.jp> References: <20000403233326V.nyan@dd.catv.ne.jp> <20000402230532V.nyan@dd.catv.ne.jp> <200004030103.TAA56398@harmony.village.org> <200004030613.AAA59095@harmony.village.org> Date: Tue, 04 Apr 2000 22:07:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000403233326V.nyan@dd.catv.ne.jp> Takahashi Yoshihiro writes: : There is not ISA bus on PC-98. So, we can't use devices for ISA bus on : PC-98. But, PC-98 has `Cbus' which is like ISA bus in software place. : As most codes for ISA bus are useful for Cbus, the code for Cbus is : based on the code for ISA bus. Hmmm. It seems that it would be useful to work this concept into the newbus system. Not having one of these boxes, I can only speculate about how to accomplish this task. For now, it seems to be the right thing. Alternatively, you could provide dummy stub isadma routines that would cause a warning to be printed when they are used, or panic the machine or something to get people's attention. That might be a good interrum solution to moving these files to the md config files. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 21:14:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5603737B732; Tue, 4 Apr 2000 21:14:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA85172; Tue, 4 Apr 2000 21:14:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 4 Apr 2000 21:14:14 -0700 (PDT) From: Kris Kennaway To: "Matthew D. Fuller" Cc: Ben Rosengart , current@FreeBSD.ORG Subject: Re: sshd library problems In-Reply-To: <20000404172852.C1916@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Matthew D. Fuller wrote: > > ** RSA_PKCS1: Unable to find an RSA implemenation shared library. > (Aren't those filenames reversed? Just a hunch...) Thanks for catching these - I've just fixed the typos. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 21:14:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 33C0737B5E2 for ; Tue, 4 Apr 2000 21:14:54 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa17-08.ix.netcom.com [207.93.156.8]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA24588 for ; Wed, 5 Apr 2000 00:14:50 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.9.3) id VAA00436; Tue, 4 Apr 2000 21:14:47 -0700 (PDT) (envelope-from tomdean) Date: Tue, 4 Apr 2000 21:14:47 -0700 (PDT) Message-Id: <200004050414.VAA00436@ix.netcom.com> From: "Thomas D. Dean" To: freebsd-current@FreeBSD.ORG Subject: Upgrade 3.4 -> 5.0 -current Success Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded a 3.4 system from the Jan. 2000 CD to 5.0 -current. I used the 3.4 CD as an installation vehicle to get -current on a new disk, cleaning the tree in the process. I removed about 100MB that had accumulated over three years tracking -current. I had an existing -current system, and was installing a larger disk. I installed the 3.4 normal user, bin and docs on the new disk. I copied /etc, /usr/src and /usr/ports from the old -current disk. I did a make world to upgrade to -current. 'make world' had two problems. The buildworld phase completed successfully. There were two problems in the install phase. 1. install-info. The 3.4 version of install-info does not support the newest version of the flags, it wants -section, not -dsection. I copied the version in /usr/obj/usr/src/i386/usr/bin to /usr/bin and this problem was solved. Can 'make install' use /usr/obj/usr/src/i386/usr/bin/install-info? 2. sh is installed and then is used in later in the installation process. The number of syscalls changed, so the new version of sh core dumps. I copied a 5.0-current kernel from another disk, rebooted, and install completed without error. Can make copy or link the existing version of sh to tools and use that during the install? Good work on the make/install process. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 21:18:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 0F26537B528 for ; Tue, 4 Apr 2000 21:18:08 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA04115; Wed, 5 Apr 2000 00:17:56 -0400 (EDT) Date: Wed, 5 Apr 2000 00:17:56 -0400 (EDT) From: Daniel Eischen Message-Id: <200004050417.AAA04115@pcnet1.pcnet.com> To: current@FreeBSD.ORG, sprice@hiwaay.net Subject: Re: signal mask from jmp_buf Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > > What is the proper way for obtaining the signal mask from > within the jmp_buf struct on 4.x or -current? Previously > with the JDK port for < 3.x we did something like this: > > signalMask = jmpbuf[0]._sjb[6]; > > This no longer works now that we support >32 signals. Is > there a better, more portable way that will work for all > versions of FreeBSD? > > Thanks. Hmm, OK, I'll bite. One of the things I've been looking at is getting rid of the sigprocmask() calls within setjmp/longjmp for libc_r (basically just switching to use _setjmp/_longjmp instead, since the threads library already knows what the signal mask of each thread is). If we supported {get,set}context, I'd say use those instead of setjmp/longjmp since the signal mask is in ucp->uc_sigmask. I do have working {get,set,make,swap}context implemented as library routines for i386 (and also _getcontext,_setcontext which don't get/set the signal masks), and am working on the alpha bits (could use some help here). I am unfamiliar with the JDK port. Does it use FreeBSD native threads? The threads library knows what each threads signal mask is, and we should be able to eliminate the system calls to get/set the signal masks if we switch to the non-signal mask saving/restoring versions of these functions. Can you not use pthread_sigmask() to get/set the signal mask for each thread? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 21:24: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 5115C37BCB1 for ; Tue, 4 Apr 2000 21:24:00 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id WAA05845; Tue, 4 Apr 2000 22:23:58 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id WAA12987; Tue, 4 Apr 2000 22:23:57 -0600 (MDT) (envelope-from nate) Date: Tue, 4 Apr 2000 22:23:57 -0600 (MDT) Message-Id: <200004050423.WAA12987@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Daniel Eischen Cc: current@FreeBSD.ORG, sprice@hiwaay.net Subject: Re: signal mask from jmp_buf In-Reply-To: <200004050417.AAA04115@pcnet1.pcnet.com> References: <200004050417.AAA04115@pcnet1.pcnet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What is the proper way for obtaining the signal mask from > > within the jmp_buf struct on 4.x or -current? Previously > > with the JDK port for < 3.x we did something like this: > > > > signalMask = jmpbuf[0]._sjb[6]; > > > > This no longer works now that we support >32 signals. Is > > there a better, more portable way that will work for all > > versions of FreeBSD? > > > > Thanks. > > Hmm, OK, I'll bite. > > One of the things I've been looking at is getting rid of the > sigprocmask() calls within setjmp/longjmp for libc_r (basically > just switching to use _setjmp/_longjmp instead, since the > threads library already knows what the signal mask of each > thread is). Note, the JDK doesn't use the threads library, and instead uses it's own thread library that is optimized for the JDK, so a solution that is specific to libc_r won't necessarily help the JDK, although it may help others. > If we supported {get,set}context, I'd say use those instead > of setjmp/longjmp since the signal mask is in ucp->uc_sigmask. > I do have working {get,set,make,swap}context implemented as > library routines for i386 (and also _getcontext,_setcontext > which don't get/set the signal masks), and am working on the > alpha bits (could use some help here). > > I am unfamiliar with the JDK port. Does it use FreeBSD native > threads? Nope, see above. If/when FreeBSD gets 'real' kernel threads, it would be worthwhile to move it to using them, but until that team my suspicion is the optimzed 'threads' library that is part of the JDK probably is an easier solution for the JDK. However, Steve may have a different opinion. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 22:24:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id E955D37BD56; Tue, 4 Apr 2000 22:24:17 -0700 (PDT) (envelope-from freebeer@fluffy.gets.an.analprobe.dk) Received: from localhost (freebeer@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id HAA08200; Wed, 5 Apr 2000 07:24:08 +0200 (CEST) (envelope-from freebeer@fluffy.gets.an.analprobe.dk) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: freebeer owned process doing -bs Date: Wed, 5 Apr 2000 07:24:08 +0200 (CEST) From: Kun Limfjordsporter X-Sender: freebeer@fLuFFy.iNt.tElE.dK Reply-To: FreeBSD-manglers@netscum.dk To: Matthew Dillon Cc: current@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: FreeBSD random I/O performance issues In-Reply-To: Message-ID: Organization: Department of Superfluous Headers MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Apr 19100, Matthew Dillon wrote: > :performance -- innd was still unresponsive during the time that the > :random history database files needed updating for somewhere around > :10 to 15 seconds when handling a full feed. > > The innd problem is a different issue entirely, one related > either to dirtying pages via mmap() or to excessive dirty > pages in the buffer cache. > > You might be able to mitigate the problem somewhat by lowering > the 'vfs.hidirtybuffers' sysctl, or maybe not. I'll take door number two, please! Just for grins, I went ahead with 5.0 and tuned the hidirtybuffers down from the default of 1410 in steps down to 400, and nope, I still see the ~6 seconds of freeze that I saw with the higher value. No improvement. No consolation prize. > :I don't see any problems with the latest code changes (of 2 1/2 days > :ago), as the machine has been running without problems for more than > > That's good. I didn't expect any problems with the > write-behind fixes, they are fairly trivial. Now about this ahc0 RECOVERED ERROR that just showed up, I guess it will be time to toss another Sun disk out the window Real Soon Now. Anyway, I'll be looking forward to see what effect the rest of the fix has on things, in hopes of matching either the NetBSD or Slowaris performance but without the problems of either, please, thankyoumuch thanks agin from the fluffy your mother should have warned you about -- *** This was posted with the express permission of *** ****************************************************** ** HIS HIGHNESS KAAZMANN LORD AND MASTER OF USENET ** ****************************************************** ********* We are simple servants of his will ********* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 22:29: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id D464037B93E for ; Tue, 4 Apr 2000 22:28:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA66904; Wed, 5 Apr 2000 14:58:26 +0930 (CST) Date: Wed, 5 Apr 2000 14:58:26 +0930 From: Greg Lehey To: Soren Schmidt Cc: Brad Knowles , Jeroen Ruigrok/Asmodai , Matthew Dillon , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch) Message-ID: <20000405145826.A66569@freebie.lemis.com> References: <200004041331.PAA89789@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004041331.PAA89789@freebsd.dk> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 4 April 2000 at 15:31:00 +0200, Søren Schmidt wrote: > It seems Brad Knowles wrote: >> >> Like I said in a previous message, Poul broke vinum (among other >> things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul >> had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't >> have been affected. But he didn't, and it was. > > Where the fsck did you get the idea that RELENG_4 was broken by > Poul's commits to -CURRENT ?? > Poul has nothing to do with vinum being broken in RELENG_4... Correct. phk broke some stuff in Vinum in -CURRENT, and that's been fixed. There's some long-standing breakage in Vinum in combination with RAID-5 and ATA/IDE. I'm quite capable of doing this kind of breakage without phk's help. I have now identified the problem, with Matt Dillon's help, and will fix Real Soon Now. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 22:32:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id A7BEE37B845 for ; Tue, 4 Apr 2000 22:32:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA66944; Wed, 5 Apr 2000 15:02:03 +0930 (CST) Date: Wed, 5 Apr 2000 15:02:03 +0930 From: Greg Lehey To: Poul-Henning Kamp Cc: Brad Knowles , Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG Subject: Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch) Message-ID: <20000405150203.B66569@freebie.lemis.com> References: <27235.954855223@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0pre2i In-Reply-To: <27235.954855223@critter.freebsd.dk> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: Linuxcare, Inc. Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 4 April 2000 at 15:33:43 +0200, Poul-Henning Kamp wrote: > In message , Brad Knowles writes: >> At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: >> >>> Like I said in another mail, this is CURRENT, things are >>> expected to break. You want stability of API's, go 3-STABLE. You want >>> a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have >>> your bandages ready. >> >> Like I said in a previous message, Poul broke vinum (among other >> things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul >> had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't >> have been affected. But he didn't, and it was. > > Brad, > > You are confused. > > I have not made one single commit to 4.0-STABLE which even comes > close to vinum. > > The problem in vinum/releng4 is the problem greg has been blaming > on CAM since at least FreeBSDcon and indications seems to be that > it is actually a malloc/free gottcha in vinum. No, this is not correct. The problem you're talking about I blamed elsewhere, not specifically CAM. To quote from http://www.lemis.com/vinum/bugs.html: Technical explanation: A buffer header gets corrupted between the time the top half of the driver issues the request to the disk driver, and when the I/O completes. Currently, the evidence is pointing towards the disk driver, but the corruption is of such an unusual nature that it's difficult to guess what's going on. This bug went away without me making any change to Vinum, so I feel that my opinion is correct. This isn't the bug which Søren has been seeing, and indeed your last lot of commits made it impossible for the bug to ever show up again in this form (since there is no longer a B_CALL in the buffer header). Greg -- Linuxcare - BSD support for the revolution. See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 4 22:37:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 9ED8237BDBD for ; Tue, 4 Apr 2000 22:37:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id HAA32009; Wed, 5 Apr 2000 07:37:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Brad Knowles , Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG Subject: Re: Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch) In-reply-to: Your message of "Wed, 05 Apr 2000 15:02:03 +0930." <20000405150203.B66569@freebie.lemis.com> Date: Wed, 05 Apr 2000 07:37:12 +0200 Message-ID: <32007.954913032@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000405150203.B66569@freebie.lemis.com>, Greg Lehey writes: >> >> The problem in vinum/releng4 is the problem greg has been blaming >> on CAM since at least FreeBSDcon and indications seems to be that >> it is actually a malloc/free gottcha in vinum. > >No, this is not correct. The problem you're talking about I blamed >elsewhere, not specifically CAM. To quote from >http://www.lemis.com/vinum/bugs.html: OK, sorry, I havn't heard about it since FreeBSDcon and back then CAM was in the spotlight. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 0:10: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id C167E37B868 for ; Wed, 5 Apr 2000 00:10:02 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA21435; Wed, 5 Apr 2000 00:10:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current" Subject: Re: Is current.freebsd.org running Linux? In-reply-to: Your message of "Tue, 04 Apr 2000 21:46:42 CDT." <002e01bf9ea9$2e343be0$0100a8c0@veldy.net> Date: Wed, 05 Apr 2000 00:10:38 -0700 Message-ID: <21432.954918638@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is down right now. It will be back soon. Thanks for asking so loudly. > Why is this machine (current.freebsd.org) always rejecting guest privileges > and why won't ANYBODY answer the question? > > Thanks in advance, > > Tom Veldhouse > veldy@veldy.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 0:51: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id CEE9D37BE57 for ; Wed, 5 Apr 2000 00:50:56 -0700 (PDT) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id QAA21431; Wed, 5 Apr 2000 16:50:54 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma021144; Wed, 5 Apr 00 16:50:19 +0900 Received: from jkpc15.tk.kubota.co.jp ([192.168.7.250]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id QAA09312 for ; Wed, 5 Apr 2000 16:50:18 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-02/21/99) with ESMTP id QAA53926 for ; Wed, 5 Apr 2000 16:47:18 +0900 (JST) To: freebsd-current@freebsd.org Subject: installworld fail with rtquery X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000405164718V.haro@tk.kubota.co.jp> Date: Wed, 05 Apr 2000 16:47:18 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, When I do installworld, it fails in src/sbin/routed/rtquery: install -c -s -o root -g wheel -m 555 rtquery usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 If I fix src/sbin/routed/Makefile.inc like following, error seems to go away. --- src/sbin/routed/Makefile.inc.ctm Sun Jan 10 19:43:43 1999 +++ src/sbin/routed/Makefile.inc Wed Apr 5 16:46:21 2000 @@ -1 +1,4 @@ -.include "../../Makefile.inc" +# $FreeBSD$ + +.include "${.CURDIR}/../../Makefile.inc" + Is it only me, or am I doing something wrong? Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Development, Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 Email: haro@tk.kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 0:57:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id ED44837BE53 for ; Wed, 5 Apr 2000 00:57:25 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id DAA10262; Wed, 5 Apr 2000 03:57:18 -0400 (EDT) Message-ID: <20000405035718.A9789@netmonger.net> Date: Wed, 5 Apr 2000 03:57:18 -0400 From: Christopher Masto To: Nick Hibma , Paul Haddad Cc: FreeBSD CURRENT Mailing List Subject: Re: USB/Orb/kue/iopener/filesystem corruption References: <008501bf9b84$ad365270$0bac2ac0@pth.com> <20000403132725.B8685@netmonger.net> <20000404184022.A15164@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <20000404184022.A15164@netmonger.net>; from Christopher Masto on Tue, Apr 04, 2000 at 06:40:22PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those following along, it's definately kue-related. On Tue, Apr 04, 2000 at 06:40:22PM -0400, Christopher Masto wrote: > Next time I get a chance, I'll try: > > Filesystem-intensive activity without using kue at all, then a > reboot and fsck. Tested, absolutely no problems. In fact, I'm writing this from the i-opener (running ppp). > Loading kue as a module. Same disaster. Instant filesystem damage if I use the maching at all with kue up. > Simulating the i-opener situation with my laptop. Haven't tried yet.. it's nearly 4AM. > Getting more details on the kernel panic. Haven't managed a panic this time around. I'm still stumped as to what exactly is going on.. whether kue is corrupting random memory, or umass's buffers.. I may just try to find an aue-based adapter to try. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 0:58:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 811FF37B594 for ; Wed, 5 Apr 2000 00:58:28 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12ckhd-0005bk-00; Wed, 05 Apr 2000 09:58:17 +0200 Date: Wed, 5 Apr 2000 09:58:17 +0200 From: Neil Blakey-Milner To: "Thomas D. Dean" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrade 3.4 -> 5.0 -current Success Message-ID: <20000405095817.A21265@mithrandr.moria.org> References: <200004050414.VAA00436@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004050414.VAA00436@ix.netcom.com> Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 2000-04-04 (21:14), Thomas D. Dean wrote: > I installed the 3.4 normal user, bin and docs on the new disk. I > copied /etc, /usr/src and /usr/ports from the old -current disk. I > did a make world to upgrade to -current. > > 'make world' had two problems. The buildworld phase completed > successfully. There were two problems in the install phase. > > 1. install-info. The 3.4 version of install-info does not support > the newest version of the flags, it wants -section, not > -dsection. I copied the version in > /usr/obj/usr/src/i386/usr/bin to /usr/bin and this problem was > solved. Can 'make install' use > /usr/obj/usr/src/i386/usr/bin/install-info? This is a known problem, and unfortunately my solution to it broke cross-compilation. Someone more intelligent may just fix it soon. > 2. sh is installed and then is used in later in the installation > process. The number of syscalls changed, so the new version of > sh core dumps. I copied a 5.0-current kernel from another disk, > rebooted, and install completed without error. Can make copy > or link the existing version of sh to tools and use that during > the install? I think you're supposed to reboot with a new kernel (built with 'make buildkernel && make installkernel') and then installworld. This is the new 'one true way'. It's not supposed to work over more than one major version, so I doubt 3.4 -> 5.0 will work for much longer. > Good work on the make/install process. Cool. Marcel and others deserve a massive round of applause. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 2: 0:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.nildram.co.uk (mercury.nildram.co.uk [195.112.4.37]) by hub.freebsd.org (Postfix) with ESMTP id 200DF37BCA6 for ; Wed, 5 Apr 2000 02:00:09 -0700 (PDT) (envelope-from freebsd@unix-consult.com) Received: from nermal.unix-consult.com (tgeusch.dial.nildram.co.uk [195.149.29.39]) by mercury.nildram.co.uk (8.10.0.Beta12/8.10.0.Beta10) with ESMTP id e3593ct20154 for ; Wed, 5 Apr 2000 10:03:38 +0100 Received: (qmail 44922 invoked from network); 5 Apr 2000 07:07:17 -0000 Received: from odie.unix-consult.com (192.168.0.2) by nermal.unix-consult.com with SMTP; 5 Apr 2000 07:07:17 -0000 Received: (qmail 308 invoked by uid 1002); 5 Apr 2000 07:06:04 -0000 Date: Wed, 5 Apr 2000 08:06:04 +0100 From: Timo Geusch To: Adrian Chadd Cc: Kris Kennaway , current@freebsd.org Subject: Re: UNIONFS Message-ID: <20000405080604.A255@odie.unix-consult.com> References: <20000404074034.A290@odie.unix-consult.com> <20000404220530.B53939@ewok.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000404220530.B53939@ewok.creative.net.au>; from adrian@freebsd.org on Tue, Apr 04, 2000 at 10:05:32PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000 at 10:05:32PM +0800, Adrian Chadd wrote: > On Tue, Apr 04, 2000, Kris Kennaway wrote: > > On Tue, 4 Apr 2000, Timo Geusch wrote: > > > > > Here be dragons, I know :-). Got myself a nice juicy & reproducable > > > crash here, so I thought I might as well try to track down this > > > problem. But before I start,is anyone else working on this one? I'd > > > hate to waste my not exactly ample time trying to duplicate somebody > > > else's work. > > > > Frankly, unless you have the time to fix unionfs completely I wouldn't > > bother. We know it's broken, whats needed is someone with a good handle on > > the VFS code to sit down and spend a week or so to fix it. On the other > > hand, if that's you then go for it (you'd certainly learn a lot of useful > > things in the process) > > > > I'm starting VFS hacking again :) Throw up a PR, I'll assign it to myself > and I'll look at it for you. Thanks, I was looking at the crash dump and at the source code and frankly, it does my head in. I'll file a PR tonight; crashdump etc are available on request/for download. Now what I need is some docs that give me a halfway decent understanding on how UNIONFS works so I can do some debugging myself. The 4.4BSD book is a bit curt on it... Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 2:25:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 269C837B84F for ; Wed, 5 Apr 2000 02:25:25 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12cm3u-000G0J-0C; Wed, 5 Apr 2000 09:25:22 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id KAA98127; Wed, 5 Apr 2000 10:27:40 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Wed, 5 Apr 2000 10:22:10 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Christopher Masto Cc: Paul Haddad , FreeBSD CURRENT Mailing List Subject: Re: USB/Orb/kue/iopener/filesystem corruption In-Reply-To: <20000404211341.E28658@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why does this sound like the warning that is written in the manual of > > the Iomega Zip drive: > > > > do not connect more than one Zip drive to the same USB host data > > might corrupted. > > > > Or something similar... > > But.. but.. I only have the one drive connected. It could be that heavy Bulk traffic gives data corruption on the wire. I've not been able to track what they meant when they said that some parts do not correctly check CRC. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 3:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from garantia.nnov.ru (garantia.nnov.ru [212.67.2.250]) by hub.freebsd.org (Postfix) with ESMTP id 4B78237C177 for ; Wed, 5 Apr 2000 03:49:08 -0700 (PDT) (envelope-from didenko@garantia.nnov.ru) Received: from didenko.garantia.nnov.ru (didenko.garantia.nnov.ru [192.168.1.192]) by garantia.nnov.ru (8.9.3/8.9.1) with SMTP id OAA35696 for ; Wed, 5 Apr 2000 14:49:06 +0400 (MSD) (envelope-from didenko@garantia.nnov.ru) Date: Wed, 5 Apr 2000 14:47:09 +0400 From: Maxim Didenko X-Mailer: The Bat! (v1.33) UNREG / CD5BF9353B3B7091 Reply-To: Maxim Didenko Organization: Bank "Garantia" X-Priority: 3 (Normal) Message-ID: <1616.000405@garantia.nnov.ru> To: freebsd-current@freebsd.org Subject: FreeBSD 4.0-RELEASE installation trouble Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody, I try to install FreeBSD 4.0-RELEASE on Dell PowerEdge SP 5100 with integrated PCI SCSI NCR controller (chip label is "Symbols Logic 53C810a 609-0392140 DR00218 9627N"). At boot time controller outputs "NCR SDMS (TM) v3.0 PCI SCSI BIOS PCI Rev. 2.0 NCRPCI-3.07.02". After loading kernel and MFS root diskettes, kernel tries to load driver for SCSI controller but forever loop begins with following messages: (noperiph:sym0:0:-1:-1): SCSI BUS reset detected sym0:0:ERROR (C0:0) (8-0-0) (0/3) @ (script 138:80080000). sym0: script cmd=720d0000 sym0: regdump: ca 00 00 03 47 00 1f 00 08 07 00 08 00 08 02 00 08 ee 02 20 ff ff ff. sym0: PCI STATUS=0x8100 When I disabled SCSI controller in system's BIOS, I got following messages: sym0: <810a> irq 0 at device 15.0 on pci0 sym0: failed to allocate MMIO resourses fatal trap 12 : page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0229c9d stack pointer = 0x10:0xc05fbce8 frame pointer = 0x10:0xc05fbcf8 code segment = base 0x0, limit 0xfffff, tape 0x1b = DOL 0, pres 1, def 32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 0(swapper) interrupt mask = net tty bio cam trap number = 12 panic: page fault FreeBSD 3.3 works on this system without problems. What's wrong? Best regards, Maxim Didenko didenko@garantia.nnov.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 5:11:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id 0DDDE37B7D3 for ; Wed, 5 Apr 2000 05:11:24 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (harconia-2-179.mdm.mke.execpc.com [169.207.133.245]) by mailgw00.execpc.com (8.9.1) id HAA32141; Wed, 5 Apr 2000 07:11:16 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 9EA0C17A; Wed, 5 Apr 2000 07:13:29 -0500 (CDT) X-Mailer: exmh version 2.1.1 10/16/1999 To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: Dangerously looking glitch (4.0-STABLE) In-reply-to: Your message of "Tue, 04 Apr 2000 20:56:38 +0300." <38EA2CD6.24636F65@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Apr 2000 07:13:29 -0500 From: Jon Hamilton Message-Id: <20000405121329.9EA0C17A@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38EA2CD6.24636F65@altavista.net>, Maxim Sobolev wrote: } This is a multi-part message in MIME format. } --------------3D64CAE46133EFA188180FFD } Content-Type: text/plain; charset=koi8-r } Content-Transfer-Encoding: 7bit } } Hi, } } I've tried to track down why my own script which is cleaning non-matching } distfiles from time to time produce incorrect results (just cvsup'ed 4.0). } After some digging I've found that this bug could be easily reproduced by doi } ng } "find -exec md5" on large set of files several times consequiently, and then } comparing results. You can see that md5 checksum of the one of the files is How many in a "large set"? I tried 10 passes on my 4.0-stable machine and was not able to replicate your results, though I only have about 500 files in my distfiles. I tried the same in /usr/src, and in another area with both large and small files (393,000 total), all of which came up clean. I think you have a hardware problem somewhere :( -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 6: 9:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 708C537B7C1 for ; Wed, 5 Apr 2000 06:09:20 -0700 (PDT) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 8F89D97AA; Wed, 5 Apr 2000 15:09:21 +0200 (MET DST) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id PAA01275; Wed, 5 Apr 2000 15:09:51 +0200 (CEST) (envelope-from fn@gatekeeper.radio-do.de) Date: Wed, 5 Apr 2000 15:09:51 +0200 From: Frank Nobis To: Jon Hamilton Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) Message-ID: <20000405150951.A1142@radio-do.de> References: <38EA2CD6.24636F65@altavista.net> <20000405121329.9EA0C17A@woodstock.monkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000405121329.9EA0C17A@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: > > up clean. I think you have a hardware problem somewhere :( That is very likely a hardwre problem. I have a nfs server under 3.4-S here running, It was easy to crash the system with much I/O over nfs on a 100M Ethernet connection. (I did a dump and the machine paniced) The same over a slower 10M ethernet, but it took longer to crash. Now I replaced a very old adaptec 1542cf with a 2940U. I did the same stress test, but got no more panics. Even a load of 80% interrupts didn't kill the machine. Maybe you have a similar problem. -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 6:28: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 2FBEB37B548 for ; Wed, 5 Apr 2000 06:28:01 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup8-60.iptelecom.net.ua [212.9.227.252]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA24096; Wed, 5 Apr 2000 16:34:30 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id QAA03943; Wed, 5 Apr 2000 16:27:20 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EB3F35.EF0E287A@altavista.net> Date: Wed, 05 Apr 2000 16:27:17 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Frank Nobis Cc: Jon Hamilton , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) References: <38EA2CD6.24636F65@altavista.net> <20000405121329.9EA0C17A@woodstock.monkey.net> <20000405150951.A1142@radio-do.de> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Nobis wrote: > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: > > > > up clean. I think you have a hardware problem somewhere :( > > That is very likely a hardwre problem. I have a nfs server under 3.4-S > here running, It was easy to crash the system with much I/O over nfs > on a 100M Ethernet connection. (I did a dump and the machine paniced) > > The same over a slower 10M ethernet, but it took longer to crash. > > Now I replaced a very old adaptec 1542cf with a 2940U. I did the same > stress test, but got no more panics. Even a load of 80% interrupts > didn't kill the machine. > > Maybe you have a similar problem. It is unlikely, because I've never seen this problem previously when 3.[01234] was installed on this hardware. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 6:29:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id C1A1C37B69F for ; Wed, 5 Apr 2000 06:28:55 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id PAA99513 for current@freebsd.org; Wed, 5 Apr 2000 15:28:32 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004051328.PAA99513@zibbi.mikom.csir.co.za> Subject: burncd problem To: current@freebsd.org Date: Wed, 5 Apr 2000 15:28:32 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have installed 4.0-STABLE on our machine with the CD burner and when I tried to burn a CD, the session went as follows: ======= tien# burncd -s 4 -f /dev/acd0c data 4.0-install.iso fixate next writeable LBA 0 writing from file 4.0-install.iso size 641174 KB written this track 641174 KB (100%) total 641174 KB fixating CD, please wait.. burncd: ioctl(CDRIOCCLOSEDISK): Input/output error tien# ======= In this time the kernel spit out the following messages: ======= Apr 5 09:49:39 tien /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 Apr 5 10:07:25 tien /kernel: acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 Apr 5 10:07:25 tien /kernel: acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 ====== The CD writer is an HP 8100 and I have used it before without problems with a much older version of 4-CURRENT, that is before the ata driver. Does anybody else have problems with the HP 8100 series? I have included dmesg.boot at the end. John -- John Hay -- John.Hay@mikom.csir.co.za Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-20000403-STABLE #0: Tue Apr 4 02:17:15 GMT 2000 root@dolphin.mikom.csir.co.za:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 134205440 (131060K bytes) avail memory = 126693376 (123724K bytes) Preloaded elf kernel "kernel" at 0xc03c3000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xc800-0xc80f at device 4.1 on pci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 5 chip1: port 0xe800-0xe80f at device 4.3 on pci0 ncr0: port 0xc000-0xc0ff mem 0xe0800000-0xe08000ff irq 12 at device 10.0 on pci0 ncr0: driver is using old-style compatability shims fxp0: port 0xb800-0xb81f mem 0xe0000000-0xe00fffff,0xe2000000-0xe2000fff irq 10 at device 11.0 on pci0 fxp0: Ethernet address 00:a0:c9:e8:0f:1f fxp0: supplying EUI64: 00:a0:c9:ff:fe:e8:0f:1f xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xb400-0xb43f irq 11 at device 12.0 on pci0 xl0: Ethernet address: 00:60:08:9f:82:e4 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 acd0: CD-RW at ata1-master using PIO3 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2058MB (4216172 512 byte sectors: 255H 63S/T 262C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 6:35:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 25C7137B740; Wed, 5 Apr 2000 06:35:26 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12cpxh-000NUy-0U; Wed, 5 Apr 2000 14:35:18 +0100 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id OAA12437; Wed, 5 Apr 2000 14:37:27 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Wed, 5 Apr 2000 14:31:55 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD STABLE Mailing List , FreeBSD CURRENT Mailing List Subject: Parallel port zip drives - inventory of working and non-working systems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could anyone who uses a Parallel Zip drive with FreeBSD 4.0 and up ('and better' I almost wrote there :-) send me a message wether it works? I'm trying to resolve PR 16153, but have no clue where to look If it does not work, please tell me - what version of the OS you are using - at which point it stoppped working (date, version of FreeBSD, which upgrade step, etc.) - if possible and you are willing, please send me the output dmesg as an attachment. Thanks in advance! Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 6:46:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id E86A037B9DB for ; Wed, 5 Apr 2000 06:46:08 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [149.173.6.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id JAA10623; Wed, 5 Apr 2000 09:44:39 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08034; Wed, 5 Apr 2000 09:44:09 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.1) id JAA15337; Wed, 5 Apr 2000 09:44:08 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <200004051344.JAA15337@dean.pc.sas.com> Subject: Re: Vinum breakage (was: 2nd call for reviews and tests: buf->bio patch) In-Reply-To: <20000405150203.B66569@freebie.lemis.com> from Greg Lehey at "Apr 5, 2000 03:02:03 pm" To: Greg Lehey Date: Wed, 5 Apr 2000 09:44:08 -0400 (EDT) Cc: Poul-Henning Kamp , Brad Knowles , Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > Technical explanation: A buffer header gets corrupted between the > time the top half of the driver issues the request to the disk > driver, and when the I/O completes. Currently, the evidence is > pointing towards the disk driver, but the corruption is of such an > unusual nature that it's difficult to guess what's going on. This type of bug sounds like a perfect candidate for using the kernel's hardware debug support (on IA32), and would allow you to take a trace trap and drop to the kernel debugger when anyone modifies the buffer header, assuming you can cover the corrupted area with the 4 debug registers available, which can cover a range of 16 bytes, in 4 byte chunks. This is exactly the type of situation that inspired me to add the support in the first place. Hopefully, when I get a little bit of time, I can merge the code that I use so that we can do this in a straight forward way from within the kernel debugger. -Brian -- Brian Dean brdean@unx.sas.com SAS Institute Inc. bsd@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7: 1:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 14AD037B804 for ; Wed, 5 Apr 2000 07:01:32 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup1-59.iptelecom.net.ua [212.9.226.59]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA01473; Wed, 5 Apr 2000 17:08:05 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id QAA03913; Wed, 5 Apr 2000 16:24:32 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EB3E8C.7E9ACA94@altavista.net> Date: Wed, 05 Apr 2000 16:24:29 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Jon Hamilton Cc: current@freebsd.org Subject: Re: Dangerously looking glitch (4.0-STABLE) References: <20000405121329.9EA0C17A@woodstock.monkey.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Hamilton wrote: > In message <38EA2CD6.24636F65@altavista.net>, Maxim Sobolev wrote: > } This is a multi-part message in MIME format. > } --------------3D64CAE46133EFA188180FFD > } Content-Type: text/plain; charset=koi8-r > } Content-Transfer-Encoding: 7bit > } > } Hi, > } > } I've tried to track down why my own script which is cleaning non-matching > } distfiles from time to time produce incorrect results (just cvsup'ed 4.0). > } After some digging I've found that this bug could be easily reproduced by doi > } ng > } "find -exec md5" on large set of files several times consequiently, and then > } comparing results. You can see that md5 checksum of the one of the files is > > How many in a "large set"? I tried 10 passes on my 4.0-stable machine > and was not able to replicate your results, though I only have about 500 > files in my distfiles. I tried the same in /usr/src, and in another > area with both large and small files (393,000 total), all of which came > up clean. I think you have a hardware problem somewhere :( I've tried it on my home machine and failed to reproduce also. However it is strange, because if it is the CPU/Memory problem, then there should be other signs - random applications crashes, spontaneous reboots etc., but machine is pretty stable - up and running for weeks since 4.0-REL w/o any notable problems. On the other hand if it is HDD problem or problem with its cable, then there should also be some signs. I've never seen this problem on the same hardware under 2.* and 3.* during past 1.5 years. Maybe it is ata driver, because it is the only thing that is known not very extensively tested (and has already acknoweleged problems with some hardware). I'll try to fallback to the wd and look what will happen. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:11:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from netvalue-gw.netvalue.fr (netvalue-gw.netvalue.fr [195.115.44.161]) by hub.freebsd.org (Postfix) with ESMTP id 678C037BC2C for ; Wed, 5 Apr 2000 07:11:02 -0700 (PDT) (envelope-from erwan@netvalue.com) Received: (from bin@localhost) by netvalue-gw.netvalue.fr (8.9.3/8.8.8) id QAA79616 for ; Wed, 5 Apr 2000 16:11:00 +0200 (CEST) (envelope-from erwan@netvalue.com) X-Authentication-Warning: netvalue-gw.netvalue.fr: bin set sender to using -f Received: from (dauphine.netvalue.fr [192.168.1.13]) by netvalue-gw.netvalue.fr via smap (V2.1) id xma079607; Wed, 5 Apr 00 16:10:43 +0200 Received: from netvalue.com ([192.168.1.1]) by mail.netvalue.fr (Netscape Messaging Server 3.6) with ESMTP id AAA6FC5; Wed, 5 Apr 2000 16:10:42 +0200 Message-ID: <38EB4961.EEDC98D4@netvalue.com> Date: Wed, 05 Apr 2000 16:10:41 +0200 From: Erwan Arzur Organization: NetValue S.A. X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en, fr-FR MIME-Version: 1.0 To: Maxim Didenko Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 4.0-RELEASE installation trouble References: <1616.000405@garantia.nnov.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maxim Didenko wrote: > > Hello everybody, > > I try to install FreeBSD 4.0-RELEASE on Dell PowerEdge SP 5100 with > integrated PCI SCSI NCR controller (chip label is "Symbols Logic > 53C810a 609-0392140 DR00218 9627N"). At boot time controller outputs > "NCR SDMS (TM) v3.0 PCI SCSI BIOS PCI Rev. 2.0 NCRPCI-3.07.02". > After loading kernel and MFS root diskettes, kernel tries to load > driver for SCSI controller but forever loop begins with following > messages: > (noperiph:sym0:0:-1:-1): SCSI BUS reset detected > sym0:0:ERROR (C0:0) (8-0-0) (0/3) @ (script 138:80080000). > sym0: script cmd=720d0000 > sym0: regdump: ca 00 00 03 47 00 1f 00 08 07 00 08 00 08 02 00 08 ee > 02 20 ff ff ff. > sym0: PCI STATUS=0x8100 Did you try to use the ncr driver too ? My /sys/i386/conf/LINT says : device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) and the 53C810 is a rather old beast ... -- UNIX *IS* user friendly. It's just selective about who its friends are. --unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:24:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from shell.telemere.net (shell.telemere.net [63.224.9.3]) by hub.freebsd.org (Postfix) with ESMTP id E4CCA37B5B3 for ; Wed, 5 Apr 2000 07:24:36 -0700 (PDT) (envelope-from visigoth@telemere.net) Received: by shell.telemere.net (Postfix, from userid 1001) id 2B88470601; Wed, 5 Apr 2000 09:32:21 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by shell.telemere.net (Postfix) with ESMTP id 281CE6C801; Wed, 5 Apr 2000 09:32:21 -0500 (CDT) Date: Wed, 5 Apr 2000 09:32:21 -0500 (CDT) From: Visigoth To: Hidetoshi Shimokawa Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is current.freebsd.org running Linux? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > current.jp.freebsd.org is another stable/current build machine. > > /\ Hidetoshi Shimokawa Thanks Hidetoshi, but I think my meager 3 years of nihongo in highschool are not going to be enough to run a Japanese snapshot just yet... Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net ____________________________________________________________________________ | - M$ Win 2K was built for the internet. | - Unix _BUILT_ the internet. | FreeBSD - The POWER to serve | http://www.freebsd.org your call... | | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:31: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D4DFD37BA07 for ; Wed, 5 Apr 2000 07:31:00 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA46863; Wed, 5 Apr 2000 16:29:38 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004051429.QAA46863@freebsd.dk> Subject: Re: burncd problem In-Reply-To: <200004051328.PAA99513@zibbi.mikom.csir.co.za> from John Hay at "Apr 5, 2000 03:28:32 pm" To: jhay@mikom.csir.co.za (John Hay) Date: Wed, 5 Apr 2000 16:29:38 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems John Hay wrote: > Hi, > > I have installed 4.0-STABLE on our machine with the CD burner and when > I tried to burn a CD, the session went as follows: > > ======= > tien# burncd -s 4 -f /dev/acd0c data 4.0-install.iso fixate > next writeable LBA 0 > writing from file 4.0-install.iso size 641174 KB > written this track 641174 KB (100%) total 641174 KB > fixating CD, please wait.. > burncd: ioctl(CDRIOCCLOSEDISK): Input/output error > tien# > ======= > > In this time the kernel spit out the following messages: > > ======= > Apr 5 09:49:39 tien /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 > Apr 5 10:07:25 tien /kernel: acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 > Apr 5 10:07:25 tien /kernel: acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 > ====== > > The CD writer is an HP 8100 and I have used it before without problems > with a much older version of 4-CURRENT, that is before the ata driver. Hmm you are the second to report that, but I also have reports that says it works. Maybe we are facing different firmaware versions... However I cannot reproduce the problem on any of my drives (but I dont have access to a 8100), so I'm not sure what to do about it. There was a change in atapi-cd.c at a time that changes the problem, it doesn't fix it, it just moves it somewhere else, and that change does break other devices... Hmm, I guess I'll have to try to locate a 8100 somewhere and try to find out what it doesn't like... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1B7DD37B6FC for ; Wed, 5 Apr 2000 07:32:15 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA47392; Wed, 5 Apr 2000 16:31:41 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004051431.QAA47392@freebsd.dk> Subject: Re: Dangerously looking glitch (4.0-STABLE) In-Reply-To: <38EB3E8C.7E9ACA94@altavista.net> from Maxim Sobolev at "Apr 5, 2000 04:24:29 pm" To: sobomax@altavista.net (Maxim Sobolev) Date: Wed, 5 Apr 2000 16:31:40 +0200 (CEST) Cc: hamilton@pobox.com (Jon Hamilton), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Maxim Sobolev wrote: > > I've tried it on my home machine and failed to reproduce also. However it is > strange, because if it is the CPU/Memory problem, then there should be other signs > - random applications crashes, spontaneous reboots etc., but machine is pretty > stable - up and running for weeks since 4.0-REL w/o any notable problems. On the > other hand if it is HDD problem or problem with its cable, then there should also > be some signs. I've never seen this problem on the same hardware under 2.* and 3.* > during past 1.5 years. Maybe it is ata driver, because it is the only thing that is > known not very extensively tested (and has already acknoweleged problems with some > hardware). I'll try to fallback to the wd and look what will happen. Uhm what acknowledged problems is that ? I know of no cases of data corruption in this way, its all pretty much go/nogo situations... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:34:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from gate.keisu.t.u-tokyo.ac.jp (gate.keisu.t.u-tokyo.ac.jp [133.11.68.1]) by hub.freebsd.org (Postfix) with ESMTP id B0CB237B57A for ; Wed, 5 Apr 2000 07:34:15 -0700 (PDT) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from sylph.sat.t.u-tokyo.ac.jp (sylph.sat.t.u-tokyo.ac.jp [10.6.1.20]) by gate.keisu.t.u-tokyo.ac.jp (Postfix) with ESMTP id 39A423DD9; Wed, 5 Apr 2000 23:34:14 +0900 (JST) Received: from localhost (ett.sat.t.u-tokyo.ac.jp [10.6.1.30]) by sylph.sat.t.u-tokyo.ac.jp (Postfix) with ESMTP id CAC5F2DAA9; Wed, 5 Apr 2000 23:34:12 +0900 (JST) To: visigoth@telemere.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is current.freebsd.org running Linux? In-Reply-To: References: X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX Date: Wed, 05 Apr 2000 23:34:12 +0900 From: Hidetoshi Shimokawa X-Dispatcher: imput version 20000113(IM136) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Visigoth Subject: Re: Is current.freebsd.org running Linux? Date: Wed, 5 Apr 2000 09:32:21 -0500 (CDT) Message-ID: visigoth> visigoth> > current.jp.freebsd.org is another stable/current build machine. visigoth> > visigoth> > /\ Hidetoshi Shimokawa visigoth> visigoth> Thanks Hidetoshi, but I think my meager 3 years of nihongo in highschool visigoth> are not going to be enough to run a Japanese snapshot just yet... There is not so much differece from snapshot built on current.freebsd.org except that crypto library source comes from cvsup.internat.freebsd.org. See http://current.jp.freebsd.org for detail. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:39:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 30EE337B57A; Wed, 5 Apr 2000 07:39:25 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12cqxe-0007sr-00; Wed, 5 Apr 2000 15:39:14 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA13696; Wed, 5 Apr 2000 15:39:14 +0100 (BST) (envelope-from jcm) Date: Wed, 5 Apr 2000 15:39:14 +0100 From: J McKitrick To: Nick Hibma Cc: FreeBSD STABLE Mailing List , FreeBSD CURRENT Mailing List Subject: Re: Parallel port zip drives - inventory of working and non-working systems Message-ID: <20000405153914.A13658@dogma.freebsd-uk.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from n_hibma@calcaphon.com on Wed, Apr 05, 2000 at 02:31:55PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone recall seeing or making a remark about a group of interrupts or hardware port locations that could be causing this problem? I was searching my email and i can't find it. Someone said 4.0 allocates a group of hardware locations (0x380-0x3f0?) differently from 3.4, and that this may affect the parallel port allocation on laptops. Has anyone had this zip timeout error on a desktop machine and not been able to fix it? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 7:49: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 02BBD37BDC0 for ; Wed, 5 Apr 2000 07:48:55 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id QAA67192; Wed, 5 Apr 2000 16:34:57 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200004051434.QAA67192@info.iet.unipi.it> Subject: Re: burncd problem In-Reply-To: <200004051429.QAA46863@freebsd.dk> from Soren Schmidt at "Apr 5, 2000 04:29:38 pm" To: Soren Schmidt Date: Wed, 5 Apr 2000 16:34:57 +0200 (CEST) Cc: John Hay , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm you are the second to report that, but I also have reports that > says it works. Maybe we are facing different firmaware versions... > > However I cannot reproduce the problem on any of my drives (but > I dont have access to a 8100), so I'm not sure what to do about > it. There was a change in atapi-cd.c at a time that changes the > problem, it doesn't fix it, it just moves it somewhere else, and > that change does break other devices... > Hmm, I guess I'll have to try to locate a 8100 somewhere and > try to find out what it doesn't like... and i guess i have to try and reproduce this on the 8200 here :) cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 8: 4: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 84EBE37BBAF for ; Wed, 5 Apr 2000 08:04:02 -0700 (PDT) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id 0FB72DDB81 for ; Wed, 5 Apr 2000 11:04:33 -0400 (EDT) Message-ID: <38EB566A.97628A3A@infolibria.com> Date: Wed, 05 Apr 2000 11:06:18 -0400 From: John LoVerso Organization: InfoLibria X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Neat kernel development environment. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the same way that OS servers under Mach3 were developed and debugged! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 8: 9:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id 52F1C37B65B for ; Wed, 5 Apr 2000 08:09:46 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id D07721905C; Wed, 5 Apr 2000 17:09:23 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id AC05E539; Wed, 5 Apr 2000 17:09:23 +0200 (CEST) Date: Wed, 5 Apr 2000 17:09:23 +0200 To: freebsd-current@freebsd.org Subject: Booting -CURRENT on Compaq Armada V300 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-04-05-17-09-23+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As described in i386/17228, the following patch, which disables DMA on ATAPI if not explicitely enabled, makes my Compaq Aramada V300 laptop able to boot -CURRENT. While this patch may not be correct, it shows once again that DMA is playing an active role in the lockup described in the PR. I'll provide detailled kernel information as soon as I've installed FreeBSD on the laptop, now that I have working boot disks. Sam Index: ata-dma.c =================================================================== RCS file: /usr/cvs/src/sys/dev/ata/ata-dma.c,v retrieving revision 1.35 diff -u -r1.35 ata-dma.c --- ata-dma.c 2000/03/05 16:52:24 1.35 +++ ata-dma.c 2000/04/05 14:35:02 @@ -70,6 +70,10 @@ if (!scp->bmaddr) return; +#ifndef ATA_ENABLE_ATAPI_DMA + return; +#endif + /* if simplex controller, only allow DMA on primary channel */ if (scp->unit == 1) { outb(scp->bmaddr + ATA_BMSTAT_PORT, inb(scp->bmaddr + ATA_BMSTAT_PORT) & To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 8:31:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 6EBB637BCB2; Wed, 5 Apr 2000 08:31:15 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id E4DD9DCB0; Wed, 5 Apr 2000 17:31:02 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: Date: Wed, 5 Apr 2000 17:30:43 +0200 To: FreeBSD-CURRENT Mailing List , FreeBSD-STABLE Mailing List From: Brad Knowles Subject: Kudos to all! Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I'd like to extend my thanks and give kudos to all who have been involved in the process of creating FreeBSD 4.0, from -CURRENT up through -STABLE, and beyond to wherever that might take us. We had a new Dell PowerEdge 6350/500 server that arrived here yesterday, and although the machine was bought to run Windows NT as a games server, the admin of the machine wanted to install and run Linux on it first, just to play around. Well, Slackware, Debian, and RedHat all seriously bombed out in one way or another. He even tried OpenBSD, but again no luck. They were convinced that there was a very serious hardware problem, and that they'd have to ship the machine back. On a lark, I slipped in a FreeBSD 4.0-RELEASE kernel floppy, and began what is clearly the easiest and simplest boot & installation procedure that they appear to have ever seen. It worked the first time without a single hiccup, it installed in *way* less time than anything else they've ever done before, and I think I pretty seriously embarrassed them. ;-) I don't know if this will win us any converts from the die-hard Linux camp, but I think it certainly demonstrates the quality of the product that this project has produced. Oh, and the machine did get very quickly wiped -- it's running NT now. However, I don't think they'll ever bother to try to run Linux on it again. ;-) -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 8:49: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C7D4937B63D for ; Wed, 5 Apr 2000 08:49:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA78448; Wed, 5 Apr 2000 08:49:01 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 08:49:01 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051549.IAA78448@apollo.backplane.com> To: Brian Dean Cc: Greg Lehey , Poul-Henning Kamp , Brad Knowles , Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tracked down two bugs in vinum's raid5 implementation and submitted a tentitive patch to Greg for evaluation. It seems to fix the panics I was able to reproduce. The patch is available (but note that once Greg commits the real fix, you need to wipe it before you cvs update): http://www.backplane.com/FreeBSD4/ Greg is likely to commit a modified form of this patch once we work through the issues it brought to light. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9: 7: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A8DBC37B744 for ; Wed, 5 Apr 2000 09:07:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA78646; Wed, 5 Apr 2000 09:06:59 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 09:06:59 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051606.JAA78646@apollo.backplane.com> To: Brian Dean , Greg Lehey , Poul-Henning Kamp , Brad Knowles , Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (needless to say, the patch I posted is relative to FreeBSD-4.x, not 5) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9:26:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from trixie.city-net.com (trixie.city-net.com [198.144.32.5]) by hub.freebsd.org (Postfix) with ESMTP id 6206737B63D for ; Wed, 5 Apr 2000 09:26:34 -0700 (PDT) (envelope-from douglas@spridle.city-net.com) Received: from spridle.city-net.com (spridle.city-net.com [206.151.184.3]) by trixie.city-net.com (8.9.3/8.9.3) with ESMTP id NAA27764 for ; Wed, 5 Apr 2000 13:27:25 -0400 Received: (from douglas@localhost) by spridle.city-net.com (8.9.1a/8.9.1) id MAA708973 for freebsd-current@freebsd.org; Wed, 5 Apr 2000 12:26:44 -0400 (EDT) From: "G. Douglas Davidson" Message-Id: <10004051226.ZM775683@spridle.city-net.com> Date: Wed, 5 Apr 2000 12:26:42 -0400 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current -- ----- G Douglas Davidson | CityNet, Inc. douglas@city-net.com | Pittsburgh, PA voice: 412.481.5406 | fax: 412.431.1315 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from puku.zamnet.zm (puku.zamnet.zm [208.224.176.40]) by hub.freebsd.org (Postfix) with ESMTP id 2A90637B5A2 for ; Wed, 5 Apr 2000 09:30:06 -0700 (PDT) (envelope-from daniel@zamnet.zm) Received: from zamnet.zm (thor.zamnet.zm [208.224.176.91]) by puku.zamnet.zm (8.10.0/8.10.0) with ESMTP id e35GUJa06283 for ; Wed, 5 Apr 2000 18:30:19 +0200 (ZMT) Message-ID: <38EB6A60.341F4FBC@zamnet.zm> Date: Wed, 05 Apr 2000 18:31:28 +0200 From: Daniel Mpolokoso X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: 4.0 RELEASE trouble Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've got FreeBSD 4.0 RELEASE running on a Compaq Deskpro with an Intel 810 motherboard. I'm running the machine as a POP3 server using Qmail's POP3D daemon. For some unknown reason, the machine keeps rebooting every 3 - 4 hours. I'm not sure how to get it to log the details of the panic so I don't have any trace of the problem. I'd be grateful for pointers on how to debug the kernel panic or any information relating to the Intel 810 motherboard. I've attached output from dmesg. Thanks, Daniel. --- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #3: Wed Apr 5 16:50:35 CAT 2000 daniel@mail.zamnet.zm:/usr/src/sys/compile/PUKU Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon (498.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 200278016 (195584K bytes) avail memory = 190967808 (186492K bytes) Preloaded elf kernel "kernel" at 0xc02f7000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 1.0 irq 11 pcib1: at device 30.0 on pci0 pci1: on pcib1 rl0: port 0x1000-0x10ff mem 0x40000000-0x400000ff irq 11 at device 13.0 on pci1 rl0: Ethernet address: 00:e0:29:5c:e5:48 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: supplying EUI64: 00:e0:29:ff:fe:5c:e5:48 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x2460-0x246f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 31.2 irq 11 chip1: port 0x2400-0x243f,0x2000-0x20ff irq 11 at device 31.5 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ad0: 4112MB [8912/15/63] at ata0-master using UDMA33 ad1: 6149MB [13328/15/63] at ata0-slave using UDMA33 acd0: CDROM at ata1-slave using PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted rl0: starting DAD for fe80:0001::02e0:29ff:fe5c:e548 rl0: DAD complete for fe80:0001::02e0:29ff:fe5c:e548 - no duplicates found ------------------------------------------------------------------------ Daniel Mpolokoso - Managing Director (Act.), Email: daniel@zamnet.zm ZAMNET Communication Systems Limited, Phone: +260 - 1 - 763065 P.O. Box 38299, Lusaka, Zambia. Fax: +260 - 1 - 224775 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9:37:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 305A037B63F for ; Wed, 5 Apr 2000 09:37:36 -0700 (PDT) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id MAA01555; Wed, 5 Apr 2000 12:37:24 -0400 (EDT) Date: Wed, 5 Apr 2000 12:37:24 -0400 From: Mathew Kanner To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Vinum breakage Message-ID: <20000405123724.A24249@cs.mcgill.ca> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.94.15i In-Reply-To: Matthew Dillon's message [Re: Vinum breakage] as of Wed, Apr 05, 2000 at 09:06:59AM -0700 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 05, Matthew Dillon wrote: > (needless to say, the patch I posted is relative to FreeBSD-4.x, not = 5) >=20 > -Matt > Matthew Dillon=20 > >=20 Here's what I got, don't put too much salt into it, somehow, the disks are a mix of ata66 and ata33. It also happened the exact moment I did a control-t to get the status of a tar. I'll try again with all ata/33 or all ata/66 later tonight. --Mat Script started on Wed Apr 5 12:33:13 2000 bash-2.03# 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 condition= s. 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) core-file(kgdb) =1B[Kexec-file /kernel=0D (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...cdone. (kgdb) core-file /usr/tmp/vmcore.6 IdlePTD 4157440 initial pcb at 364ec0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x4 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc274cf3c stack pointer =3D 0x10:0xc032198c frame pointer =3D 0x10:0xc03219a8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D Idle interrupt mask =3D bio=20 trap number =3D 12 panic: page fault syncing disks...=20 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x30 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc025e120 stack pointer =3D 0x10:0xc03217c4 frame pointer =3D 0x10:0xc03217c8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D Idle interrupt mask =3D bio=20 trap number =3D 12 panic: page fault Uptime: 17m47s dumping to dev #ad/0x20001, offset 3047552 dump ata0: resetting devices .. done 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=20 --- #0 boot (howto=3D260) at ../../kern/kern_shutdown.c:304 304 dumppcb.pcb_cr3 =3D rcr3(); (kgdb) where #0 boot (howto=3D260) at ../../kern/kern_shutdown.c:304 #1 0xc017fa18 in poweroff_wait (junk=3D0xc0317dcf, howto=3D0) at ../../kern/kern_shutdown.c:554 #2 0xc02ba969 in trap_fatal (frame=3D0xc0321784, eva=3D48) at ../../i386/i386/trap.c:924 #3 0xc02ba641 in trap_pfault (frame=3D0xc0321784, usermode=3D0, eva=3D48) at ../../i386/i386/trap.c:817 #4 0xc02ba237 in trap (frame=3D{tf_fs =3D -1070465008, tf_es =3D -10722344= 80,=20 tf_ds =3D -1028587504, tf_edi =3D 0, tf_esi =3D 0, tf_ebp =3D -107045= 8936,=20 tf_isp =3D -1070458960, tf_ebx =3D -1070357604, tf_edx =3D 1074284608= ,=20 tf_ecx =3D -1030717427, tf_eax =3D 0, tf_trapno =3D 12, tf_err =3D 0,= =20 tf_eip =3D -1071259360, tf_cs =3D 8, tf_eflags =3D 66050, tf_esp =3D = -855983880,=20 tf_ss =3D -1070458912}) at ../../i386/i386/trap.c:423 #5 0xc025e120 in acquire_lock (lk=3D0xc033a39c) at ../../ufs/ffs/ffs_softdep.c:282 #6 0xc0263290 in softdep_count_dependencies (bp=3D0xccfab8f8, wantcount=3D= 0) at ../../ufs/ffs/ffs_softdep.c:4535 #7 0xc02663c4 in ffs_fsync (ap=3D0xc032183c) at ../../ufs/ffs/ffs_vnops.c:= 168 #8 0xc0264f73 in ffs_sync (mp=3D0xc2905c00, waitfor=3D2, cred=3D0xc10c5900= ,=20 p=3D0xc037c540) at vnode_if.h:537 #9 0xc01aac8f in sync (p=3D0xc037c540, uap=3D0x0) at ../../kern/vfs_syscal= ls.c:549 #10 0xc017f467 in boot (howto=3D256) at ../../kern/kern_shutdown.c:226 #11 0xc017fa18 in poweroff_wait (junk=3D0xc0317dcf, howto=3D0) at ../../kern/kern_shutdown.c:554 ---Type to continue, or q to quit--- #12 0xc02ba969 in trap_fatal (frame=3D0xc032194c, eva=3D4) at ../../i386/i386/trap.c:924 #13 0xc02ba641 in trap_pfault (frame=3D0xc032194c, usermode=3D0, eva=3D4) at ../../i386/i386/trap.c:817 #14 0xc02ba237 in trap (frame=3D{tf_fs =3D 16, tf_es =3D 16, tf_ds =3D -102= 8325360,=20 tf_edi =3D -1030706144, tf_esi =3D -1028598720, tf_ebp =3D -107045845= 6,=20 tf_isp =3D -1070458504, tf_ebx =3D -1032780800, tf_edx =3D 1074284608= ,=20 tf_ecx =3D -1070458424, tf_eax =3D 0, tf_trapno =3D 12, tf_err =3D 0,= =20 tf_eip =3D -1032532164, tf_cs =3D 8, tf_eflags =3D 66178,=20 tf_esp =3D -1032780800, tf_ss =3D -1028598720}) at ../../i386/i386/tr= ap.c:423 #15 0xc274cf3c in ?? () #16 0xc01a329b in biodone (bp=3D0xc290ac20) at ../../kern/vfs_bio.c:2697 #17 0xc02913ee in ad_interrupt (request=3D0xc2b0d440) at ../../dev/ata/ata-disk.c:555 #18 0xc028dde6 in ata_intr (data=3D0xc261f380) at ../../dev/ata/ata-all.c:1= 122 #19 0xc02ccfe1 in intr_mux (arg=3D0xc10be820) at ../../i386/isa/intr_machdep.c:569 (kgdb) quit bash-2.03# exit Script done on Wed Apr 5 12:33:45 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9:46:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from ams2eusosrv15.ams.ops.eu.uu.net (ams2eusosrv15.ams.ops.eu.uu.net [146.188.99.70]) by hub.freebsd.org (Postfix) with ESMTP id 3451F37B63D for ; Wed, 5 Apr 2000 09:46:42 -0700 (PDT) (envelope-from mroorda@eu.uu.net) Received: from ams2eusosrv20.ams.ops.eu.uu.net by ams2eusosrv15.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: ams2eusosrv20.ams.ops.eu.uu.net [146.188.99.75]) id QQijpz04269 for ; Wed, 5 Apr 2000 16:46:34 GMT Received: from jmnoc28.ams.ops.eu.uu.net by ams2eusosrv20.ams.ops.eu.uu.net with ESMTP (peer crosschecked as: jmnoc28.ams.ops.eu.uu.net [146.188.98.24]) id QQijpy00203 for ; Wed, 5 Apr 2000 16:44:44 GMT Received: from localhost by jmnoc28.ams.ops.eu.uu.net with SMTP (peer crosschecked as: mroorda@localhost) id QQijpy03324; Wed, 5 Apr 2000 18:44:44 +0200 (MET DST) Message-Id: X-Organization: UUNET, EMEA Operations X-Address: J. Muyskenweg 22, 1097 CJ Amsterdam, The netherlands X-Phone: +31 20 711 6000 X-Fax: +31 20 711 6001 X-ncc-regid: nl.nlnet To: current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Fri, 24 Sep 1999 00:50:00 -0700" <199909240750.AAA02115@dingo.cdrom.com> From: Anne Marcel Roorda Date: Wed, 05 Apr 2000 18:44:43 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith once wrote: >> After doing a cvsup yesterday evening i can't seem to boot on >my >> raid cotroller using the same kernel config. >> >> Is -current probing hardware i a different way now or ?? > >This is a consequence of a defect in the way that the ida driver >works, >and new code which resorts the disk drivers (so that the 'wd' >driver >throws out the 'ida' driver). > >The correct fix for this is nontrivial and a little while off; >you >might want to go back to your old kernel for a while if the >issue >hasn't already been resolved. > >-- >\\ The mind's the standard \\ Mike Smith >\\ of the man. \\ msmith@freebsd.org >\\ -- Joseph Merrick \\ msmith@cdrom.com Hi, I'm trying to install 4.0-RELEASE on a COMPAQ Proliant 1850R with the root disk on a SMART-2SL raid controller. The install works perfectly, but boot/loader fails to load the kernel. Booting "kernel" fails with 'Don't know how to load module "/kernel"', and boot kernel.GENERIC fails for unknown reasons. (It loads partly, but then falls back to the loader). Is there an easy way to get this to work, or do I need to start thinking about adding a seperate root disk? Thanks, - marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 9:49:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 532CB37B86B for ; Wed, 5 Apr 2000 09:49:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA78992; Wed, 5 Apr 2000 09:49:12 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 09:49:12 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051649.JAA78992@apollo.backplane.com> To: Mathew Kanner Cc: current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Apr 05, Matthew Dillon wrote: :> (needless to say, the patch I posted is relative to FreeBSD-4.x, not 5) :> :> -Matt :> Matthew Dillon :> :> : : Here's what I got, don't put too much salt into it, somehow, :the disks are a mix of ata66 and ata33. It also happened the exact :moment I did a control-t to get the status of a tar. I'll try again :with all ata/33 or all ata/66 later tonight. : : --Mat I'm crossing my fingers and hoping it was the ^T -- wasn't there a big thread on ^T not being 'safe' a while back? I never use ^T myself. Also, as a general note to everyone, make sure you are building vinum into the kernel directly and not using it as a kld, just to ensure that it stays in sync with the kernel. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 10: 3:52 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 103FC37BBA8; Wed, 5 Apr 2000 10:03:50 -0700 (PDT) From: "Jonathan M. Bresler" To: dillon@apollo.backplane.com Cc: brdean@unx.sas.com, grog@lemis.com, phk@critter.freebsd.dk, blk@skynet.be, asmodai@wxs.nl, current@FreeBSD.ORG In-reply-to: <200004051549.IAA78448@apollo.backplane.com> (message from Matthew Dillon on Wed, 5 Apr 2000 08:49:01 -0700 (PDT)) Subject: Re: Vinum breakage Message-Id: <20000405170350.103FC37BBA8@hub.freebsd.org> Date: Wed, 5 Apr 2000 10:03:50 -0700 (PDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've tracked down two bugs in vinum's raid5 implementation and > submitted a tentitive patch to Greg for evaluation. It seems > to fix the panics I was able to reproduce. The patch is available > (but note that once Greg commits the real fix, you need to wipe it > before you cvs update): > > http://www.backplane.com/FreeBSD4/ > > Greg is likely to commit a modified form of this patch once we work > through the issues it brought to light. > > -Matt Matt, help me understand your patch. this is how i read it at this time: Matt has just made available an early patch that corrects the vinum panic. is this the same vinum panic that people are claiming phk created with the bio/buf changes? i dont know the vinum code. i dont know the bio/buf code. i do see that all the code changes are to vinum source files. none of the changes reference the buf/bio parts for the kernel. the patch is against 4.0, code unaffected by phk's changes. the revision levels are those indicated in Matt's patch and those I recevied via CVSup last night. the changes to vinuminterrupt.c from 1.25 to 1.29 appear to be: replace bp->b_flags with bp->b_ioflags and B_ERROR with BIO_ERROR bp->b_flags with bp->b_iocmd and B_READ with BIO_READ BUF_STRATEGY with DEV_STRATEGY rqe->b.b_flags &= ~(B_READ | B_DONE); with rqe->b.b_flags &= ~B_DONE; rqe->b.b_flags |= B_CALL; with rqe->b.b_iocmd = BIO_WRITE; the changes to vinumio.c from 1.52 to 1.55 appear to be the same as the first global search and replace listed above for vinuminterrupt.c the changes to vinumrequest.c from 1.44 to 1.48 appear to be the same as the first global search and replace listed above for vinuminterrupt.c. there are ALSO this change: 794,795c794,796 < bp->b_flags = ubp->b_flags & (B_ORDERED | B_NOCACHE | B_ASYNC); < bp->b_iocmd = BIO_READ; /* inform us when it 's done */ --- > bp->b_flags = ubp->b_flags & (B_NOCACHE | B_ASYNC); > bp->b_ioflags = ubp->b_ioflags & BIO_ORDERED; > bp->b_iocmd = ubp->b_iocmd; and 896c897 < else --- > else if (bp->b_iocmd == BIO_WRITE) /* writing, */ Matt's patch does not affect either area of the code. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 10: 5: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4F2B037B797 for ; Wed, 5 Apr 2000 10:04:47 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12crln-0004QX-00; Wed, 05 Apr 2000 16:31:03 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12crln-000Dkx-00; Wed, 05 Apr 2000 16:31:03 +0100 Date: Wed, 5 Apr 2000 16:31:03 +0100 From: Ben Smithurst To: John Hay Cc: current@freebsd.org Subject: Re: burncd problem Message-ID: <20000405163103.C93540@strontium.scientia.demon.co.uk> References: <200004051328.PAA99513@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200004051328.PAA99513@zibbi.mikom.csir.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > The CD writer is an HP 8100 and I have used it before without problems > with a much older version of 4-CURRENT, that is before the ata driver. > > Does anybody else have problems with the HP 8100 series? I have included > dmesg.boot at the end. Someone else reported problems with an HP 8100 on (I think) -stable recently. Maybe coincidence, maybe not. -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 10:12:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 4A38537BE0D for ; Wed, 5 Apr 2000 10:12:33 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 21FCEDDBC; Wed, 5 Apr 2000 19:10:13 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200004051649.JAA78992@apollo.backplane.com> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> Date: Wed, 5 Apr 2000 19:06:08 +0200 To: Matthew Dillon , Mathew Kanner From: Brad Knowles Subject: Re: Vinum breakage Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:49 AM -0700 2000/4/5, Matthew Dillon wrote: > Also, as a general note to everyone, make sure you are building vinum > into the kernel directly and not using it as a kld, just to ensure that > it stays in sync with the kernel. Isn't this in direct conflict with the instructions given for normally using vinum? Is this a temporary change, until we get over some of the current problems, or is this a more permanent change? Out of curiosity, is this your recommendation, or does Greg agree with it? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 10:32:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 547EC37BAB5 for ; Wed, 5 Apr 2000 10:32:25 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F547A.dip0.t-ipconnect.de [193.159.84.122]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id SAA31561; Wed, 5 Apr 2000 18:31:35 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 846C8AC2C; Wed, 5 Apr 2000 19:34:07 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id TAA08168; Wed, 5 Apr 2000 19:31:35 +0200 (CEST) (envelope-from alex) Date: Wed, 5 Apr 2000 19:31:34 +0200 From: Alexander Langer To: Soren Schmidt Cc: John Hay , current@FreeBSD.ORG Subject: Re: burncd problem Message-ID: <20000405193134.A8133@cichlids.cichlids.com> Mail-Followup-To: Soren Schmidt , John Hay , current@FreeBSD.ORG References: <200004051328.PAA99513@zibbi.mikom.csir.co.za> <200004051429.QAA46863@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004051429.QAA46863@freebsd.dk>; from sos@freebsd.dk on Wed, Apr 05, 2000 at 04:29:38PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Soren Schmidt (sos@freebsd.dk): > Hmm, I guess I'll have to try to locate a 8100 somewhere and > try to find out what it doesn't like... The Mitsumi 4801 does the same thing. If you can't fine a 8100, I could take a look at it - in a month or such. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 10:54:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9FA6437B797 for ; Wed, 5 Apr 2000 10:54:13 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e35IJp305772; Wed, 5 Apr 2000 11:19:51 -0700 (PDT) Date: Wed, 5 Apr 2000 11:19:51 -0700 From: Alfred Perlstein To: Greg Lehey Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c Message-ID: <20000405111950.F20770@fw.wintelcom.net> References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> <200004022338.QAA51565@apollo.backplane.com> <20000402172349.T21029@fw.wintelcom.net> <20000404100911.C53037@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000404100911.C53037@freebie.lemis.com>; from grog@lemis.com on Tue, Apr 04, 2000 at 10:09:11AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey [000403 18:07] wrote: > On Sunday, 2 April 2000 at 17:23:49 -0700, Alfred Perlstein wrote: > > * Matthew Dillon [000402 17:04] wrote: > >> > >> :I did look at the code, struct proc is allocated from a zone, > >> :meaning it won't "go away" once allocated, there's no danger in > >> :dereferencing p_pptr, I don't get it. > >> : > >> :-- > >> :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > >> :"I have the heart of a child; I keep it in a jar on my desk." > >> > >> What happens when the parent process exits and the system must > >> reassign the parent to process 1? Now think about what happens > >> when it occurs on one cpu while another is trying to access the > >> ppid. > >> > >> cpu#1: cpu#2: > >> > >> read p->p_pptr > >> indirect through to get ppid > >> (stalls on a cache miss plus, > >> due to heavy DMA, stalls on main memory) > >> parent process finishes > >> exiting, replaces p_pptr > >> of children, releases > >> struct proc. > >> > >> struct proc is reused, > >> pid is reallocated > >> read completes, wrong ppid is returned > >> (neither the original ppid nor ppid 1 > >> is returned). > >> > >> In an SMP system you have to assume the worst case, and the worst case > >> is that a cpu can stall INDEFINITELY between instructions. > > > > Good call. > > > > Ugh, I should think about this more, but i'll just grasp at straws > > and suggest that p_pptr is set to volatile variable, and we re-read > > it after we snarf the pid from the pointer and make sure it hasn't > > changed out from under us. > > > > Either that or store it in the child's proc struct as well. > > This seems the obvious solution. The version of Linux kernel source that I have uses the first: asmlinkage long sys_getppid(void) { int pid; struct task_struct * me = current; struct task_struct * parent; parent = me->p_opptr; for (;;) { pid = parent->pid; #if __SMP__ { struct task_struct *old = parent; mb(); parent = me->p_opptr; if (old != parent) continue; } #endif break; } return pid; } I like it. mb() is most certainly a "memory barrier" inline to force ordering constraints. interesting how they don't use volatile for the pointer though: /* * pointers to (original) parent process, youngest child, younger sibling, * older sibling, respectively. (p->father can be replaced with * p->p_pptr->pid) */ struct task_struct *p_opptr, *p_pptr, *p_cptr, *p_ysptr, *p_osptr; I prefer this method, we can't copy _everything_ into the child struct so we might as well do it this way. Feeling lazy, i'm wondering if we have the equivenlant of a mb() macro/inline we'll need one. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:12: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 685AE37B6FC for ; Wed, 5 Apr 2000 11:11:58 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA00729; Wed, 5 Apr 2000 11:16:38 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004051816.LAA00729@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Anne Marcel Roorda Cc: current@FreeBSD.ORG Subject: Re: Problem with Compaq SMART-2SL array controller In-reply-to: Your message of "Wed, 05 Apr 2000 18:44:43 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Apr 2000 11:16:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm trying to install 4.0-RELEASE on a COMPAQ Proliant 1850R > with the root disk on a SMART-2SL raid controller. The install > works perfectly, but boot/loader fails to load the kernel. > > Booting "kernel" fails with 'Don't know how to load module > "/kernel"', and boot kernel.GENERIC fails for unknown reasons. > (It loads partly, but then falls back to the loader). If it "falls back" you should get an error message. > Is there an easy way to get this to work, or do I need to > start thinking about adding a seperate root disk? Looks like you have data corruption problems here; it's possible that your array wasn't correctly built, or is malfunctioning. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:29:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id ED4F337B62B for ; Wed, 5 Apr 2000 11:29:51 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id C5E8C2DC07; Wed, 5 Apr 2000 20:33:37 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id E006A7811; Wed, 5 Apr 2000 20:25:56 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id DE1EF10E17 for ; Wed, 5 Apr 2000 20:25:56 +0200 (CEST) Date: Wed, 5 Apr 2000 20:25:56 +0200 (CEST) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Installworld to /some/where/... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is it possible to do an installworld not to / of existing system, but to, say, subdirs somewhere, which could be mountpoints for another disk? Something like: /mnt/installdir/ /mnt/installdir/compat /mnt/installdir/etc /mnt/installdir/usr /mnt/installdir/var /mnt/installdir/ The reason I'm asking is that I'm looking for a method to easily clone/upgrade a bunch of servers without having to do 'make world' on all of them. I'm not satisfied either with using dd - the machines are not identical, there are some bits and pieces of config specific to each machine. So far the best method was to do a make world, but it becomes more and more a nuisance and waste of time... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:40:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 47D9737B62B; Wed, 5 Apr 2000 11:40:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA54761; Wed, 5 Apr 2000 11:40:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 5 Apr 2000 11:40:14 -0700 (PDT) From: Kris Kennaway To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: Re: Installworld to /some/where/... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Apr 2000, Andrzej Bialecki wrote: > Is it possible to do an installworld not to / of existing system, but to, > say, subdirs somewhere, which could be mountpoints for another disk? DESTDIR? Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:41:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id C2B4D37B888 for ; Wed, 5 Apr 2000 11:41:39 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F547A.dip0.t-ipconnect.de [193.159.84.122]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id TAA19094; Wed, 5 Apr 2000 19:41:12 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 5DB03AC2C; Wed, 5 Apr 2000 20:43:45 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id UAA09405; Wed, 5 Apr 2000 20:41:13 +0200 (CEST) (envelope-from alex) Date: Wed, 5 Apr 2000 20:41:13 +0200 From: Alexander Langer To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installworld to /some/where/... Message-ID: <20000405204113.A9347@cichlids.cichlids.com> Mail-Followup-To: Andrzej Bialecki , freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from abial@webgiro.com on Wed, Apr 05, 2000 at 08:25:56PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Andrzej Bialecki (abial@webgiro.com): > The reason I'm asking is that I'm looking for a method to easily > clone/upgrade a bunch of servers without having to do 'make world' on all make DESTDIR=/mnt installworld Same counts for kernel-build. This belongs to -questions, not -current. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:42:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 737FA37B9E4; Wed, 5 Apr 2000 11:42:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA79600; Wed, 5 Apr 2000 11:42:40 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 11:42:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051842.LAA79600@apollo.backplane.com> To: "Jonathan M. Bresler" Cc: brdean@unx.sas.com, grog@lemis.com, phk@critter.freebsd.dk, blk@skynet.be, asmodai@wxs.nl, current@FreeBSD.ORG Subject: Vinum breakage Summary (was Re: Vinum breakage) References: <20000405170350.103FC37BBA8@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt, : help me understand your patch. this is how i read it at this :time: : : :Matt has just made available an early patch that corrects the vinum :panic. is this the same vinum panic that people are claiming phk :created with the bio/buf changes? i dont know the vinum code. i dont :know the bio/buf code. i do see that all the code changes are to :vinum source files. none of the changes reference the buf/bio parts :for the kernel. : :the patch is against 4.0, code unaffected by phk's changes. :the revision levels are those indicated in Matt's patch and those I :recevied via CVSup last night. There is a lot of confusion here, which I will straighten out: * 3/20 - phk makes his first buffer cache commit, adding b_iocmd. This breaks vinum, but it takes a while for people to realize it. (see 1.46 sys/dev/vinum/vinumrequest.c and other files) This commit is made into -current. -stable is not effected * 3/26 - alfred fixes phk's type-o that broke vinum (1.47 vinumrequest.c, and other files). (3/26 == last week). * During the last week, at aroudn the same time, a panic was traced definitively to vinum. On saturday it was traced to the raid5 code. Some of the people using vinum, including Greg, are using it under -current. * Phk begins making more radical commits (to -current) on sunday. * Confusion reigns. I don't think the later commits broke vinum again, but at this point there were a number of people focused on vinum and having the buffer cache ripped out from under them might have resulted in false positives due to people using vinum as a kld rather then building it into the kernel. I believe there was a message or two in this regard that turned out to be a false positive. * Greg's test machine was running -current. Greg is dead in the water at this point (i.e. he would need to retool to -stable), and complains mightily (and appropriately, I believe). Despites the truth that it would be better to track the vinum bug down in -stable, the fact remains that many people are using -current. * I start complaining about the lack of discussion, review, notification, or documentation prior to phk's commits. * Phk is referenced by Brad as breaking vinum in 4.0, which is incorrect (message-id ), on 4/4, and Brad retracts this later when the mistake is realized, also on 4/4. (more confusion added to the mix). * I spend five or six hours settings vinum up on my -stable test box to try to reproduce and fix the panic on monday. * I come up with a patch, which Greg is now reviewing & using as a basis for the 'real' fix. This patch fixes a bug in vinum -- we knew there was one (on saturday, see above). The only known bug introduced by phk's commit (so far) was fixed by Alfred on 3/26. This panic is not related to phk's commits. My patch is relative to 4.0. * It is currently unknown whether further breakage in -current exists due to phk's changes. I don't think we'll know whether there are further problems until the currently known bug fix is committed and we see where we stand. * I also do not know if Greg has successfully retooled his test box to run -stable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 991BF37BB24 for ; Wed, 5 Apr 2000 11:44:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA79634; Wed, 5 Apr 2000 11:43:52 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 11:43:52 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051843.LAA79634@apollo.backplane.com> To: Brad Knowles Cc: Mathew Kanner , current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Also, as a general note to everyone, make sure you are building vinum :> into the kernel directly and not using it as a kld, just to ensure that :> it stays in sync with the kernel. : : Isn't this in direct conflict with the instructions given for :normally using vinum? Is this a temporary change, until we get over :some of the current problems, or is this a more permanent change? : : Out of curiosity, is this your recommendation, or does Greg agree with it? This is my personal recommendation - if you are messing around with something that is under development or test, it is best to build it into the kernel to avoid getting out of sync without knowing it. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:45:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 865FA37BD59 for ; Wed, 5 Apr 2000 11:45:54 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel1.hp.com (Postfix) with ESMTP id F2A9AACC; Wed, 5 Apr 2000 11:45:53 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0.1) id LAA09704; Wed, 5 Apr 2000 11:45:53 -0700 (PDT) Message-ID: <38EB89E1.BD89BA7@cup.hp.com> Date: Wed, 05 Apr 2000 11:45:53 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installworld to /some/where/... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Is it possible to do an installworld not to / of existing system, but to, > say, subdirs somewhere, which could be mountpoints for another disk? Yes. Do something like: make installworld DESTDIR=/where/ever/you/want/it/installed HTH, -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:53:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 6228037B533 for ; Wed, 5 Apr 2000 11:53:22 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id B9748DD54; Wed, 5 Apr 2000 20:52:02 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <200004051843.LAA79634@apollo.backplane.com> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> <200004051843.LAA79634@apollo.backplane.com> Date: Wed, 5 Apr 2000 20:51:20 +0200 To: Matthew Dillon From: Brad Knowles Subject: Re: Vinum breakage Cc: Mathew Kanner , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:43 AM -0700 2000/4/5, Matthew Dillon wrote: > This is my personal recommendation - if you are messing around with > something that is under development or test, it is best to build it > into the kernel to avoid getting out of sync without knowing it. Ahh, okay. Sounds logical to me. Thanks again! -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 11:56:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E701E37B953 for ; Wed, 5 Apr 2000 11:56:43 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e35JLq508491; Wed, 5 Apr 2000 12:21:52 -0700 (PDT) Date: Wed, 5 Apr 2000 12:21:52 -0700 From: Alfred Perlstein To: Matthew Dillon Cc: Brad Knowles , Mathew Kanner , current@FreeBSD.ORG Subject: Re: Vinum breakage Message-ID: <20000405122151.A8349@fw.wintelcom.net> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> <200004051843.LAA79634@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004051843.LAA79634@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Apr 05, 2000 at 11:43:52AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000405 12:12] wrote: > > : > :> Also, as a general note to everyone, make sure you are building vinum > :> into the kernel directly and not using it as a kld, just to ensure that > :> it stays in sync with the kernel. > : > : Isn't this in direct conflict with the instructions given for > :normally using vinum? Is this a temporary change, until we get over > :some of the current problems, or is this a more permanent change? > : > : Out of curiosity, is this your recommendation, or does Greg agree with it? > > > This is my personal recommendation - if you are messing around with > something that is under development or test, it is best to build it > into the kernel to avoid getting out of sync without knowing it. Last I checked, doing so is dangerous because by default the userland components of vinum have debugging on which is incompatible with a kernel running vinum without debug (the default when linked in). So you must also relink your vinum utilities without debug and install them or you won't be able to use vinum. I hope to work with Greg soon to resolve this, if it hasn't already been fixed. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 12:28:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id DA5E437B9FA for ; Wed, 5 Apr 2000 12:28:36 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id 73B211F209; Wed, 5 Apr 2000 21:11:18 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000405122151.A8349@fw.wintelcom.net> References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> <200004051843.LAA79634@apollo.backplane.com> <20000405122151.A8349@fw.wintelcom.net> Date: Wed, 5 Apr 2000 21:10:46 +0200 To: Alfred Perlstein , Matthew Dillon From: Brad Knowles Subject: Re: Vinum breakage Cc: Mathew Kanner , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:21 PM -0700 2000/4/5, Alfred Perlstein wrote: > Last I checked, doing so is dangerous because by default the userland > components of vinum have debugging on which is incompatible with > a kernel running vinum without debug (the default when linked in). Correct, I believe that this is still an issue. > So you must also relink your vinum utilities without debug and install > them or you won't be able to use vinum. IMO, it would be better to make the changes so that the kernel components of vinum are built with debugging turned on, so that they are compatible with the userland components. For someone that is working with vinum in this period of time, and contemplating using it as a built-in part of the kernel, I do not believe that this would be too hard. Of course, I would not do this on a normal basis, just during the current difficulties while certain bugs are tracked down and fixed. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 13:38:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 1AEFA37B748 for ; Wed, 5 Apr 2000 13:38:45 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 24858 invoked from network); 5 Apr 2000 20:31:56 -0000 Received: from acs-63-90-88-25.zbzoom.net (HELO cvzoom.net) (63.90.88.25) by ns.cvzoom.net with SMTP; 5 Apr 2000 20:31:56 -0000 Message-ID: <38EBA2A1.AD3D477E@cvzoom.net> Date: Wed, 05 Apr 2000 16:31:29 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Recent pcm commits Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The pcm driver has been much more stable than before. Congrats. But, one note: I think that in /sys/dev/sound/isa/ess.c, on line 41, the buffer size should be bumped down to 12288. Before, it was set to 16k, and my ESS 1868 would not work properly. Also, there's some new problems that have cropped up with RealPlayer 5.0. (I know, we should pretty much be using RealPlayer 7.0.) When I try to play an audio clip with Rvplayer 5, I get an audio write error: xxx bytes, and the clip aborts. But, RealPlayer 7.0 works flawlessly, and the pcm driver has been working better than in the past couple of days. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 13:49:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1F2A937BEF6 for ; Wed, 5 Apr 2000 13:49:09 -0700 (PDT) (envelope-from jeremyp@pc0640.alcatel.com.au) Received: by border.alcanet.com.au id <115226>; Thu, 6 Apr 2000 06:49:25 +1000 From: Peter Jeremy Subject: Re: Using packed structs to gain cheap SMP primatives In-reply-to: <20000329221042.Y21029@fw.wintelcom.net>; from bright@wintelcom.net on Fri, Mar 31, 2000 at 12:50:51AM +1000 To: Alfred Perlstein Cc: current@FreeBSD.ORG Message-Id: <00Apr6.064925est.115226@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003300530.XAA40214@prism.flugsvamp.com> <20000329221042.Y21029@fw.wintelcom.net> Date: Thu, 6 Apr 2000 06:49:23 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 31, 2000 at 12:50:51AM +1000, Alfred Perlstein wrote: >What I'm calling for is a vote if we'll rely on this type of behavior >(32 bit stores being atomic with respect to readers) or not, or >perhaps to rely on it but mark it somehow so people can "fix it" >if the need arises later by using other locking primatives on what >should be atomic updates. I can't imagine any implementation with an N-bit bus where N-bit aligned transfers were not atomic WRT other N-bit aligned transfers. It may not be (and probably isn't) guaranteed for non-aligned transfers, or for smaller bus sizes (anyone for a 386SX SMP box?). Larger bus sizes are also problematical - they may require some form of RMW sequence to update an object smaller than the bus. If more than one writer is allowed to the bus-word containing the object, some form of locking will probably be necessary anyway (the Alpha, and presumably the IA64, special-case 32-bit R/W, but future architectures may not). Since we started talking about packed structs, it's worth remembering that struct { short foo[2];} will only require short alignment and therefore may not wind up with 32-bit alignment. IMHO, we can't rely on 32-bit stores being atomic in the future, but there will be some size where this will be true. This suggests that the objects or object accesses should be marked somehow. (Of course, since this size will be the `most efficient' size for that architecture, it should be C's `int' type). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 13:49:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 29F9637BD59 for ; Wed, 5 Apr 2000 13:49:17 -0700 (PDT) (envelope-from jeremyp@pc0640.alcatel.com.au) Received: by border.alcanet.com.au id <115212>; Thu, 6 Apr 2000 06:49:23 +1000 From: Peter Jeremy Subject: Re: Kernel trace question (kernel doesn't compile _without_ -O) In-reply-to: <14560.64806.608659.960815@trooper.velocet.net>; from dgilbert@velocet.ca on Wed, Mar 29, 2000 at 04:44:08AM +1000 To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Apr6.064923est.115212@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <14560.64806.608659.960815@trooper.velocet.net> Date: Thu, 6 Apr 2000 06:49:22 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 29, 2000 at 04:44:08AM +1000, David Gilbert wrote: >Also... I have noticed that several modules don't want to compile in >the kernel without -O, including kern_synch.c (undefined reference to >__cursig) and atomic.c (inconsistent operand constraints in an `asm'). I am aware of problems with atomic.c, but haven't had the time to fix it properly. My original problem was trying to make the code work in both 3.x and 4.x since gcc 2.7.x and egcs/gcc 2.9.x have imcompatible constraint requirements. I suspect the current approach (inline functions) may not be optimal, but haven't spent enough time experimenting to be certain. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 13:52: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 96CF037BF11 for ; Wed, 5 Apr 2000 13:51:56 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1830 invoked from network); 5 Apr 2000 20:51:45 -0000 Received: from acs-63-90-88-25.zbzoom.net (HELO cvzoom.net) (63.90.88.25) by ns.cvzoom.net with SMTP; 5 Apr 2000 20:51:45 -0000 Message-ID: <38EBA73D.B6FDE729@cvzoom.net> Date: Wed, 05 Apr 2000 16:51:09 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Recent pcm commits References: <200004052043.NAA02737@papermill.wrs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [note: followups directed to -current] David Holloway wrote: > > What is the exact error message when using rvplayer 5? Here it is: General error. An error occurred. For more information, please see Error 1 at: http://www.realaudio.com/help/error After I press OK, I get this: ****audio: write error: 724 bytes errno: 0 ****audio: write error: 724 bytes errno: 0 Here'a a snippet of my dmesg. unknown0: at port 0x800-0x807 on isa0 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 unknown1: at port 0x201 on isa0 - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 15: 7: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8FB9F37B916 for ; Wed, 5 Apr 2000 15:06:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA80643; Wed, 5 Apr 2000 15:06:50 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 15:06:50 -0700 (PDT) From: Matthew Dillon Message-Id: <200004052206.PAA80643@apollo.backplane.com> To: Brad Knowles Cc: Alfred Perlstein , Mathew Kanner , current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> <200004051649.JAA78992@apollo.backplane.com> <200004051843.LAA79634@apollo.backplane.com> <20000405122151.A8349@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 12:21 PM -0700 2000/4/5, Alfred Perlstein wrote: : :> Last I checked, doing so is dangerous because by default the userland :> components of vinum have debugging on which is incompatible with :> a kernel running vinum without debug (the default when linked in). : : Correct, I believe that this is still an issue. Yes, but it does warn you about it if there is a mismatch, and I still think it's much safer (and will reduce bogus bug reports, not that the recent bug reports have been bogus :-)) to build vinum into the kernel with all the flak flying around. I agree re: fixing the debugging support, but I don't think that should be a priority. The priority should be to make vinum as reliable as possible considering the number of people who are using it or will be using it. Despite the problems, vinum is well on its way to becoming a defacto standard for FreeBSD systems and for that reason any perceived problem with vinum will become a problem with 'FreeBSD', just like problems with NFS were attributed as being problems with FreeBSD in past years (reviews, performance tests, etc.). One of the main reasons FreeBSD has a better reputation for reliably then Linux, for example, is due to our focus on testing whole (fully integrated) systems over Linux's piecemeal approach. Vinum is now a defacto part of that integration. -Matt Matthew Dillon : : Of course, I would not do this on a normal basis, just during the :current difficulties while certain bugs are tracked down and fixed. : :-- : These are my opinions -- not to be taken as official Skynet policy :====================================================================== :Brad Knowles, || Belgacom Skynet SA/NV To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 15:26:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by hub.freebsd.org (Postfix) with ESMTP id A5E8337BF2F for ; Wed, 5 Apr 2000 15:26:29 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (minbar-1-15.mdm.mke.execpc.com [169.207.135.15]) by mailgw02.execpc.com (8.9.1) id RAA20759; Wed, 5 Apr 2000 17:26:00 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id ADBDF173; Wed, 5 Apr 2000 17:28:18 -0500 (CDT) X-Mailer: exmh version 2.1.1 10/16/1999 To: Maxim Sobolev Cc: Frank Nobis , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) In-reply-to: Your message of "Wed, 05 Apr 2000 16:27:17 +0300." <38EB3F35.EF0E287A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Apr 2000 17:28:18 -0500 From: Jon Hamilton Message-Id: <20000405222818.ADBDF173@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38EB3F35.EF0E287A@altavista.net>, Maxim Sobolev wrote: } Frank Nobis wrote: } } > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: } > > } > > up clean. I think you have a hardware problem somewhere :( } > } > That is very likely a hardwre problem. I have a nfs server under 3.4-S } > here running, It was easy to crash the system with much I/O over nfs } > on a 100M Ethernet connection. (I did a dump and the machine paniced) } > } > The same over a slower 10M ethernet, but it took longer to crash. } > } > Now I replaced a very old adaptec 1542cf with a 2940U. I did the same } > stress test, but got no more panics. Even a load of 80% interrupts } > didn't kill the machine. } > } > Maybe you have a similar problem. } } It is unlikely, because I've never seen this problem previously when 3.[01234 } ] } was installed on this hardware. Hardware does fail over time; just because it performed OK in the past doesn't mean that something hasn't gone bad since. I suppose it could be a problem with one of the drivers for your particular setup; is it feasable for you to try booting an older version (even from floppy) of FreeBSD and try the test again? -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 15:37:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 330B837B953 for ; Wed, 5 Apr 2000 15:37:42 -0700 (PDT) (envelope-from brameld@twave.net) Received: from [208.47.188.48] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id xa729115 for ; Wed, 5 Apr 2000 18:37:16 -0400 From: Walter Brameld To: J McKitrick , Nick Hibma Subject: Re: Parallel port zip drives - inventory of working and non-working systems Date: Wed, 5 Apr 2000 19:36:17 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: FreeBSD STABLE Mailing List , FreeBSD CURRENT Mailing List References: <20000405153914.A13658@dogma.freebsd-uk.eu.org> In-Reply-To: <20000405153914.A13658@dogma.freebsd-uk.eu.org> MIME-Version: 1.0 Message-Id: <00040519372802.01864@Bozo_3.BozoLand.domain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 05 Apr 2000, in a never-ending search for enlightenment, J McKitrick wrote: > Does anyone recall seeing or making a remark about a group of interrupts or > hardware port locations that could be causing this problem? I was searching > my email and i can't find it. > > Someone said 4.0 allocates a group of hardware locations (0x380-0x3f0?) > differently from 3.4, and that this may affect the parallel port allocation > on laptops. > > Has anyone had this zip timeout error on a desktop machine and not been > able to fix it? My problem was it stopped working when I went to 4.0. When I changed my BIOS setting the parallel port to EPP, it started working again. -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter: And what does THIS button do?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 15:40:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from enigma.whacky.net (enigma.whacky.net [194.109.204.120]) by hub.freebsd.org (Postfix) with ESMTP id 7161537B6A3 for ; Wed, 5 Apr 2000 15:40:29 -0700 (PDT) (envelope-from stephanb@enigma.whacky.net) Received: (from stephanb@localhost) by enigma.whacky.net (8.9.3/8.9.3) id AAA90141 for current@freebsd.org; Thu, 6 Apr 2000 00:40:21 +0200 (CEST) (envelope-from stephanb) Date: Thu, 6 Apr 2000 00:00:53 +0200 From: Stephan van Beerschoten To: current@freebsd.org Subject: dev/vx/if_vx_pci.c 5.0-CURRENT Message-ID: <20000406004011.A89888@enigma.whacky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe there are some people with the same problem .. or maybe someone who knows what this could be and how this problem sneaked into the system. I'm cunning -CURRENT for ages but since March 19 I am unable to compile myself a new kernel. I'm cunning 5.0-CURRENT but somehow I don't think that matters this time since the modification timestamp for the the vx devicedriver is Sat Jan 29 14:50:32 2000 (cvs timestamp that is). Its about the following ethernetcard: (info from dmesg of running kernel) vx0: <3COM 3C590 Etherlink III PCI> port 0xec00-0xec1f irq 11 at device 17.0 on pci0 With a nicely updated cvs sourctree it fails on me when I run make. I get the following warnings and the final error: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -n -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/vx/if_vx_pci.c ../../dev/vx/if_vx_pci.c:131: variable `vxdevice' has initializer but incomplete type ../../dev/vx/if_vx_pci.c:132: warning: excess elements in struct initializer ../../dev/vx/if_vx_pci.c:132: warning: (near initialization for `vxdevice') ../../dev/vx/if_vx_pci.c:133: warning: excess elements in struct initializer ../../dev/vx/if_vx_pci.c:133: warning: (near initialization for `vxdevice') ../../dev/vx/if_vx_pci.c:134: warning: excess elements in struct initializer ../../dev/vx/if_vx_pci.c:134: warning: (near initialization for `vxdevice') ../../dev/vx/if_vx_pci.c:135: warning: excess elements in struct initializer ../../dev/vx/if_vx_pci.c:135: warning: (near initialization for `vxdevice') ../../dev/vx/if_vx_pci.c:137: warning: excess elements in struct initializer ../../dev/vx/if_vx_pci.c:137: warning: (near initialization for `vxdevice') ../../dev/vx/if_vx_pci.c:139: warning: type defaults to `int' in declaration of `COMPAT_PCI_DRIVER' ../../dev/vx/if_vx_pci.c:139: warning: parameter names (without types) in function declaration ../../dev/vx/if_vx_pci.c:139: warning: data definition has no type or storage class ../../dev/vx/if_vx_pci.c:131: warning: `vxdevice' defined but not used *** Error code 1 This is the relevant piece of my config file: (the xl device does work btw) # PCI Ethernet NICs. device vx # 3Com 3c590, 3c595 (``Vortex'') device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') My world is current as of yesterday.. Anyone? I hate to post to -current *grin* but I have found absolutely nothing in my mailarchives and on the webarchive. Here are some final details about my system: FreeBSD tripwire.whacky.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Mar 19 19:13:00 CET 2000 stephanb@tripwire.whacky.net:/mnt/archive/CVS/5.0-CURRENT/src/sys/compile/TRIPWIRE i386 CPU: Pentium II/Pentium II Xeon/Celeron (412.37-MHz 686-class CPU) real memory = 268369920 (262080K bytes) pci1: xl0: <3Com 3c905C-TX Fast Etherlink XL> ahc0: vx0: <3COM 3C590 Etherlink III PCI> sbc0: da0: Fixed Direct Access SCSI-3 device da1: Fixed Direct Access SCSI-2 device cd0: Removable CD-ROM SCSI-2 device cd1: Removable CD-ROM SCSI-2 device -Steve -- Stephan van Beerschoten stephanb@whacky.net PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 In god we trust.. all others we verify with PGP fingerprints To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 15:49:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id E76D637BA46 for ; Wed, 5 Apr 2000 15:49:54 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id PAA16963; Wed, 5 Apr 2000 15:49:41 -0700 (PDT) Date: Wed, 5 Apr 2000 15:49:40 -0700 From: Brooks Davis To: Stephan van Beerschoten Cc: current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT Message-ID: <20000405154940.A14513@orion.ac.hmc.edu> References: <20000406004011.A89888@enigma.whacky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000406004011.A89888@enigma.whacky.net>; from stephanb@whacky.net on Thu, Apr 06, 2000 at 12:00:53AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 06, 2000 at 12:00:53AM +0200, Stephan van Beerschoten wrote: > Maybe there are some people with the same problem .. or maybe someone > who knows what this could be and how this problem sneaked into the system. > I'm cunning -CURRENT for ages but since March 19 I am unable to compile > myself a new kernel. I'm cunning 5.0-CURRENT but somehow I don't think > that matters this time since the modification timestamp for the > the vx devicedriver is Sat Jan 29 14:50:32 2000 (cvs timestamp that is). > > Its about the following ethernetcard: (info from dmesg of running kernel) > vx0: <3COM 3C590 Etherlink III PCI> port 0xec00-0xec1f irq 11 at device 17.0 on pci0 > > With a nicely updated cvs sourctree it fails on me when I run make. I get > the following warnings and the final error: See /usr/src/UPDATING entry dated 20000319. It looks like you are missing the required "option COMPAT_OLDPCI". The PCI portion of the vx driver needs to be converted to newbus. It looks pretty straight forward if you're feeling a moderatly ambitious. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 16:36:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id C9CBE37BE11 for ; Wed, 5 Apr 2000 16:36:31 -0700 (PDT) (envelope-from kent@chapel-hill.tfd.com) Received: from chapel-hill.tfd.com (chapel-hill.tfd.com [10.20.0.40]) by rtp.tfd.com (8.9.3/8.9.3) with ESMTP id TAA12454 for ; Wed, 5 Apr 2000 19:37:01 -0400 (EDT) Received: (from kent@localhost) by chapel-hill.tfd.com (8.9.3/8.9.3) id TAA00273 for current@freebsd.org; Wed, 5 Apr 2000 19:35:07 -0400 (EDT) (envelope-from kent) Date: Wed, 5 Apr 2000 19:35:07 -0400 (EDT) From: Kent Hauser Message-Id: <200004052335.TAA00273@chapel-hill.tfd.com> To: current@freebsd.org Subject: pcm & SoundBlaster Live! PCI card Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I can't for the life of me get my new gateway computer to make any noise (at least with FreeBSD). I've tried all the PNP/nonPNP combinations from LINT (and then some). The card is a "Creative Labs Soundblaster Live!" PCI card. The gateway blurb is found on: http://www.gateway.com/mes/default.asp?page=soundcards The sound config lines & dmesg output are attached. Any pointers would be greatly appreciated. Thanks a bunch. Kent ========= options PNPBIOS device pcm device sbc device csa device pca0 at isa? port IO_TIMER1 ========= Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Wed Apr 5 19:14:25 EDT 2000 kent@chapel-hill.tfd.com:/usr/src/sys/compile/GW Calibrating clock(s) ... TSC clock: 696358058 Hz, i8254 clock: 1193099 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Pentium III Xeon (696.41-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) 0x00462000 - 0x040fcfff, 63549440 bytes (15515 pages) 0x04100000 - 0x07ff7fff, 66027520 bytes (16120 pages) avail memory = 126103552 (123148K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6a90 bios32: Entry = 0xfd780 (c00fd780) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f6ae0 pnpbios: Entry = f0000:9e33 Rev = 1.0 Other BIOS signatures found: ACPI: 000f6ac0 Preloaded elf kernel "kernel" at 0xc0449000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f8000000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00001400, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 000010c0, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00007000, size 4, enabled found-> vendor=0x14f1, dev=0x1036, revid=0x08 class=07-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base f4000000, size 16, enabled map[14]: type 1, range 32, base 00001410, size 3, enabled found-> vendor=0x1102, dev=0x0002, revid=0x07 class=04-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 000010e0, size 5, enabled found-> vendor=0x1102, dev=0x7002, revid=0x07 class=09-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 3, range 32, base 00001418, size 3, enabled found-> vendor=0x105a, dev=0x4d38, revid=0x01 class=01-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00001430, size 3, enabled map[14]: type 1, range 32, base 00001424, size 2, enabled map[18]: type 3, range 32, base 00001428, size 3, enabled map[1c]: type 1, range 32, base 00001420, size 2, enabled map[20]: type 1, range 32, base 00001080, size 6, enabled map[24]: type 1, range 32, base f4020000, size 17, enabled found-> vendor=0x10b7, dev=0x9006, revid=0x04 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base 00001000, size 7, enabled map[14]: type 1, range 32, base f4010000, size 7, enabled found-> vendor=0x12b9, dev=0x1008, revid=0x01 class=07-00-02, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=5 map[10]: type 3, range 32, base 00001438, size 3, enabled pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10de, dev=0x0028, revid=0x15 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f5000000, size 24, enabled map[14]: type 1, range 32, base fc000000, size 25, enabled pci1: on pcib1 pci1: (vendor=0x10de, dev=0x0028) at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1400-0x140f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1400 ata0: mask=00 status0=ff status1=ff ata0: probe allocation failed ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1408 ata1: mask=03 status0=50 status1=50 ata1: mask=03 status0=00 status1=10 ata1: devices = 0xc ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x7112) at 7.2 irq 9 chip1: port 0x7000-0x700f at device 7.3 on pci0 pci0: (vendor=0x14f1, dev=0x1036) at 13.0 irq 5 pci0: (vendor=0x1102, dev=0x0002) at 14.0 irq 11 pci0: (vendor=0x1102, dev=0x7002) at 14.1 atapci1: port 0x1080-0x10bf,0x1420-0x1423,0x1428-0x142f,0x1424-0x1427,0x1430-0x1437 mem 0xf4020000-0xf403ffff irq 10 at device 15.0 on pci0 ata-: ata2 exists, using next available unit number ata2: iobase=0x1430 altiobase=0x1424 bmaddr=0x1080 ata2: mask=03 status0=50 status1=00 ata2: mask=03 status0=50 status1=00 ata2: devices = 0x1 ata2: at 0x1430 on atapci1 ata3: iobase=0x1428 altiobase=0x1420 bmaddr=0x1088 ata3: mask=03 status0=00 status1=00 ata3: mask=03 status0=00 status1=00 ata3: devices = 0x0 ata3: probe allocation failed xl0: <3Com 3c900B-TPC Etherlink XL> port 0x1000-0x107f mem 0xf4010000-0xf401007f irq 9 at device 16.0 on pci0 xl0: Ethernet address: 00:50:da:17:a0:3a xl0: media options word: 18 xl0: guessing TPC (BNC/TP) xl0: found 10baseT xl0: found BNC xl0: selecting 10baseT transceiver, half duplex xl0: supplying EUI64: 00:50:da:ff:fe:17:a0:3a bpf: xl0 attached sio0: irq maps: 0x3 0x23 0x3 0x3 sio0: <3COM PCI FaxModem> port 0x1438-0x143f irq 5 at device 17.0 on pci0 sio0: moving to sio4 sio4: type 16550A pnpbios: 17 devices, largest 317 bytes PNP0c02: adding io range 0x370-0x371, size=0x2, align=0x1 PNP0c02: adding io range 0xea-0xeb, size=0x2, align=0x1 PNP0c02: adding fixed memory32 range 0xfffc0000-0xffffffff, size=0x40000 PNP0c02: end config pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xe4000-0xfffff, size=0x1c000 PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding fixed memory32 range 0xfff80000-0xfffbffff, size=0x40000 PNP0c01: end config pnpbios: handle 1 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: end config pnpbios: handle 2 device ID PNP0200 (0002d041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 00x4 PNP0000: end config pnpbios: handle 3 device ID PNP0000 (0000d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 00x1 PNP0100: end config pnpbios: handle 4 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 PNP0b00: end config pnpbios: handle 5 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 00x2 PNP0303: end config pnpbios: handle 6 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 PNP0c04: end config pnpbios: handle 7 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 8 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: end config pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0x8000-0x803f, size=0x40, align=0x1 PNP0c02: adding io range 0x7000-0x700f, size=0x10, align=0x1 PNP0c02: end config pnpbios: handle 10 device ID PNP0c02 (020cd041) PNP0c02: adding fixed memory32 range 0xcb000-0xcbfff, size=0x1000 PNP0c02: end config pnpbios: handle 12 device ID PNP0c02 (020cd041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 13 device ID PNP0f13 (130fd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 PNP0501: end config pnpbios: handle 14 device ID PNP0501 (0105d041) PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: adding irq mask 00x8 PNP0501: end config pnpbios: handle 15 device ID PNP0501 (0105d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 17 device ID PNP0700 (0007d041) PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0401: adding io range 0x778-0x77f, size=0x8, align=0x8 PNP0401: adding irq mask 0x80 PNP0401: adding dma mask 0x8 PNP0401: end config pnpbios: handle 20 device ID PNP0401 (0104d041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number ex_isa_identify() isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata4: mask=00 status0=ff status1=ff ata4: probe allocation failed bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x330 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x334 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x230 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x234 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x130 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x134 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 06 00 psm: data 08 01 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 30 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached isa_compat: didn't get irq for le pca0 at port 0x40 on isa0 isa_probe_children: probing PnP devices unknown0: at port 0x370-0x371,0xea-0xeb iomem 0xfffc0000-0xffffffff on isa0 unknown1: at iomem 0-0x9ffff,0xe4000-0xfffff,0x100000-0x7ffffff,0xfff80000-0xfffbffff on isa0 unknown2: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown3: at port 0x40-0x43 irq 0 on isa0 unknown4: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown5: at port 0xf0-0xff irq 13 on isa0 pca1: at port 0x61 on isa0 unknown6: at port 0xcf8-0xcff on isa0 unknown7: at port 0x4d0-0x4d1,0x8000-0x803f,0x7000-0x700f on isa0 unknown8: at iomem 0xcb000-0xcbfff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. new masks: bio 40088440, tty 400310ba, net 400712ba bpf: sl0 attached bpf: ppp0 attached new masks: bio 40088440, tty 400310ba, net 400712ba bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached IPsec: Initialized Security Association Processing. ata2-master: success setting up UDMA4 mode on Promise chip ad4: ATA-4 disk at ata2 as master ad4: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S ad4: 16 secs/int, 32 depth queue, UDMA66 ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 Creating DISK ad4 Creating DISK wd4 ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: DVD-ROM drive at ata1 as master acd0: read 2750KB/s (6875KB/s), 512KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-slave: success setting up PIO4 mode on generic chip acd1: CD-RW drive at ata1 as slave acd1: read 4134KB/s (4134KB/s) write 689KB/s (689KB/s), 2048KB buffer, PIO4 acd1: Reads: CD-R, CD-RW, CD-DA stream, packet acd1: Writes: CD-R, CD-RW, test write acd1: Audio: play, 2 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/ad4s2a ad4s1: type 0xb, start 63, end = 16048934, size 16048872 : OK ad4s2: type 0xa5, start 16048935, end = 53464319, size 37415385 : OK start_init: trying /sbin/init xl0: starting DAD for fe80:0001::0250:daff:fe17:a03a bpf: tun0 attached xl0: DAD complete for fe80:0001::0250:daff:fe17:a03a - no duplicates found Linux-ELF exec handler installed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 17:10:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 5E43237BABE; Wed, 5 Apr 2000 17:09:59 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA72917; Thu, 6 Apr 2000 09:39:49 +0930 (CST) Date: Thu, 6 Apr 2000 09:39:49 +0930 From: Greg Lehey To: Matthew Dillon Cc: "Jonathan M. Bresler" , brdean@unx.sas.com, phk@critter.freebsd.dk, blk@skynet.be, asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: Vinum breakage Summary (was Re: Vinum breakage) Message-ID: <20000406093949.M66569@freebie.lemis.com> References: <20000405170350.103FC37BBA8@hub.freebsd.org> <200004051842.LAA79600@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004051842.LAA79600@apollo.backplane.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 5 April 2000 at 11:42:40 -0700, Matthew Dillon wrote: >> Matt, >> help me understand your patch. this is how i read it at this >> time: >> >> >> Matt has just made available an early patch that corrects the vinum >> panic. is this the same vinum panic that people are claiming phk >> created with the bio/buf changes? i dont know the vinum code. i dont >> know the bio/buf code. i do see that all the code changes are to >> vinum source files. none of the changes reference the buf/bio parts >> for the kernel. >> >> the patch is against 4.0, code unaffected by phk's changes. >> the revision levels are those indicated in Matt's patch and those I >> recevied via CVSup last night. > > There is a lot of confusion here, which I will straighten out: > > * 3/20 - phk makes his first buffer cache commit, adding b_iocmd. > This breaks vinum, but it takes a while for people to realize it. > (see 1.46 sys/dev/vinum/vinumrequest.c and other files) > > This commit is made into -current. -stable is not effected > > * 3/26 - alfred fixes phk's type-o that broke vinum (1.47 vinumrequest.c, > and other files). (3/26 == last week). As far as I can tell, this is correct. I still haven't finished checking the changes, and there's a possibility that some lesser-used functions are still broken, though I have no direct evidence for that beyond the fact they haven't been tested. > * During the last week, at aroudn the same time, a panic was traced > definitively to vinum. On saturday it was traced to the raid5 code. > > Some of the people using vinum, including Greg, are using it under > -current. In fact, in view of what we've seen, this affects all recent versions of Vinum, but the problem only shows up with RAID-5 and IDE. > * Phk begins making more radical commits (to -current) on sunday. > > * Confusion reigns. I don't think the later commits broke vinum again, > but at this point there were a number of people focused on vinum and > having the buffer cache ripped out from under them might have resulted > in false positives due to people using vinum as a kld rather then > building it into the kernel. I believe there was a message or two > in this regard that turned out to be a false positive. The only issue I see is that it required additional work to get everything in sync. It was nuisance value more than anything. > * Greg's test machine was running -current. Greg is dead in the water > at this point (i.e. he would need to retool to -stable), and > complains mightily (and appropriately, I believe). Well, I'm not "dead in the water", but I don't see any reason to build a -STABLE machine at this point, since I can't reproduce the problem on either. > Despites the truth that it would be better to track the vinum bug down > in -stable, the fact remains that many people are using -current. I don't agree that it's better to track it in -STABLE. I'm pretty sure that the bug is unchanged in both releases. > * I spend five or six hours settings vinum up on my -stable test box to > try to reproduce and fix the panic on monday. > > * I come up with a patch, which Greg is now reviewing & using as a > basis for the 'real' fix. This patch fixes a bug in vinum -- we > knew there was one (on saturday, see above). The only known bug > introduced by phk's commit (so far) was fixed by Alfred on 3/26. > > This panic is not related to phk's commits. > > My patch is relative to 4.0. In fact, the relevant parts are also unchanged in -CURRENT. I'm going to commit what I consider to be the core of the fix right now. I'm still analysing the rest. > * It is currently unknown whether further breakage in -current exists > due to phk's changes. I don't think we'll know whether there are > further problems until the currently known bug fix is committed and > we see where we stand. Agreed, though I consider it unlikely. phk's last lot of commits just meant a lot of extra work when I could least use it. > * I also do not know if Greg has successfully retooled his test > box to run -stable. Not yet. I'll fix the problem in -CURRENT first. Once I have confirmation from sos that the patch fixes his problems, I'll commit to -STABLE. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 17:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id C14E137B6CB for ; Wed, 5 Apr 2000 17:44:17 -0700 (PDT) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id UAA01770; Wed, 5 Apr 2000 20:43:30 -0400 (EDT) (envelope-from efutch@nyct.net) Date: Wed, 5 Apr 2000 20:43:30 -0400 (EDT) From: "Eric D. Futch" To: Brooks Davis Cc: Stephan van Beerschoten , current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT In-Reply-To: <20000405154940.A14513@orion.ac.hmc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok.. I figured I'd take this on on my way to getting more comfy with FreeBSD. Check out my patch and let me know how far I've gone off the deep end :) http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch Unfortunately I do not have the acutal card to test this patch. It did survive a buildkernel, so I'm just assuming that I'm not that far off. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Wed, 5 Apr 2000, Brooks Davis wrote: >See /usr/src/UPDATING entry dated 20000319. It looks like you are >missing the required "option COMPAT_OLDPCI". The PCI portion of the vx >driver needs to be converted to newbus. It looks pretty straight >forward if you're feeling a moderatly ambitious. > >-- Brooks > >-- >Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 18: 9:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 5076D37B712 for ; Wed, 5 Apr 2000 18:09:17 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id SAA08515; Wed, 5 Apr 2000 18:09:09 -0700 (PDT) Date: Wed, 5 Apr 2000 18:09:09 -0700 From: Brooks Davis To: "Eric D. Futch" Cc: Brooks Davis , Stephan van Beerschoten , current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT Message-ID: <20000405180909.A2921@orion.ac.hmc.edu> References: <20000405154940.A14513@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from efutch@nyct.net on Wed, Apr 05, 2000 at 08:43:30PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote: > Ok.. I figured I'd take this on on my way to getting more comfy with > FreeBSD. Check out my patch and let me know how far I've gone off the > deep end :) > > http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch > > Unfortunately I do not have the acutal card to test this patch. It did > survive a buildkernel, so I'm just assuming that I'm not that far off. I think if you install the kernel and reboot it will likely explode in probe. It takes more then just new structs. The function signatures have changed as well. Take a look at rev 1.67 of src/sys/pci/if_fxp.c to see what newbus conversion takes. I'm taking a wack at a rewrite, but like you I don't have a card, so testing will be kinda trickey. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 18:29:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 039CB37B7C5 for ; Wed, 5 Apr 2000 18:29:33 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id SAA15648; Wed, 5 Apr 2000 18:29:27 -0700 (PDT) Date: Wed, 5 Apr 2000 18:29:27 -0700 From: Brooks Davis To: "Eric D. Futch" Cc: Stephan van Beerschoten , current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT Message-ID: <20000405182927.A10848@orion.ac.hmc.edu> References: <20000405154940.A14513@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from efutch@nyct.net on Wed, Apr 05, 2000 at 08:43:30PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote: > Ok.. I figured I'd take this on on my way to getting more comfy with > FreeBSD. Check out my patch and let me know how far I've gone off the > deep end :) > > http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch > > Unfortunately I do not have the acutal card to test this patch. It did > survive a buildkernel, so I'm just assuming that I'm not that far off. Take a look at: http://www.one-eyed-alien.net/~brooks/FreeBSD/if_vx.diff It does a newbus coversion and makes the pci probe function look half way normal. It compiles without COMPAT_OLDPCI and the kernel boots so the probe function is probably ok. I'm less sure about the attach function. This one is modeled after the eisa attach function. Testing would be appreciated, but don't try this on a production system. ;-) This driver needs a lot more work. It has a very dated view of the world and should be updated. Maybe I'll pick up one of these cards on Ebay and take a shot at it. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 18:35:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id EB7AD37BB63 for ; Wed, 5 Apr 2000 18:35:33 -0700 (PDT) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id VAA09525; Wed, 5 Apr 2000 21:35:31 -0400 (EDT) (envelope-from efutch@nyct.net) Date: Wed, 5 Apr 2000 21:35:31 -0400 (EDT) From: "Eric D. Futch" To: Brooks Davis Cc: current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT In-Reply-To: <20000405180909.A2921@orion.ac.hmc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I figured it would take more work than I put into it. It was just a shot in the dark. I think I have one of these cars in my Linux box at home which I wouldn't mind ripping out and sticking in this machine. Let me know if it's still worth me poking around in, or if you're going ahead with the rewrite. I'm gonna keep playing with it out of my own interest on newbusifying things. Maybe once I get a bigger clue of what has to be done, I'll see about newbusifying other things. I always have all this extra time on my hands :) -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Wed, 5 Apr 2000, Brooks Davis wrote: >On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote: > >I think if you install the kernel and reboot it will likely explode in >probe. It takes more then just new structs. The function signatures >have changed as well. Take a look at rev 1.67 of src/sys/pci/if_fxp.c >to see what newbus conversion takes. I'm taking a wack at a rewrite, >but like you I don't have a card, so testing will be kinda trickey. > >-- Brooks > >-- >Any statement of the form "X is the one, true Y" is FALSE. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 18:45:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 9533237BE0F for ; Wed, 5 Apr 2000 18:45:06 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id SAA21352; Wed, 5 Apr 2000 18:45:01 -0700 (PDT) Date: Wed, 5 Apr 2000 18:45:00 -0700 From: Brooks Davis To: "Eric D. Futch" Cc: current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT Message-ID: <20000405184500.A17982@orion.ac.hmc.edu> References: <20000405180909.A2921@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from efutch@nyct.net on Wed, Apr 05, 2000 at 09:35:31PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 09:35:31PM -0400, Eric D. Futch wrote: > I figured it would take more work than I put into it. It was just a shot > in the dark. I think I have one of these cars in my Linux box at home > which I wouldn't mind ripping out and sticking in this machine. Let me > know if it's still worth me poking around in, or if you're going ahead > with the rewrite. I'm gonna keep playing with it out of my own > interest on newbusifying things. Maybe once I get a bigger clue of what > has to be done, I'll see about newbusifying other things. I always have > all this extra time on my hands :) I've posted a rewrite, but I can't test it. You might go ahead and take the card out of the Linux box and play around with it. There's plenty of other work to be done on this driver to make it fully modern beyond just a simple newbus conversion. The current static storage of softc's really should be replaced. A bus_space conversion would also be a good thing. Storing the resource pointers in the softc for removal in the detach function would probalby be a good thing. If you take a look at PR kern/17601 you'll find a patch I wrote to modernize the tx driver. In and of it self, it's probably too complicated to be very useful to learn from, but I mention four revisions of if_fxp which do individual parts of the conversion. Upgrading tx was a good six hourish exercise. I've got a much better understanding of probe and attach now. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 20:20:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from lotus2.lotus.com (lotus2.lotus.com [192.233.136.8]) by hub.freebsd.org (Postfix) with ESMTP id D9F0037B798 for ; Wed, 5 Apr 2000 20:20:18 -0700 (PDT) (envelope-from Yu_Guo@lotus.com) Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id XAA24755 for ; Wed, 5 Apr 2000 23:37:08 -0400 (EDT) Received: from a3mail.lotus.com (A3MAIL.lotus.com [9.95.5.66]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id XAA03211 for ; Wed, 5 Apr 2000 23:20:16 -0400 (EDT) Subject: Re: Installworld to /some/where/... To: "Andrzej Bialecki Cc: "freebsd-current" X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 From: "Yu Guo/PEK/Lotus" Date: Thu, 6 Apr 2000 11:31:16 +0800 Message-ID: X-MIMETrack: Serialize by Router on A3MAIL/CAM/H/Lotus(Release 5.0.3 |March 21, 2000) at 04/05/2000 11:21:50 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just do a make DESTDIR=/mnt/installdir installworld Thanks & Best Regards, Yu Guo Lotus Development, China PD Tel: +86-10-68025588 ext 603 Email: yu_guo@lotus.com Andrzej Bialecki To: freebsd-current@FreeBSD.ORG Sent by: cc: (bcc: Yu Guo/PEK/Lotus) owner-freebsd-current@F Subject: Installworld to /some/where/... reeBSD.ORG 00-04-06 02:25 AM Hi, Is it possible to do an installworld not to / of existing system, but to, say, subdirs somewhere, which could be mountpoints for another disk? Something like: /mnt/installdir/ /mnt/installdir/compat /mnt/installdir/etc /mnt/installdir/usr /mnt/installdir/var /mnt/installdir/ The reason I'm asking is that I'm looking for a method to easily clone/upgrade a bunch of servers without having to do 'make world' on all of them. I'm not satisfied either with using dd - the machines are not identical, there are some bits and pieces of config specific to each machine. So far the best method was to do a make world, but it becomes more and more a nuisance and waste of time... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 20:48: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 7E8B137B997 for ; Wed, 5 Apr 2000 20:48:03 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA69869; Wed, 5 Apr 2000 23:47:45 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Wed, 5 Apr 2000 23:47:45 -0400 (EDT) From: Chuck Robey To: Yu Guo/PEK/Lotus Cc: "Andrzej Bialecki , freebsd-current Subject: Re: Installworld to /some/where/... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Yu Guo/PEK/Lotus wrote: > > Just do a > make DESTDIR=/mnt/installdir installworld > Or remotely mount /usr/obj and /usr/src, and do 15 make installworlds on 15 machines. In fact, I'm not totally sure that first method works, because I think that perl, at least, records the name of DESTDIR during the 'make buildworld' so moving DESTDIR only in installworld, that might bomb later when you ran it. In fact, I think that will happen, and to cc1 (of gcc) also, because the 'specs' get set during buildworld, don't they? The above would only be safe, I think, if you did the make buildworld with the same DESTDIR. Anyone know if that's true? > > Hi, > > Is it possible to do an installworld not to / of existing system, but to, > say, subdirs somewhere, which could be mountpoints for another disk? > Something like: > > /mnt/installdir/ > /mnt/installdir/compat > /mnt/installdir/etc > /mnt/installdir/usr > /mnt/installdir/var > /mnt/installdir/ > > The reason I'm asking is that I'm looking for a method to easily > clone/upgrade a bunch of servers without having to do 'make world' on all > of them. I'm not satisfied either with using dd - the machines are not > identical, there are some bits and pieces of config specific to each > machine. So far the best method was to do a make world, but it becomes > more and more a nuisance and waste of time... > > > Andrzej Bialecki > > // WebGiro AB, Sweden (http://www.webgiro.com) > // ------------------------------------------------------------------- > // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- > // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 20:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 7833D37B7F0 for ; Wed, 5 Apr 2000 20:52:49 -0700 (PDT) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id MAA25087; Thu, 6 Apr 2000 12:52:44 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id MAA25261; Thu, 6 Apr 2000 12:52:43 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA22608; Thu, 6 Apr 2000 12:52:42 +0900 (JST) To: cpiazza@jaxon.net Cc: current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <20000402124742P.shin@nd.net.fujitsu.co.jp> References: <20000402075551N.shin@nd.net.fujitsu.co.jp> <20000401193005.A353@norn.ca.eu.org> <20000402124742P.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Thu_Apr__6_12:53:40_2000_518)--" Content-Transfer-Encoding: 7bit Message-Id: <20000406125344R.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Apr 2000 12:53:44 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 633 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Thu_Apr__6_12:53:40_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > > Sorry for the inconvenience and I'll try the fix. > > > > > > Sorry to be late, but I tried resolver fix and it seems to work. > > > This should remove such 75 seconds delay in apps which use > > > getaddrinfo(). > > > > > > Please review and try this patches. > > > > I applied it and am running with it now, but I can't say one way or another > > if it has fixed the problem :-). It only cropped up every couple of > > weeks and seemingly random at that. I'll assume it works if I don't see > > it happening again. > > > > Thanks, > > OK, anyway it is rather critical fix, so I think it needs some > testing period. I did a little bit cleanup, and made new patches. (with no behaviour change) I already received several positive confirmations for the patches. I'll wait more several days and will commit this if no significant problem is found for this. Thanks, Yoshinobu Inoue ----Next_Part(Thu_Apr__6_12:53:40_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="resolver.diff" Index: getaddrinfo.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/getaddrinfo.c,v retrieving revision 1.9 diff -u -r1.9 getaddrinfo.c --- getaddrinfo.c 2000/02/19 16:10:12 1.9 +++ getaddrinfo.c 2000/04/06 03:50:46 @@ -108,7 +108,6 @@ }; struct explore { - int e_af; int e_socktype; int e_protocol; const char *e_protostr; @@ -119,15 +118,10 @@ }; static const struct explore explore[] = { -#ifdef INET6 - { PF_INET6, SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, - { PF_INET6, SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, - { PF_INET6, SOCK_RAW, ANY, NULL, 0x05 }, -#endif - { PF_INET, SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, - { PF_INET, SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, - { PF_INET, SOCK_RAW, ANY, NULL, 0x05 }, - { -1, 0, 0, NULL, 0 }, + { SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, + { SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, + { SOCK_RAW, ANY, NULL, 0x05 }, + { 0, 0, NULL, 0 }, }; #ifdef INET6 @@ -136,7 +130,8 @@ #define PTON_MAX 4 #endif - +extern struct hostent * _getipnodebyname_multi __P((const char *name, + int af, int flags, int *errp)); static int str_isnumber __P((const char *)); static int explore_fqdn __P((const struct addrinfo *, const char *, const char *, struct addrinfo **)); @@ -307,9 +302,7 @@ if (pai->ai_socktype != ANY && pai->ai_protocol != ANY) { int matched = 0; - for (ex = explore; ex->e_af >= 0; ex++) { - if (pai->ai_family != ex->e_af) - continue; + for (ex = explore; ex->e_socktype; ex++) { if (ex->e_socktype == ANY) continue; if (ex->e_protocol == ANY) @@ -353,10 +346,12 @@ } /* NULL hostname, or numeric hostname */ - for (ex = explore; ex->e_af >= 0; ex++) { + for (afd = afdl; afd->a_af; afd++) + { + for (ex = explore; ex->e_socktype; ex++) { *pai = ai0; - if (!MATCH_FAMILY(pai->ai_family, ex->e_af, WILD_AF(ex))) + if (!MATCH_FAMILY(pai->ai_family, afd->a_af, WILD_AF(ex))) continue; if (!MATCH(pai->ai_socktype, ex->e_socktype, WILD_SOCKTYPE(ex))) continue; @@ -364,7 +359,7 @@ continue; if (pai->ai_family == PF_UNSPEC) - pai->ai_family = ex->e_af; + pai->ai_family = afd->a_af; if (pai->ai_socktype == ANY && ex->e_socktype != ANY) pai->ai_socktype = ex->e_socktype; if (pai->ai_protocol == ANY && ex->e_protocol != ANY) @@ -381,6 +376,7 @@ while (cur && cur->ai_next) cur = cur->ai_next; } + } /* * XXX @@ -394,27 +390,12 @@ ERR(EAI_NONAME); if (hostname == NULL) ERR(EAI_NONAME); - - /* - * hostname as alphabetical name. - * we would like to prefer AF_INET6 than AF_INET, so we'll make a - * outer loop by AFs. - */ - for (afd = afdl; afd->a_af; afd++) { - *pai = ai0; - if (!MATCH_FAMILY(pai->ai_family, afd->a_af, 1)) - continue; - - for (ex = explore; ex->e_af >= 0; ex++) { + /* hostname as alphabetical name. */ + { + for (ex = explore; ex->e_socktype; ex++) { *pai = ai0; - if (pai->ai_family == PF_UNSPEC) - pai->ai_family = afd->a_af; - - if (!MATCH_FAMILY(pai->ai_family, ex->e_af, - WILD_AF(ex))) - continue; if (!MATCH(pai->ai_socktype, ex->e_socktype, WILD_SOCKTYPE(ex))) { continue; @@ -424,8 +405,6 @@ continue; } - if (pai->ai_family == PF_UNSPEC) - pai->ai_family = ex->e_af; if (pai->ai_socktype == ANY && ex->e_socktype != ANY) pai->ai_socktype = ex->e_socktype; if (pai->ai_protocol == ANY && ex->e_protocol != ANY) @@ -485,12 +464,8 @@ if (get_portmatch(pai, servname) != 0) return 0; - afd = find_afd(pai->ai_family); - if (afd == NULL) - return 0; - - hp = getipnodebyname(hostname, pai->ai_family, AI_ADDRCONFIG, - &h_error); + hp = _getipnodebyname_multi(hostname, pai->ai_family, AI_ADDRCONFIG, + &h_error); if (hp == NULL) { switch (h_error) { case HOST_NOT_FOUND: @@ -519,8 +494,12 @@ for (i = 0; hp->h_addr_list[i] != NULL; i++) { af = hp->h_addrtype; ap = hp->h_addr_list[i]; + + if (pai->ai_family != AF_UNSPEC && af != pai->ai_family) + continue; - if (af != pai->ai_family) + afd = find_afd(af); + if (afd == NULL) continue; GET_AI(cur->ai_next, afd, ap); Index: name6.c =================================================================== RCS file: /home/ncvs/src/lib/libc/net/name6.c,v retrieving revision 1.7 diff -u -r1.7 name6.c --- name6.c 2000/03/15 15:04:54 1.7 +++ name6.c 2000/04/06 03:50:47 @@ -42,11 +42,13 @@ #include #include #include +#include #include #include #include +#include #include #include #include @@ -255,8 +257,6 @@ if (flags & AI_ADDRCONFIG) { int s; - if ((s = socket(af, SOCK_DGRAM, 0)) < 0) - return NULL; /* * TODO: * Note that implementation dependent test for address @@ -264,7 +264,23 @@ * (or apropriate interval), * because addresses will be dynamically assigned or deleted. */ - _close(s); + if (af == AF_UNSPEC) { + if ((s = socket(AF_INET6, SOCK_DGRAM, 0)) < 0) + af = AF_INET; + else { + _close(s); + if ((s = socket(AF_INET, SOCK_DGRAM, 0)) < 0) + af = AF_INET6; + else + _close(s); + } + + } + if (af != AF_UNSPEC) { + if ((s = socket(af, SOCK_DGRAM, 0)) < 0) + return NULL; + _close(s); + } } for (i = 0; i < MAXHOSTCONF; i++) { @@ -277,16 +293,19 @@ return NULL; } +/* getipnodebyname() internal routine for multiple query(PF_UNSPEC) support. */ struct hostent * -getipnodebyname(const char *name, int af, int flags, int *errp) +_getipnodebyname_multi(const char *name, int af, int flags, int *errp) { struct hostent *hp; union inx_addr addrbuf; + /* XXX: PF_UNSPEC is only supposed to be passed from getaddrinfo() */ if (af != AF_INET #ifdef INET6 && af != AF_INET6 #endif + && af != PF_UNSPEC ) { *errp = NO_RECOVERY; @@ -341,6 +360,21 @@ } struct hostent * +getipnodebyname(const char *name, int af, int flags, int *errp) +{ + if (af != AF_INET +#ifdef INET6 + && af != AF_INET6 +#endif + ) + { + *errp = NO_RECOVERY; + return NULL; + } + return(_getipnodebyname_multi(name, af ,flags, errp)); +} + +struct hostent * getipnodebyaddr(const void *src, size_t len, int af, int *errp) { struct hostent *hp; @@ -746,6 +780,7 @@ char *aliases[MAXALIASES + 1], *addrs[2]; union inx_addr addrbuf; char buf[BUFSIZ]; + int af0 = af; if ((fp = _files_open(errp)) == NULL) return NULL; @@ -766,11 +801,39 @@ } if (!match) continue; - if ((af == AF_INET - ? inet_aton(addrstr, (struct in_addr *)&addrbuf) - : inet_pton(af, addrstr, &addrbuf)) != 1) { + switch (af0) { + case AF_INET: + if (inet_aton(addrstr, (struct in_addr *)&addrbuf) + != 1) { + *errp = NO_DATA; /* name found */ + continue; + } + af = af0; + break; +#ifdef INET6 + case AF_INET6: + if (inet_pton(af, addrstr, &addrbuf) != 1) { + *errp = NO_DATA; /* name found */ + continue; + } + af = af0; + break; +#endif + case AF_UNSPEC: + if (inet_aton(addrstr, (struct in_addr *)&addrbuf) + == 1) { + af = AF_INET; + break; + } +#ifdef INET6 + if (inet_pton(AF_INET6, addrstr, &addrbuf) == 1) { + af = AF_INET6; + break; + } +#endif *errp = NO_DATA; /* name found */ continue; + /* NOTREACHED */ } hp = &hpbuf; hp->h_name = cname; @@ -842,6 +905,8 @@ { struct hostent *hp = NULL; + if (af == AF_UNSPEC) + af = AF_INET; if (af == AF_INET) { hp = _gethostbynisname(name, af); if (hp != NULL) @@ -870,15 +935,22 @@ #define DNS_ASSERT(X) if (!(X)) { goto badanswer; } #endif +struct __res_type_list { + SLIST_ENTRY(__res_type_list) rtl_entry; + int rtl_type; +}; + static struct hostent * -_dns_ghbyname(const char *name, int af, int *errp) +_gethpbyanswer(answer, anslen, qtype, errp) + const u_char *answer; + int anslen; + int qtype; + int *errp; { int n; - u_char answer[BUFSIZ]; char tbuf[MAXDNAME+1]; HEADER *hp; - u_char *cp, *eom; - int qtype; + const u_char *cp, *eom; int type, class, ancount, qdcount; u_long ttl; char hostbuf[BUFSIZ]; @@ -889,30 +961,17 @@ int buflen; int na, nh; - if ((_res.options & RES_INIT) == 0) { - if (res_init() < 0) { - *errp = h_errno; - return NULL; - } - } hbuf.h_aliases = alist; - hbuf.h_addrtype = af; - hbuf.h_length = ADDRLEN(af); - hbuf.h_addr_list = hlist; - na = nh = 0; - + hbuf.h_addrtype = #ifdef INET6 - qtype = (af == AF_INET6 ? T_AAAA : T_A); -#else - qtype = T_A; + (qtype == T_AAAA) ? AF_INET6 : #endif - n = res_search(name, C_IN, qtype, answer, sizeof(answer)); - if (n < 0) { - *errp = h_errno; - return NULL; - } + AF_INET; + hbuf.h_length = ADDRLEN(hbuf.h_addrtype); + hbuf.h_addr_list = hlist; + na = nh = 0; hp = (HEADER *)answer; - eom = answer + n; + eom = answer + anslen; ancount = ntohs(hp->ancount); qdcount = ntohs(hp->qdcount); DNS_ASSERT(qdcount == 1); @@ -992,6 +1051,210 @@ alist[na] = NULL; hlist[nh] = NULL; return _hpcopy(&hbuf, errp); +} + +/* res_search() variant with multiple query support. */ +static struct hostent * +_res_search_multi(name, rtl, errp) + const char *name; /* domain name */ + struct __res_type_list *rtl; /* list of query types */ + int *errp; +{ + u_char answer[BUFSIZ]; /* buffer to put answer */ + const char *cp, * const *domain; + struct hostent *hp0 = NULL, *hp; + u_int dots; + int trailing_dot, ret, saved_herrno; + int got_nodata = 0, got_servfail = 0, tried_as_is = 0; + struct __res_type_list *rtl0 = rtl; + + if ((_res.options & RES_INIT) == 0 && res_init() == -1) { + *errp = NETDB_INTERNAL; + return (NULL); + } + dots = 0; + for (cp = name; *cp; cp++) + dots += (*cp == '.'); + trailing_dot = 0; + if (cp > name && *--cp == '.') + trailing_dot++; + + /* If there aren't any dots, it could be a user-level alias */ + if (!dots && (cp = hostalias(name)) != NULL) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_query(cp, C_IN, rtl->rtl_type, answer, + sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + return (hp0); + } + + /* + * If there are dots in the name already, let's just give it a try + * 'as is'. The threshold can be set with the "ndots" option. + */ + saved_herrno = -1; + if (dots >= _res.ndots) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, NULL, C_IN, rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + saved_herrno = *errp; + tried_as_is++; + } + + /* + * We do at least one level of search if + * - there is no dot and RES_DEFNAME is set, or + * - there is at least one dot, there is no trailing dot, + * and RES_DNSRCH is set. + */ + if ((!dots && (_res.options & RES_DEFNAMES)) || + (dots && !trailing_dot && (_res.options & RES_DNSRCH))) { + int done = 0; + + for (domain = (const char * const *)_res.dnsrch; + *domain && !done; + domain++) { + + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, *domain, C_IN, + rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, + rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + + /* + * If no server present, give up. + * If name isn't found in this domain, + * keep trying higher domains in the search list + * (if that's enabled). + * On a NO_DATA error, keep trying, otherwise + * a wildcard entry of another type could keep us + * from finding this entry higher in the domain. + * If we get some other error (negative answer or + * server failure), then stop searching up, + * but try the input name below in case it's + * fully-qualified. + */ + if (errno == ECONNREFUSED) { + *errp = TRY_AGAIN; + return (NULL); + } + + switch (*errp) { + case NO_DATA: + got_nodata++; + /* FALLTHROUGH */ + case HOST_NOT_FOUND: + /* keep trying */ + break; + case TRY_AGAIN: + if (((HEADER *)answer)->rcode == SERVFAIL) { + /* try next search element, if any */ + got_servfail++; + break; + } + /* FALLTHROUGH */ + default: + /* anything else implies that we're done */ + done++; + } + + /* if we got here for some reason other than DNSRCH, + * we only wanted one iteration of the loop, so stop. + */ + if (!(_res.options & RES_DNSRCH)) + done++; + } + } + + /* + * If we have not already tried the name "as is", do that now. + * note that we do this regardless of how many dots were in the + * name or whether it ends with a dot unless NOTLDQUERY is set. + */ + if (!tried_as_is && (dots || !(_res.options & RES_NOTLDQUERY))) { + for(rtl = rtl0; rtl != NULL; + rtl = SLIST_NEXT(rtl, rtl_entry)) { + ret = res_querydomain(name, NULL, C_IN, rtl->rtl_type, + answer, sizeof(answer)); + if (ret > 0) { + hp = _gethpbyanswer(answer, ret, rtl->rtl_type, + errp); + hp0 = _hpmerge(hp0, hp, errp); + } + } + if (hp0 != NULL) + return (hp0); + } + + /* if we got here, we didn't satisfy the search. + * if we did an initial full query, return that query's h_errno + * (note that we wouldn't be here if that query had succeeded). + * else if we ever got a nodata, send that back as the reason. + * else send back meaningless h_errno, that being the one from + * the last DNSRCH we did. + */ + if (saved_herrno != -1) + *errp = saved_herrno; + else if (got_nodata) + *errp = NO_DATA; + else if (got_servfail) + *errp = TRY_AGAIN; + return (NULL); +} + +static struct hostent * +_dns_ghbyname(const char *name, int af, int *errp) +{ + struct __res_type_list *rtl, rtl4; +#ifdef INET6 + struct __res_type_list rtl6; +#endif + +#ifdef INET6 + switch (af) { + case AF_UNSPEC: + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + SLIST_NEXT(&rtl6, rtl_entry) = &rtl4; rtl6.rtl_type = T_AAAA; + rtl = &rtl6; + break; + case AF_INET6: + SLIST_NEXT(&rtl6, rtl_entry) = NULL; rtl6.rtl_type = T_AAAA; + rtl = &rtl6; + break; + case AF_INET: + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + rtl = &rtl4; + break; + } +#else + SLIST_NEXT(&rtl4, rtl_entry) = NULL; rtl4.rtl_type = T_A; + rtl = &rtl4; +#endif + return(_res_search_multi(name, rtl, errp)); } static struct hostent * ----Next_Part(Thu_Apr__6_12:53:40_2000_518)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 21: 8:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 72F4D37BEB6 for ; Wed, 5 Apr 2000 21:08:49 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA99113; Wed, 5 Apr 2000 22:08:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA88417; Wed, 5 Apr 2000 22:07:45 -0600 (MDT) Message-Id: <200004060407.WAA88417@harmony.village.org> To: Andrzej Bialecki Subject: Re: Installworld to /some/where/... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Apr 2000 20:25:56 +0200." References: Date: Wed, 05 Apr 2000 22:07:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Andrzej Bialecki writes: : The reason I'm asking is that I'm looking for a method to easily : clone/upgrade a bunch of servers without having to do 'make world' on all : of them. I'm not satisfied either with using dd - the machines are not : identical, there are some bits and pieces of config specific to each : machine. So far the best method was to do a make world, but it becomes : more and more a nuisance and waste of time... Two things. One, you could use DESTDIR to install the stuff, but it won't create a bootable disk. This + mergemaster is a good option to update an existing disk. The other option is do mount /usr/obj on the target machines and do an make installworld. This usually takes me about 20 minutes or so, which is much faster than any hardware-hacking I'd need to do to get a disk from one machine to another. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 21:16:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 18CA537B6A1 for ; Wed, 5 Apr 2000 21:16:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA99133; Wed, 5 Apr 2000 22:16:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA88467; Wed, 5 Apr 2000 22:15:29 -0600 (MDT) Message-Id: <200004060415.WAA88467@harmony.village.org> To: Brooks Davis Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT Cc: "Eric D. Futch" , Stephan van Beerschoten , current@FreeBSD.org In-reply-to: Your message of "Wed, 05 Apr 2000 18:29:27 PDT." <20000405182927.A10848@orion.ac.hmc.edu> References: <20000405182927.A10848@orion.ac.hmc.edu> <20000405154940.A14513@orion.ac.hmc.edu> Date: Wed, 05 Apr 2000 22:15:29 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000405182927.A10848@orion.ac.hmc.edu> Brooks Davis writes: : http://www.one-eyed-alien.net/~brooks/FreeBSD/if_vx.diff + irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, + 0, ~0, 1, RF_ACTIVE); irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); pci devices can share interrupts. Otherwise I didn't see anything wrong with this. I have a 905B, so I can't test this driver on hardware I have :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 21:34:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 137BB37B7F0 for ; Wed, 5 Apr 2000 21:34:45 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id C72632DC0C; Thu, 6 Apr 2000 06:38:37 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 7F93A7815; Thu, 6 Apr 2000 06:31:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 7D91610E17; Thu, 6 Apr 2000 06:31:20 +0200 (CEST) Date: Thu, 6 Apr 2000 06:31:20 +0200 (CEST) From: Andrzej Bialecki To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installworld to /some/where/... In-Reply-To: <200004060407.WAA88417@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Apr 2000, Warner Losh wrote: > In message Andrzej Bialecki writes: > : The reason I'm asking is that I'm looking for a method to easily > : clone/upgrade a bunch of servers without having to do 'make world' on all > : of them. I'm not satisfied either with using dd - the machines are not > : identical, there are some bits and pieces of config specific to each > : machine. So far the best method was to do a make world, but it becomes > : more and more a nuisance and waste of time... > > Two things. One, you could use DESTDIR to install the stuff, but it > won't create a bootable disk. This + mergemaster is a good option to > update an existing disk. > > The other option is do mount /usr/obj on the target machines and do an > make installworld. This usually takes me about 20 minutes or so, > which is much faster than any hardware-hacking I'd need to do to get a > disk from one machine to another. That's exactly what I was looking for. Thank you. Thanks to all who replied! Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 21:53:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from web1.allunix.com (17.93.rsvl.dsl.quiknet.com [207.231.93.17]) by hub.freebsd.org (Postfix) with ESMTP id BFD6137B8A1 for ; Wed, 5 Apr 2000 21:53:42 -0700 (PDT) (envelope-from David@allunix.com) Received: from tiffany (tiffany.allunix.com [192.168.3.4]) by web1.allunix.com (8.9.3/8.9.3) with ESMTP id VAA03103; Wed, 5 Apr 2000 21:28:19 -0700 (PDT) (envelope-from David@allunix.com) From: David@allunix.com To: current@FreeBSD.ORG Date: Wed, 5 Apr 2000 21:29:47 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: 75 second delay using telnet/ssh (ipv6 related) Cc: current@FreeBSD.ORG Message-ID: <38EBB04B.13877.3416842@localhost> References: <20000402124742P.shin@nd.net.fujitsu.co.jp> In-reply-to: <20000406125344R.shin@nd.net.fujitsu.co.jp> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote: Is this problem just with current? I am having the same type of problem with the sshd daemon on 4.0-STABLE David DeTinne > > > On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote: > > > I applied it and am running with it now, but I can't say one way > > > or another if it has fixed the problem :-). It only cropped up > > > every couple of weeks and seemingly random at that. I'll assume > > > it works if I don't see it happening again. > > > > > > Thanks, > > > > OK, anyway it is rather critical fix, so I think it needs some > > testing period. > > > I did a little bit cleanup, and made new patches. > (with no behaviour change) > I already received several positive confirmations for the > patches. > > I'll wait more several days and will commit this if no > significant problem is found for this. > > Thanks, > Yoshinobu Inoue > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 22:16:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id DD0FD37B518 for ; Wed, 5 Apr 2000 22:16:47 -0700 (PDT) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id OAA13016; Thu, 6 Apr 2000 14:16:45 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id OAA00468; Thu, 6 Apr 2000 14:16:44 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id OAA25267; Thu, 6 Apr 2000 14:16:44 +0900 (JST) To: David@allunix.com Cc: current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <38EBB04B.13877.3416842@localhost> References: <20000402124742P.shin@nd.net.fujitsu.co.jp> <20000406125344R.shin@nd.net.fujitsu.co.jp> <38EBB04B.13877.3416842@localhost> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000406141745U.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Apr 2000 14:17:45 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote: > Is this problem just with current? I am having the same type of > problem with the sshd daemon on 4.0-STABLE The problem also happens on 4.0-STABLE, and my patch also applies to it. I'll MFC it to 4.0-STABLE after I confirmed it on the current. But if you have trouble now, please try this patch on your 4.0-STABLE machine. I'll also send this patch to freebsd-stable. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 22:58:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0777837BB61 for ; Wed, 5 Apr 2000 22:58:32 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA99574; Wed, 5 Apr 2000 23:58:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA88971; Wed, 5 Apr 2000 23:57:43 -0600 (MDT) Message-Id: <200004060557.XAA88971@harmony.village.org> To: David@allunix.com Subject: Re: 75 second delay using telnet/ssh (ipv6 related) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Apr 2000 21:29:47 PDT." <38EBB04B.13877.3416842@localhost> References: <38EBB04B.13877.3416842@localhost> <20000402124742P.shin@nd.net.fujitsu.co.jp> Date: Wed, 05 Apr 2000 23:57:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38EBB04B.13877.3416842@localhost> David@allunix.com writes: : Is this problem just with current? I am having the same type of : problem with the sshd daemon on 4.0-STABLE We found that the AAAA records were confusing our local name server. Kill and restart it and it was fine again for a while. When we rebuilt the kernel on the machine that was slow w/o INET6 the name server stopped, and it stopped going out to lunch. 4.0 machine against a 3.4release-ish named. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 5 23:21:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 8FCE237B8BF for ; Wed, 5 Apr 2000 23:21:42 -0700 (PDT) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id PAA05027; Thu, 6 Apr 2000 15:21:40 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id PAA14074; Thu, 6 Apr 2000 15:21:38 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id PAA27399; Thu, 6 Apr 2000 15:21:37 +0900 (JST) To: imp@village.org Cc: David@allunix.com, current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <200004060557.XAA88971@harmony.village.org> References: <38EBB04B.13877.3416842@localhost> <20000402124742P.shin@nd.net.fujitsu.co.jp> <200004060557.XAA88971@harmony.village.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000406152238G.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Apr 2000 15:22:38 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <38EBB04B.13877.3416842@localhost> David@allunix.com writes: > : Is this problem just with current? I am having the same type of > : problem with the sshd daemon on 4.0-STABLE > > We found that the AAAA records were confusing our local name server. > Kill and restart it and it was fine again for a while. When we > rebuilt the kernel on the machine that was slow w/o INET6 the name > server stopped, and it stopped going out to lunch. 4.0 machine > against a 3.4release-ish named. > > Warner Are those AAAA records defined for local machines on the local name server? Then, I would like to try same configuration, and could you please give me that zone files? Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 0:27: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 2AE2C37BDF5 for ; Thu, 6 Apr 2000 00:26:53 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-16.iptelecom.net.ua [212.9.227.16]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA03871; Thu, 6 Apr 2000 10:33:30 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA03589; Thu, 6 Apr 2000 10:26:14 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EC3C14.2471F70@altavista.net> Date: Thu, 06 Apr 2000 10:26:13 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Soren Schmidt Cc: Jon Hamilton , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) References: <200004051431.QAA47392@freebsd.dk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Maxim Sobolev wrote: > > > > I've tried it on my home machine and failed to reproduce also. However it is > > strange, because if it is the CPU/Memory problem, then there should be other signs > > - random applications crashes, spontaneous reboots etc., but machine is pretty > > stable - up and running for weeks since 4.0-REL w/o any notable problems. On the > > other hand if it is HDD problem or problem with its cable, then there should also > > be some signs. I've never seen this problem on the same hardware under 2.* and 3.* > > during past 1.5 years. Maybe it is ata driver, because it is the only thing that is > > known not very extensively tested (and has already acknoweleged problems with some > > hardware). I'll try to fallback to the wd and look what will happen. > > Uhm what acknowledged problems is that ? I know of no cases of data > corruption in this way, its all pretty much go/nogo situations... Soren, I apologise for blaming your ata, it seems that it is not it, because when I switched back to the old wd it brought the same unpleasant result. I've also check the cable by replacing it with another and trying to plug it firmly, but it also did not solve the problem. Could you as a HDD expert suggest the way to track it down? Maybe you had previously seen any problems of that sort. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 0:40:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 32CE537BC0D for ; Thu, 6 Apr 2000 00:40:55 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA99835; Thu, 6 Apr 2000 01:40:53 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA89466; Thu, 6 Apr 2000 01:40:06 -0600 (MDT) Message-Id: <200004060740.BAA89466@harmony.village.org> To: Yoshinobu Inoue Subject: Re: 75 second delay using telnet/ssh (ipv6 related) Cc: David@allunix.com, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 06 Apr 2000 15:22:38 +0900." <20000406152238G.shin@nd.net.fujitsu.co.jp> References: <20000406152238G.shin@nd.net.fujitsu.co.jp> <38EBB04B.13877.3416842@localhost> <20000402124742P.shin@nd.net.fujitsu.co.jp> <200004060557.XAA88971@harmony.village.org> Date: Thu, 06 Apr 2000 01:40:06 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000406152238G.shin@nd.net.fujitsu.co.jp> Yoshinobu Inoue writes: : Are those AAAA records defined for local machines on the local : name server? : Then, I would like to try same configuration, and could you : please give me that zone files? Machine A is trying to access a filesystem on machine B via amd + nfs. Machine A first looks up machine B's AAAA record, this fails and then it looks up machine B's A record. This succeeds and the file accesses go through. However, when Machine B's named goes to lunch (this is the named that machine A is using), the query for the AAAA record times out and then the query for A happens some 30-45 seconds later and succeeds right away. At least that's my reading of the tcpdump traffic. None of these machines should be using IPv6 since we have no IPv6 machines and don't use IPv6 address. No AAAA records are defined at all. And it only seems to happen sometimes. I don't know what kills named in the first place, just what happens when it goes partially brain dead. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 0:50:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 9B4DD37C03C for ; Thu, 6 Apr 2000 00:50:43 -0700 (PDT) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id QAA25549; Thu, 6 Apr 2000 16:50:41 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master) id QAA00702; Thu, 6 Apr 2000 16:50:40 +0900 (JST) Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id QAA00491; Thu, 6 Apr 2000 16:50:40 +0900 (JST) To: imp@village.org Cc: David@allunix.com, current@FreeBSD.ORG Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: <200004060740.BAA89466@harmony.village.org> References: <20000402124742P.shin@nd.net.fujitsu.co.jp> <200004060557.XAA88971@harmony.village.org> <200004060740.BAA89466@harmony.village.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000406165141W.shin@nd.net.fujitsu.co.jp> Date: Thu, 06 Apr 2000 16:51:41 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 26 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Machine A is trying to access a filesystem on machine B via amd + > nfs. Machine A first looks up machine B's AAAA record, this fails and > then it looks up machine B's A record. This succeeds and the file > accesses go through. > > However, when Machine B's named goes to lunch (this is the named that > machine A is using), the query for the AAAA record times out and then > the query for A happens some 30-45 seconds later and succeeds right > away. > > At least that's my reading of the tcpdump traffic. > > None of these machines should be using IPv6 since we have no IPv6 > machines and don't use IPv6 address. No AAAA records are defined at > all. And it only seems to happen sometimes. I don't know what kills > named in the first place, just what happens when it goes partially > brain dead. > > Warner Ah, that will be same problem with others and it is not named problem but resolver problem, I think. Could you please try applying my patches to the 4.0 machine? Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 1: 2:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 54D0C37BB68 for ; Thu, 6 Apr 2000 01:02:17 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id BAA29325; Thu, 6 Apr 2000 01:01:05 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <38EC443F.C1503735@gorean.org> Date: Thu, 06 Apr 2000 01:01:04 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Masto Cc: Nick Hibma , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? References: <20000403024241.A13365@netmonger.net> <20000403130055.A8685@netmonger.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Masto wrote: > > On Mon, Apr 03, 2000 at 10:52:13AM +0100, Nick Hibma wrote: > > Are there actually any good reasons why we _should_ upgrade in the first > > place? > > Of course. We now have an obsolete version of Perl. That should be > reason enough to upgrade. You haven't given a sufficiently compelling definition of "obsolete" yet. I think that what people are really asking is, "What does this new perl get us that we don't already have?" Once we've answered that, then we can balance the benefits against the costs (which are pretty high, considering the complexity of integrating perl into the berkeley make environment) and then we can try and apply those arguments in the search for someone who is willing and able to do the work. > 5.6 is the first major release in over a year. It has significant new > syntax that I intend to start using immediately, as will much of the > rest of the Perl community. "Why haven't you upgraded yet?" is a > rather traditional battle cry. Sure it is, in the linux community. And no, I'm not casting aspersions here. FreeBSD has a much different set of development priorities. Our friends in the linux community like to be on the "hemmorhaging" edge, as early adopters of stuff like a .0 release of perl, we prefer to wait till some of the wounds have scabbed over a bit. (Note, I'm talking about my perceptions based on experience, I don't speak for anyone other than myself.) Also, anyone who wants to use the new perl can. You just compile it up and install it wherever you want. We've even provided hooks to prevent the system perl from being compiled if you need that level of control over the process. > I don't know whey they called it 5.6.0.. I'm dropping the .0, because > it seems to inspire the usual "point-oh fear". In my experience with perl (which is fairly extensive) that fear is well justified. > This is not a > "point-oh" release in the usual sense, and waiting for 5.6.1 would be > a mistake. Why? -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 1:17:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from lola.heim10.tu-clausthal.de (lola.heim10.tu-clausthal.de [139.174.241.25]) by hub.freebsd.org (Postfix) with ESMTP id E947B37BACF for ; Thu, 6 Apr 2000 01:16:55 -0700 (PDT) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Received: from heim9.tu-clausthal.de (localhost.heim10.tu-clausthal.de [127.0.0.1]) by lola.heim10.tu-clausthal.de (8.9.3/8.9.3) with ESMTP id KAA00261; Thu, 6 Apr 2000 10:16:44 +0200 (CEST) (envelope-from norbert.irmer@heim9.tu-clausthal.de) Message-ID: <38EC47EC.78300EE5@heim9.tu-clausthal.de> Date: Thu, 06 Apr 2000 10:16:44 +0200 From: Norbert Irmer X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kent Hauser Cc: current@FreeBSD.ORG Subject: Re: pcm & SoundBlaster Live! PCI card References: <200004052335.TAA00273@chapel-hill.tfd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you really using the latest FREEBSD_5.0_CURRENT ? I have just device pcm in my kernel config (without PNPBIOS) and the SBLive works fine (many thanks to Cameron for his nice driver). Make sure that the line dev/sound/pci/emu10k1.c optional pcm pci is not commented (in /usr/src/sys/conf/files) norbert Kent Hauser wrote: > > Hi all, > > I can't for the life of me get my new gateway computer > to make any noise (at least with FreeBSD). I've tried > all the PNP/nonPNP combinations from LINT (and then some). > > The card is a "Creative Labs Soundblaster Live!" PCI card. > The gateway blurb is found on: > > http://www.gateway.com/mes/default.asp?page=soundcards > > The sound config lines & dmesg output are attached. Any > pointers would be greatly appreciated. > > Thanks a bunch. > Kent > > ========= > options PNPBIOS > device pcm > device sbc > device csa > device pca0 at isa? port IO_TIMER1 > ========= > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Wed Apr 5 19:14:25 EDT 2000 > kent@chapel-hill.tfd.com:/usr/src/sys/compile/GW > Calibrating clock(s) ... TSC clock: 696358058 Hz, i8254 clock: 1193099 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CLK_USE_TSC_CALIBRATION not specified - using old calibration method > CPU: Pentium III/Pentium III Xeon (696.41-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x681 Stepping = 1 > Features=0x383f9ff > real memory = 134217728 (131072K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009dfff, 643072 bytes (157 pages) > 0x00462000 - 0x040fcfff, 63549440 bytes (15515 pages) > 0x04100000 - 0x07ff7fff, 66027520 bytes (16120 pages) > avail memory = 126103552 (123148K bytes) > bios32: Found BIOS32 Service Directory header at 0xc00f6a90 > bios32: Entry = 0xfd780 (c00fd780) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0x203 > pnpbios: Found PnP BIOS data at 0xc00f6ae0 > pnpbios: Entry = f0000:9e33 Rev = 1.0 > Other BIOS signatures found: > ACPI: 000f6ac0 > Preloaded elf kernel "kernel" at 0xc0449000. > Pentium Pro MTRR support enabled > md0: Malloc disk > Creating DISK md0 > Math emulator present > pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) > npx0: on motherboard > npx0: INT 16 interface > pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) > pcib0: on motherboard > found-> vendor=0x8086, dev=0x7190, revid=0x03 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base f8000000, size 26, enabled > found-> vendor=0x8086, dev=0x7191, revid=0x03 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 > found-> vendor=0x8086, dev=0x7110, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[20]: type 1, range 32, base 00001400, size 4, enabled > found-> vendor=0x8086, dev=0x7112, revid=0x01 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=9 > map[20]: type 1, range 32, base 000010c0, size 5, enabled > found-> vendor=0x8086, dev=0x7113, revid=0x02 > class=06-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[90]: type 1, range 32, base 00007000, size 4, enabled > found-> vendor=0x14f1, dev=0x1036, revid=0x08 > class=07-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=5 > map[10]: type 1, range 32, base f4000000, size 16, enabled > map[14]: type 1, range 32, base 00001410, size 3, enabled > found-> vendor=0x1102, dev=0x0002, revid=0x07 > class=04-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base 000010e0, size 5, enabled > found-> vendor=0x1102, dev=0x7002, revid=0x07 > class=09-80-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > map[10]: type 3, range 32, base 00001418, size 3, enabled > found-> vendor=0x105a, dev=0x4d38, revid=0x01 > class=01-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[10]: type 1, range 32, base 00001430, size 3, enabled > map[14]: type 1, range 32, base 00001424, size 2, enabled > map[18]: type 3, range 32, base 00001428, size 3, enabled > map[1c]: type 1, range 32, base 00001420, size 2, enabled > map[20]: type 1, range 32, base 00001080, size 6, enabled > map[24]: type 1, range 32, base f4020000, size 17, enabled > found-> vendor=0x10b7, dev=0x9006, revid=0x04 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=9 > map[10]: type 1, range 32, base 00001000, size 7, enabled > map[14]: type 1, range 32, base f4010000, size 7, enabled > found-> vendor=0x12b9, dev=0x1008, revid=0x01 > class=07-00-02, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=5 > map[10]: type 3, range 32, base 00001438, size 3, enabled > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > found-> vendor=0x10de, dev=0x0028, revid=0x15 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base f5000000, size 24, enabled > map[14]: type 1, range 32, base fc000000, size 25, enabled > pci1: on pcib1 > pci1: (vendor=0x10de, dev=0x0028) at 0.0 irq 11 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0x1400-0x140f at device 7.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x1400 > ata0: mask=00 status0=ff status1=ff > ata0: probe allocation failed > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x1408 > ata1: mask=03 status0=50 status1=50 > ata1: mask=03 status0=00 status1=10 > ata1: devices = 0xc > ata1: at 0x170 irq 15 on atapci0 > pci0: (vendor=0x8086, dev=0x7112) at 7.2 irq 9 > chip1: port 0x7000-0x700f at device 7.3 on pci0 > pci0: (vendor=0x14f1, dev=0x1036) at 13.0 irq 5 > pci0: (vendor=0x1102, dev=0x0002) at 14.0 irq 11 > pci0: (vendor=0x1102, dev=0x7002) at 14.1 > atapci1: port 0x1080-0x10bf,0x1420-0x1423,0x1428-0x142f,0x1424-0x1427,0x1430-0x1437 mem 0xf4020000-0xf403ffff irq 10 at device 15.0 on pci0 > ata-: ata2 exists, using next available unit number > ata2: iobase=0x1430 altiobase=0x1424 bmaddr=0x1080 > ata2: mask=03 status0=50 status1=00 > ata2: mask=03 status0=50 status1=00 > ata2: devices = 0x1 > ata2: at 0x1430 on atapci1 > ata3: iobase=0x1428 altiobase=0x1420 bmaddr=0x1088 > ata3: mask=03 status0=00 status1=00 > ata3: mask=03 status0=00 status1=00 > ata3: devices = 0x0 > ata3: probe allocation failed > xl0: <3Com 3c900B-TPC Etherlink XL> port 0x1000-0x107f mem 0xf4010000-0xf401007f irq 9 at device 16.0 on pci0 > xl0: Ethernet address: 00:50:da:17:a0:3a > xl0: media options word: 18 > xl0: guessing TPC (BNC/TP) > xl0: found 10baseT > xl0: found BNC > xl0: selecting 10baseT transceiver, half duplex > xl0: supplying EUI64: 00:50:da:ff:fe:17:a0:3a > bpf: xl0 attached > sio0: irq maps: 0x3 0x23 0x3 0x3 > sio0: <3COM PCI FaxModem> port 0x1438-0x143f irq 5 at device 17.0 on pci0 > sio0: moving to sio4 > sio4: type 16550A > pnpbios: 17 devices, largest 317 bytes > PNP0c02: adding io range 0x370-0x371, size=0x2, align=0x1 > PNP0c02: adding io range 0xea-0xeb, size=0x2, align=0x1 > PNP0c02: adding fixed memory32 range 0xfffc0000-0xffffffff, size=0x40000 > PNP0c02: end config > pnpbios: handle 0 device ID PNP0c02 (020cd041) > PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 > PNP0c01: adding fixed memory32 range 0xe4000-0xfffff, size=0x1c000 > PNP0c01: adding fixed memory32 range 0x100000-0x7ffffff, size=0x7f00000 > PNP0c01: adding fixed memory32 range 0xfff80000-0xfffbffff, size=0x40000 > PNP0c01: end config > pnpbios: handle 1 device ID PNP0c01 (010cd041) > PNP0200: adding io range 0-0xf, size=0x10, align=0x1 > PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 > PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 > PNP0200: adding dma mask 0x10 > PNP0200: end config > pnpbios: handle 2 device ID PNP0200 (0002d041) > PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 > PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 > PNP0000: adding irq mask 00x4 > PNP0000: end config > pnpbios: handle 3 device ID PNP0000 (0000d041) > PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 > PNP0100: adding irq mask 00x1 > PNP0100: end config > pnpbios: handle 4 device ID PNP0100 (0001d041) > PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 > PNP0b00: adding irq mask 0x100 > PNP0b00: end config > pnpbios: handle 5 device ID PNP0b00 (000bd041) > PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 > PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 > PNP0303: adding irq mask 00x2 > PNP0303: end config > pnpbios: handle 6 device ID PNP0303 (0303d041) > PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 > PNP0c04: adding irq mask 0x2000 > PNP0c04: end config > pnpbios: handle 7 device ID PNP0c04 (040cd041) > PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 > PNP0800: end config > pnpbios: handle 8 device ID PNP0800 (0008d041) > PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 > PNP0a03: end config > pnpbios: handle 9 device ID PNP0a03 (030ad041) > PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 > PNP0c02: adding io range 0x8000-0x803f, size=0x40, align=0x1 > PNP0c02: adding io range 0x7000-0x700f, size=0x10, align=0x1 > PNP0c02: end config > pnpbios: handle 10 device ID PNP0c02 (020cd041) > PNP0c02: adding fixed memory32 range 0xcb000-0xcbfff, size=0x1000 > PNP0c02: end config > pnpbios: handle 12 device ID PNP0c02 (020cd041) > PNP0f13: adding irq mask 0x1000 > PNP0f13: end config > pnpbios: handle 13 device ID PNP0f13 (130fd041) > PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 > PNP0501: adding irq mask 0x10 > PNP0501: end config > pnpbios: handle 14 device ID PNP0501 (0105d041) > PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 > PNP0501: adding irq mask 00x8 > PNP0501: end config > pnpbios: handle 15 device ID PNP0501 (0105d041) > PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 > PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 > PNP0700: adding irq mask 0x40 > PNP0700: adding dma mask 0x4 > PNP0700: end config > pnpbios: handle 17 device ID PNP0700 (0007d041) > PNP0401: adding io range 0x378-0x37f, size=0x8, align=0x8 > PNP0401: adding io range 0x778-0x77f, size=0x8, align=0x8 > PNP0401: adding irq mask 0x80 > PNP0401: adding dma mask 0x8 > PNP0401: end config > pnpbios: handle 20 device ID PNP0401 (0104d041) > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > ata-: ata0 exists, using next available unit number > ata-: ata1 exists, using next available unit number > ex_isa_identify() > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 > ata4: mask=00 status0=ff status1=ff > ata4: probe allocation failed > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x330 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x334 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x230 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x234 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x130 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x134 > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 > psm0: current command byte:0047 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fa > kbdc: RESET_AUX status:00aa > kbdc: RESET_AUX ID:0000 > psm: status 00 02 64 > psm: status 00 00 64 > psm: status 00 03 64 > psm: status 00 03 64 > psm: data 08 06 00 > psm: data 08 01 00 > psm: status 00 02 64 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3-00, 3 buttons > psm0: config:00000000, flags:00000000, packet size:4 > psm0: syncmask:08, syncbits:08 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > fb0: vga0, vga, type:VGA (5), flags:0x7007f > fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0e 0f 00 00 07 30 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) > pcic1: not probed (disabled) > sio0: irq maps: 0x41 0x51 0x41 0x41 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: irq maps: 0x41 0x49 0x41 0x41 > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > sio2: not probed (disabled) > sio3: not probed (disabled) > ppc0: parallel port found at 0x378 > ppc0: ECP SPP ECP+EPP SPP > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > bpf: lp0 attached > isa_compat: didn't get irq for le > pca0 at port 0x40 on isa0 > isa_probe_children: probing PnP devices > unknown0: at port 0x370-0x371,0xea-0xeb iomem 0xfffc0000-0xffffffff on isa0 > unknown1: at iomem 0-0x9ffff,0xe4000-0xfffff,0x100000-0x7ffffff,0xfff80000-0xfffbffff on isa0 > unknown2: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 > unknown: can't assign resources > unknown3: at port 0x40-0x43 irq 0 on isa0 > unknown4: at port 0x70-0x71 irq 8 on isa0 > unknown: can't assign resources > unknown5: at port 0xf0-0xff irq 13 on isa0 > pca1: at port 0x61 on isa0 > unknown6: at port 0xcf8-0xcff on isa0 > unknown7: at port 0x4d0-0x4d1,0x8000-0x803f,0x7000-0x700f on isa0 > unknown8: at iomem 0xcb000-0xcbfff on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > BIOS Geometries: > 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > new masks: bio 40088440, tty 400310ba, net 400712ba > bpf: sl0 attached > bpf: ppp0 attached > new masks: bio 40088440, tty 400310ba, net 400712ba > bpf: lo0 attached > bpf: gif0 attached > bpf: gif1 attached > bpf: gif2 attached > bpf: gif3 attached > bpf: stf0 attached > bpf: faith0 attached > IPsec: Initialized Security Association Processing. > ata2-master: success setting up UDMA4 mode on Promise chip > ad4: ATA-4 disk at ata2 as master > ad4: 26105MB (53464320 sectors), 53040 cyls, 16 heads, 63 S/T, 512 B/S > ad4: 16 secs/int, 32 depth queue, UDMA66 > ad4: piomode=4 dmamode=2 udmamode=4 cblid=1 > Creating DISK ad4 > Creating DISK wd4 > ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 > ata1-master: success setting up PIO4 mode on generic chip > acd0: DVD-ROM drive at ata1 as master > acd0: read 2750KB/s (6875KB/s), 512KB buffer, PIO4 > acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, packet > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked > ata1-slave: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 > ata1-slave: success setting up PIO4 mode on generic chip > acd1: CD-RW drive at ata1 as slave > acd1: read 4134KB/s (4134KB/s) write 689KB/s (689KB/s), 2048KB buffer, PIO4 > acd1: Reads: CD-R, CD-RW, CD-DA stream, packet > acd1: Writes: CD-R, CD-RW, test write > acd1: Audio: play, 2 volume levels > acd1: Mechanism: ejectable tray > acd1: Medium: no/blank disc inside, unlocked > Mounting root from ufs:/dev/ad4s2a > ad4s1: type 0xb, start 63, end = 16048934, size 16048872 : OK > ad4s2: type 0xa5, start 16048935, end = 53464319, size 37415385 : OK > start_init: trying /sbin/init > xl0: starting DAD for fe80:0001::0250:daff:fe17:a03a > bpf: tun0 attached > xl0: DAD complete for fe80:0001::0250:daff:fe17:a03a - no duplicates found > Linux-ELF exec handler installed > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- email: norbert.irmer@heim9.tu-clausthal.de web: http://gul.sourceforge.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 5:26:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat194.206.mpoweredpc.net [142.177.194.206]) by hub.freebsd.org (Postfix) with ESMTP id 7D4AE37BC2A for ; Thu, 6 Apr 2000 05:26:07 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id JAA02854; Thu, 6 Apr 2000 09:24:06 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 6 Apr 2000 09:24:06 -0300 (ADT) From: The Hermit Hacker To: Doug Barton Cc: Christopher Masto , Nick Hibma , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: <38EC443F.C1503735@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Doug Barton wrote: > Christopher Masto wrote: > > > > On Mon, Apr 03, 2000 at 10:52:13AM +0100, Nick Hibma wrote: > > > Are there actually any good reasons why we _should_ upgrade in the first > > > place? > > > > Of course. We now have an obsolete version of Perl. That should be > > reason enough to upgrade. > > You haven't given a sufficiently compelling definition of "obsolete" > yet. I think that what people are really asking is, "What does this new > perl get us that we don't already have?" Once we've answered that, then > we can balance the benefits against the costs (which are pretty high, > considering the complexity of integrating perl into the berkeley make > environment) and then we can try and apply those arguments in the search > for someone who is willing and able to do the work. My experiences with perl tend to be that as soon as a new release comes out, all the module maintainers tend to adopt it as standard and start to deprecate the older versions. I'm not saying that this is an overnight sort of thing, but it does pose a problem ... My stupid question, though, is why is this such a big issue? Would it be too hard to extend our /usr/src build process so that it is smart enough to do an install out of ports, and just build the ports version of 5.6.0, vs trying to integrate it into our build tree? Create a symlink to /usr/ports/devel/perl560 so that when it cd's to the perl directory and does a 'make', it builds that? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 5:43:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (mail.spc.nl [193.79.3.34]) by hub.freebsd.org (Postfix) with ESMTP id 687F837BD6A for ; Thu, 6 Apr 2000 05:43:23 -0700 (PDT) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (firewall.spcgroup.nl [193.79.3.33]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id OAA01497; Thu, 6 Apr 2000 14:43:03 +0200 Message-ID: <38EC86C5.6010206@spcgroup.nl> Date: Thu, 06 Apr 2000 14:44:53 +0200 From: Edwin Mons User-Agent: Mozilla/5.0 (Windows; N; WinNT4.0; en-US; m14) Netscape6/6.0b1 X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker Cc: Doug Barton , Christopher Masto , Nick Hibma , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? References: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > = > On Thu, 6 Apr 2000, Doug Barton wrote: > = > > Christopher Masto wrote: > > > = > > > On Mon, Apr 03, 2000 at 10:52:13AM +0100, Nick Hibma wrote: > > > > Are there actually any good reasons why we _should_ upgrade in th= e first > > > > place? > > > = > > > Of course. We now have an obsolete version of Perl. That should b= e > > > reason enough to upgrade. > > = > > You haven't given a sufficiently compelling definition of "obsolete"= > > yet. I think that what people are really asking is, "What does this n= ew > > perl get us that we don't already have?" Once we've answered that, th= en > > we can balance the benefits against the costs (which are pretty high,= > > considering the complexity of integrating perl into the berkeley make= > > environment) and then we can try and apply those arguments in the sea= rch > > for someone who is willing and able to do the work. = > = > My experiences with perl tend to be that as soon as a new release comes= > out, all the module maintainers tend to adopt it as standard and start = to > deprecate the older versions. I'm not saying that this is an overnight= > sort of thing, but it does pose a problem ... > = > My stupid question, though, is why is this such a big issue? Would it = be > too hard to extend our /usr/src build process so that it is smart enoug= h > to do an install out of ports, and just build the ports version of 5.6.= 0, > vs trying to integrate it into our build tree? Create a symlink to > /usr/ports/devel/perl560 so that when it cd's to the perl directory and= > does a 'make', it builds that? Whoah!=A0 That would mean that I'd have to install the ports tree on ever= y = machine I intend to build world on..=A0 That's just not acceptable to me.= =A0 = The source tree should remain independant to external sources. Regards, Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 5:50: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 2372F37BC10 for ; Thu, 6 Apr 2000 05:49:55 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup8-13.iptelecom.net.ua [212.9.227.205]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA13973; Thu, 6 Apr 2000 15:56:26 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id PAA00426; Thu, 6 Apr 2000 15:49:08 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EC87C2.EE98B58D@altavista.net> Date: Thu, 06 Apr 2000 15:49:06 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Soren Schmidt , Jon Hamilton , current@FreeBSD.ORG Subject: Re: [SOLVED] Dangerously looking glitch (4.0-STABLE) References: <200004051431.QAA47392@freebsd.dk> <38EC3C14.2471F70@altavista.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all who replied - problem has been solved by replacing long-served P100 with newest K6-200. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 6:36:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 0D0B037BB75 for ; Thu, 6 Apr 2000 06:36:14 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id JAA12430; Thu, 6 Apr 2000 09:35:55 -0400 (EDT) Date: Thu, 6 Apr 2000 09:35:55 -0400 (EDT) From: "Matthew N. Dodd" To: "Eric D. Futch" Cc: Brooks Davis , Stephan van Beerschoten , current@FreeBSD.ORG Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Apr 2000, Eric D. Futch wrote: > Ok.. I figured I'd take this on on my way to getting more comfy with > FreeBSD. Check out my patch and let me know how far I've gone off the > deep end :) > > http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch > > Unfortunately I do not have the acutal card to test this patch. It did > survive a buildkernel, so I'm just assuming that I'm not that far off. I've actually ignored the 'vx' driver since its functionality will be folded into the 'ep' driver at some point in the future. I'm not sure its worth messing with it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 6:41:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id E9A0237BB1C for ; Thu, 6 Apr 2000 06:41:51 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 8105925230; Thu, 6 Apr 2000 09:41:51 -0400 (EDT) Received: by osaka.louisville.edu (Postfix, from userid 15) id 0022218605; Thu, 6 Apr 2000 09:41:50 -0400 (EDT) Date: Thu, 6 Apr 2000 09:41:50 -0400 From: Keith Stevenson To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: Perl 5.6.0? Message-ID: <20000406094150.B34220@osaka.louisville.edu> References: <38EC443F.C1503735@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from scrappy@hub.org on Thu, Apr 06, 2000 at 09:24:06AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (cc-list pruned) On Thu, Apr 06, 2000 at 09:24:06AM -0300, The Hermit Hacker wrote: > > My stupid question, though, is why is this such a big issue? Would it be > too hard to extend our /usr/src build process so that it is smart enough > to do an install out of ports, and just build the ports version of 5.6.0, > vs trying to integrate it into our build tree? Create a symlink to > /usr/ports/devel/perl560 so that when it cd's to the perl directory and > does a 'make', it builds that? Take a look at perl's build process. After you are done, take a look at how Mark M. mangled it to make it fit nicely into FreeBSD's buildworld process. After your eyes uncross, you'll understand why no one is falling all over themselves to tackle the issue. It's not trivial. Parts of the core OS depend on perl. Making those parts depend on a port is unacceptable. Importing a new version of perl, ESPECIALLY a version which is not 100% backwards compatible with the one currently in the tree is a delicate process. Unfortunately, perl's build process makes it much harder than it should. If you need the new functionality, install the port. I have every confidence that perl 5.6.x will eventually be imported into the tree. Now is a bit too soon though. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 8:18:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 8B0F637C069 for ; Thu, 6 Apr 2000 08:18:50 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12dE3E-0004Wj-0B; Thu, 6 Apr 2000 15:18:35 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id QAA97319; Thu, 6 Apr 2000 16:21:09 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Thu, 6 Apr 2000 16:15:24 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Eric D. Futch" Cc: Brooks Davis , current@freebsd.org Subject: Re: dev/vx/if_vx_pci.c 5.0-CURRENT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You really want to look at other drivers, how they have been done. When you are done, send me the diff and I will have a look at it. It is fairly straightforward to convert from one to the other, once you have understood both concepts a bit. Nick On Wed, 5 Apr 2000, Eric D. Futch wrote: > I figured it would take more work than I put into it. It was just a shot > in the dark. I think I have one of these cars in my Linux box at home > which I wouldn't mind ripping out and sticking in this machine. Let me > know if it's still worth me poking around in, or if you're going ahead > with the rewrite. I'm gonna keep playing with it out of my own > interest on newbusifying things. Maybe once I get a bigger clue of what > has to be done, I'll see about newbusifying other things. I always have > all this extra time on my hands :) > > -- > Eric Futch New York Connect.Net, Ltd. > efutch@nyct.net Technical Support Staff > http://www.nyct.net (212) 293-2620 > "Bringing New York The Internet Access It Deserves" > > > On Wed, 5 Apr 2000, Brooks Davis wrote: > > >On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote: > > > >I think if you install the kernel and reboot it will likely explode in > >probe. It takes more then just new structs. The function signatures > >have changed as well. Take a look at rev 1.67 of src/sys/pci/if_fxp.c > >to see what newbus conversion takes. I'm taking a wack at a rewrite, > >but like you I don't have a card, so testing will be kinda trickey. > > > >-- Brooks > > > >-- > >Any statement of the form "X is the one, true Y" is FALSE. > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 8:28:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 8562537C020 for ; Thu, 6 Apr 2000 08:28:38 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e36FSYp25572; Thu, 6 Apr 2000 11:28:34 -0400 (EDT) Date: Thu, 6 Apr 2000 11:28:33 -0400 (EDT) From: Trevor Johnson To: Soren Schmidt Cc: freebsd-current@freebsd.org Subject: trouble with burncd on FreeBSD-CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings. I'm getting errors when I use burncd, and I'm hoping you may have insight into them. Both burncd and the kernel were compiled from sources cvsupped at around 11:27 UTC 2000-04-06. While burncd seems to be able to blank a CD-RW disk and to write data onto it, there is always a failure around the time it does the "fixate" operation. Afterward, I cannot eject the disk by pressing the eject button on the drive, until rebooting the computer. Under FreeBSD 3.4, I was able to use wormcontrol with no trouble. My kernel configuration file has these options: # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices I have similar problems without ATA_ENABLE_ATAPI_DMA. I also had similar problems when I had the CD-RW drive slaved to the 84000A6 hard disk. Here's a typical attempt: # burncd -s 2 -f /dev/acd0c blank Apr 6 16:13:28 ws99 /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 Apr 6 16:13:28 ws99 /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 blanking CD, please wait.. # Apr 6 16:14:58 ws99 /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 Apr 6 16:14:58 ws99 /kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 # time burncd -s 2 -f /dev/acd0c data test.iso fixate next writeable LBA 0 writing from file test.iso size 360 KB written this track 360 KB (100%) total 360 KB fixating CD, please wait.. burncd: ioctl(CDRIOCCLOSEDISK): Input/output error Apr 6 16:15:30 ws99 /kernel: acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 0.0u 0.0s 0:00.87 0.0% 0+0k 8+0io 0pf+0w Apr 6 16:15:30 ws99 /kernel: acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 # Apr 6 16:15:30 ws99 /kernel: acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 Apr 6 16:15:30 ws99 /kernel: acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 Here's an example of the dmesg output: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Apr 6 14:33:41 BST 2000 root@ws99.localdomain:/usr/src/sys/compile/FREEBASE50a Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (411.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183f9ff real memory = 134152192 (131008K bytes) config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config> aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> q avail memory = 127016960 (124040K bytes) Preloaded elf kernel "kernel" at 0xc035d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc035d09c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 2.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 2.2 irq 11 chip1: port 0x5000-0x500f at device 2.3 on pci0 pci0: at 13.0 irq 7 ed0: port 0xe400-0xe41f irq 3 at device 15. 0 on pci0 ed0: supplying EUI64: 00:40:05:ff:fe:39:7d:e0 ed0: address 00:40:05:39:7d:e0, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. pca0 at port 0x40 on isa0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown1: at port 0x620-0x623 on isa0 unknown2: at port 0x200-0x207 on isa0 unknown3: at port 0x100 on isa0 ad0: 6149MB [12495/16/63] at ata0-master using UDMA33 ad1: 3820MB [7763/16/63] at ata0-slave using WDMA2 acd0: CD-RW at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s1a ed0: starting DAD for fe80:0001::0240:05ff:fe39:7de0 ed0: DAD complete for fe80:0001::0240:05ff:fe39:7de0 - no duplicates found WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=04 acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 __ Trevor Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 8:38:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 78E9B37C074 for ; Thu, 6 Apr 2000 08:38:18 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 12dEMK-000KSW-00; Thu, 6 Apr 2000 16:38:16 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id QAA30021 for current@freebsd.org; Thu, 6 Apr 2000 16:38:15 +0100 (BST) (envelope-from jcm) Date: Thu, 6 Apr 2000 16:38:15 +0100 From: J McKitrick To: current@freebsd.org Subject: bad memory patch? Message-ID: <20000406163815.A29984@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw this link recently... http://home.zonnet.nl/vanrein/badram/ Apparently, you make a floppy with the supplied image, boot with it to find the bad RAM addresses, and then those addresses are passed on as a kernel parameter once the patch is applied. Bad addresses will be excluded from addressable/virtual memory from then on. Sounds like sometheing we could use, eh? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org To Microsoft: "Your tyranny I was part of, is now cracking on every side. Now your own life is in danger. Your Empire is on fire." Front 242 ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 10:14:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 2C9E437C02C for ; Thu, 6 Apr 2000 10:14:39 -0700 (PDT) (envelope-from marcel@cup.hp.com) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 7F7102DB; Thu, 6 Apr 2000 10:14:38 -0700 (PDT) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0.1) id KAA15213; Thu, 6 Apr 2000 10:14:34 -0700 (PDT) Message-ID: <38ECC5FB.5A47A057@cup.hp.com> Date: Thu, 06 Apr 2000 10:14:35 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey Cc: Yu Guo/PEK/Lotus , "Andrzej Bialecki , freebsd-current Subject: Re: Installworld to /some/where/... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Thu, 6 Apr 2000, Yu Guo/PEK/Lotus wrote: > > > > > Just do a > > make DESTDIR=/mnt/installdir installworld > > > > Or remotely mount /usr/obj and /usr/src, and do 15 make installworlds on > 15 machines. In fact, I'm not totally sure that first method works, > because I think that perl, at least, records the name of DESTDIR during > the 'make buildworld' so moving DESTDIR only in installworld, that might > bomb later when you ran it. > > In fact, I think that will happen, and to cc1 (of gcc) also, because the > 'specs' get set during buildworld, don't they? Yes. > The above would only be safe, I think, if you did the make buildworld with > the same DESTDIR. Anyone know if that's true? Yes, and it's not true :-) DESTDIR is overloaded. It is reassigned during a buildworld for internal purposes. There's only a very limited way (ie for a very limited set of tools) to specify during build where they will end up and where they can expect data files. In all other cases it is assumed that the programs are run from the normal place. -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 10:58: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E52A37BAF9 for ; Thu, 6 Apr 2000 10:58:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA89372; Thu, 6 Apr 2000 10:57:58 -0700 (PDT) (envelope-from dillon) Date: Thu, 6 Apr 2000 10:57:58 -0700 (PDT) From: Matthew Dillon Message-Id: <200004061757.KAA89372@apollo.backplane.com> To: Alfred Perlstein Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c References: <200004021752.KAA13175@freefall.freebsd.org> <20000402163552.P21029@fw.wintelcom.net> <200004022312.QAA51299@apollo.backplane.com> <20000402164700.R21029@fw.wintelcom.net> <200004022338.QAA51565@apollo.backplane.com> <20000402172349.T21029@fw.wintelcom.net> <20000404100911.C53037@freebie.lemis.com> <20000405111950.F20770@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The version of Linux kernel source that I have uses the first: : :asmlinkage long sys_getppid(void) :{ : int pid; : struct task_struct * me = current; : struct task_struct * parent; : : parent = me->p_opptr; : for (;;) { : pid = parent->pid; :#if __SMP__ :{ : struct task_struct *old = parent; : mb(); : parent = me->p_opptr; : if (old != parent) : continue; :} :#endif : break; : } : return pid; :} : :I like it. mb() is most certainly a "memory barrier" inline to :force ordering constraints. interesting how they don't use :volatile for the pointer though: mb() just prevents the compiler from optimizing access to the structural fields (otherwise it might move the accesses outside the for() loop and you would get an infinite loop. From the compiler's point of view, mb() is a subroutine call (I assume in the headers it's a volatile __asm). We can either use an mb() type of thing, or we can declare the structural field volatile, or we can cast the access to be volatile. : /* : * pointers to (original) parent process, youngest child, younger sibling, : * older sibling, respectively. (p->father can be replaced with : * p->p_pptr->pid) : */ : struct task_struct *p_opptr, *p_pptr, *p_cptr, *p_ysptr, *p_osptr; : :I prefer this method, we can't copy _everything_ into the child struct :so we might as well do it this way. : :Feeling lazy, i'm wondering if we have the equivenlant of a mb() :macro/inline we'll need one. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 11:11:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E179537C06F for ; Thu, 6 Apr 2000 11:11:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01450 for ; Thu, 6 Apr 2000 11:13:04 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: Snapshot building machines back on line. Date: Thu, 06 Apr 2000 11:13:04 -0700 Message-ID: <1447.955044784@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the latest 4.0-STABLE snapshots: ftp://releng4.freebsd.org/pub/FreeBSD For the latest 5.0-CURRENT snapshots: ftp://current.freebsd.org/pub/FreeBSD I don't run mirrors of these machines so please don't ask where you can get the bits closer/faster/cheaper/etc. If you want to mirror the contents yourself and put them up for anonymous FTP, feel free. :) I also don't have ISO images up for the snapshots on the site because they're generally too big to make frequently. I may make snapshot ISOs available on certain "milestone" dates at my discretion, but there aren't any of those coming up for awhile yet. Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 11:33:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from acc0.visti.net (acc0.visti.net [195.64.225.233]) by hub.freebsd.org (Postfix) with ESMTP id 36F0F37B83C for ; Thu, 6 Apr 2000 11:33:36 -0700 (PDT) (envelope-from amb@visti.net) Received: from office.visti.net (office.visti.net [195.64.225.183]) by acc0.visti.net (8.8.8-Elvisti-980428/8.8.8) with ESMTP id VAA04006; Thu, 6 Apr 2000 21:33:23 +0300 (EEST) Received: from gw.visti.net (gw0-dos.visti.net [195.64.225.161]) by office.visti.net (8.6.12/8.ElVisti) with ESMTP id VAA18988; Thu, 6 Apr 2000 21:33:22 +0300 Received: from visti.net (pinta.visti.net [195.64.225.241]) by gw.visti.net (8.9.3/8.9.3) with ESMTP id VAA03306; Thu, 6 Apr 2000 21:33:16 +0300 (EEST) Message-ID: <38ECD86B.514DE599@visti.net> Date: Thu, 06 Apr 2000 21:33:16 +0300 From: Andrei Biryukov Organization: Elvisti X-Mailer: Mozilla 4.72 [ru] (X11; I; FreeBSD 3.3-19991102-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Snapshot building machines back on line. References: <1447.955044784@zippy.cdrom.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > For the latest 4.0-STABLE snapshots: > ftp://releng4.freebsd.org/pub/FreeBSD Unfortunately does not work ... root[amb]@pinta# nslookup releng4.freebsd.org. who.cdrom.com Server: who.cdrom.com Address: 204.216.27.3 *** who.cdrom.com can't find releng4.freebsd.org.: Non-existent host/domain -- âÉÒÀËÏ× áÎÄÒÅÊ IC ElVisti E-mail amb@visti.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 12: 9: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 9FDD137BAF5 for ; Thu, 6 Apr 2000 12:08:50 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.hiwaay.net (8.10.0/8.10.0) with ESMTP id e36J8jR13275; Thu, 6 Apr 2000 14:08:45 -0500 (CDT) Date: Thu, 6 Apr 2000 14:08:45 -0500 (CDT) From: Steve Price To: Nate Williams Cc: Daniel Eischen , current@FreeBSD.ORG Subject: Re: signal mask from jmp_buf In-Reply-To: <200004050423.WAA12987@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 4 Apr 2000, Nate Williams wrote: # > I am unfamiliar with the JDK port. Does it use FreeBSD native # > threads? # # Nope, see above. If/when FreeBSD gets 'real' kernel threads, it would # be worthwhile to move it to using them, but until that team my suspicion # is the optimzed 'threads' library that is part of the JDK probably is an # easier solution for the JDK. However, Steve may have a different # opinion. :) Actually I was just looking into cleaning the code up a bit and getting it to work on -current again. The version that I compiled many moons ago just coredumps when trying to bootstrap JDK2 builds on -current and I think it has to do with the signals changes. I would like to get a 'real' kernel threads implementation going but it seems that it would be a -current only thing for some time to come, so it might not be worth the effort at this point. At least I don't think I have the energy for it at the moment - too many other interesting projects going on right now. :) Thanks. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 12:26:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BDAC437B926; Thu, 6 Apr 2000 12:26:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA76532; Thu, 6 Apr 2000 12:26:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 6 Apr 2000 12:26:22 -0700 (PDT) From: Kris Kennaway To: J McKitrick Cc: current@freebsd.org Subject: Re: bad memory patch? In-Reply-To: <20000406163815.A29984@dogma.freebsd-uk.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, J McKitrick wrote: > I saw this link recently... > > http://home.zonnet.nl/vanrein/badram/ > > Apparently, you make a floppy with the supplied image, boot with it to > find the bad RAM addresses, and then those addresses are passed on as a > kernel parameter once the patch is applied. Bad addresses will be excluded > from addressable/virtual memory from then on. > > Sounds like sometheing we could use, eh? It's not possible to find bad RAM deterministically from software..if you have bad RAM, you need to replace it, end of story. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 12:48:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E23CD37BB59 for ; Thu, 6 Apr 2000 12:48:19 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01760; Thu, 6 Apr 2000 12:49:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Andrei Biryukov Cc: current@FreeBSD.ORG Subject: Re: Snapshot building machines back on line. In-reply-to: Your message of "Thu, 06 Apr 2000 21:33:16 +0300." <38ECD86B.514DE599@visti.net> Date: Thu, 06 Apr 2000 12:49:38 -0700 Message-ID: <1757.955050578@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try again, the DNS wasn't updated yet. > "Jordan K. Hubbard" wrote: > > > > For the latest 4.0-STABLE snapshots: > > ftp://releng4.freebsd.org/pub/FreeBSD > > Unfortunately does not work ... > > root[amb]@pinta# nslookup releng4.freebsd.org. who.cdrom.com > Server: who.cdrom.com > Address: 204.216.27.3 > > *** who.cdrom.com can't find releng4.freebsd.org.: Non-existent > host/domain > > > -- > âÉÒÀËÏ× áÎÄÒÅÊ IC ElVisti > E-mail amb@visti.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 13:39:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id DD1FE37B762 for ; Thu, 6 Apr 2000 13:39:27 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA183636; Thu, 6 Apr 2000 16:39:19 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <1447.955044784@zippy.cdrom.com> References: <1447.955044784@zippy.cdrom.com> Date: Thu, 6 Apr 2000 16:39:11 -0400 To: "Jordan K. Hubbard" , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Snapshot building machines back on line. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:13 AM -0700 4/6/00, Jordan K. Hubbard wrote: >For the latest 4.0-STABLE snapshots: > ftp://releng4.freebsd.org/pub/FreeBSD > I can get to the above machine just fine, but it does not seem to let me use anonymous-ftp login's... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 13:52: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CF6C937BC7C for ; Thu, 6 Apr 2000 13:51:58 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA02208; Thu, 6 Apr 2000 13:53:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Garance A Drosihn Cc: current@FreeBSD.ORG Subject: Re: Snapshot building machines back on line. In-reply-to: Your message of "Thu, 06 Apr 2000 16:39:11 EDT." Date: Thu, 06 Apr 2000 13:53:21 -0700 Message-ID: <2205.955054401@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's very odd - the exact same wu-ftpd installation (same version, same ~ftp setup and permissions, everything) I have on current.freebsd.org (usw2) just Does Not Work on releng4.freebsd.org (usw3). Argh. In the meantime, I've switched over to the stock ftp on that machine so things work, though so much for `get foo.tar' working over on that box at the moment either. - Jordan > At 11:13 AM -0700 4/6/00, Jordan K. Hubbard wrote: > >For the latest 4.0-STABLE snapshots: > > ftp://releng4.freebsd.org/pub/FreeBSD > > > > I can get to the above machine just fine, but it does not seem > to let me use anonymous-ftp login's... > > > --- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or drosih@rpi.edu > Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 16: 3:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id D869E37BB91 for ; Thu, 6 Apr 2000 16:03:23 -0700 (PDT) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id IAA25452; Fri, 7 Apr 2000 08:03:21 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma025384; Fri, 7 Apr 00 08:03:08 +0900 Received: from jkpc15.tk.kubota.co.jp ([192.168.7.250]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id IAA01004; Fri, 7 Apr 2000 08:03:07 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-02/21/99) with ESMTP id XAA23081; Thu, 6 Apr 2000 23:21:24 +0900 (JST) To: Yoshinobu Inoue , current@FreeBSD.ORG Cc: haro@tk.kubota.co.jp Subject: Re: 75 second delay using telnet/ssh (ipv6 related) In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000406232123B.haro@tk.kubota.co.jp> Date: Thu, 06 Apr 2000 23:21:23 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Thu, 06 Apr 2000 12:53:44 +0900 From: Yoshinobu Inoue :: ::> > > > Sorry for the inconvenience and I'll try the fix. ::> > > ::> > > Sorry to be late, but I tried resolver fix and it seems to work. ::> > > This should remove such 75 seconds delay in apps which use ::> > > getaddrinfo(). ::I did a little bit cleanup, and made new patches. ::(with no behaviour change) ::I already received several positive confirmations for the ::patches. :: ::I'll wait more several days and will commit this if no ::significant problem is found for this. Hello Inoue-san, I'm using fetchmail, from the ports, and it seems to choke while trying forward mail to local sendmail. I've tried your previous patch, but did not seem to help. The problem may be with fetchmail or sendmail, but cannot figure out. If you need more information, please send me a mail, in Japanese. :-) Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Office of Business Planning & Development, Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@tk.kubota.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 16:11:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 6BC9937C20A for ; Thu, 6 Apr 2000 16:11:17 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id TAA85325 for freebsd-current@FreeBSD.ORG; Thu, 6 Apr 2000 19:11:16 -0400 (EDT) (envelope-from ak03) 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: <38EC86C5.6010206@spcgroup.nl> Date: Thu, 06 Apr 2000 19:11:10 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: FreeBSD-Current Subject: Re: Perl 5.6.0? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's source tree already. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 17:38:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66]) by hub.freebsd.org (Postfix) with ESMTP id 8966037B7C0 for ; Thu, 6 Apr 2000 17:38:46 -0700 (PDT) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id UAA60104; Thu, 6 Apr 2000 20:19:22 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id UAA08904; Thu, 6 Apr 2000 20:19:21 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: jcm@freebsd-uk.eu.org (J McKitrick) Cc: current@freebsd.org Subject: Re: bad memory patch? Date: Fri, 07 Apr 2000 00:16:45 GMT Message-ID: <38ed282a.168335243@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Apr 2000 11:44:52 -0400, in sentex.lists.freebsd.current you wrote: >Apparently, you make a floppy with the supplied image, boot with it to >find the bad RAM addresses, and then those addresses are passed on as a >kernel parameter once the patch is applied. Bad addresses will be excluded >from addressable/virtual memory from then on. > >Sounds like sometheing we could use, eh? It sounds like a recipe for disaster. You cannot determine with any degree of reasonable certainty via software if RAM is bad. For such a critical component, I cant imagine anyone wanting to take such a chance. It would be bad enough even on a personal workstation, let alone a server. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 18: 1:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from tesla.salk.edu (tesla.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id 3392537B918; Thu, 6 Apr 2000 18:01:17 -0700 (PDT) (envelope-from jorge@salk.edu) Received: from merckx.salk.edu (merckx.salk.edu [198.202.70.90]) by tesla.salk.edu (8.7.5/8.7.3) with ESMTP id SAA13040; Thu, 6 Apr 2000 18:01:14 -0700 (PDT) Date: Thu, 6 Apr 2000 18:01:12 -0700 (PDT) From: Jorge Aldana To: current@freebsd.org, stable@freebsd.org Cc: Paul Ganter , Jorge Aldana Subject: 3Com NIC PC-Card on 4.0-20000317-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On attempting to insert a 3Com Fast Ethernet PC-Card on an Isperion Dell portable with FreeBSD 4.0-Stable I get the following from pccardd when I insert my pc-card: No card in database for ""("") It does not identify it, has anyone seen this problem or know of a solution? I've copied the sample pccard.conf.sample to pccard.conf and started pccardd, I even added a "device 0x1 "ep0" 10" to the kernal config file as suggested in a previous attempt by someone to fix this, still same result. Also, added PC-Card support in the kernel, the network dongle LED's turn on but for both 10 and 100 base-t. Can anyone help! Jorge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 18:37:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (Postfix) with ESMTP id 1EDAF37BEED; Thu, 6 Apr 2000 18:37:16 -0700 (PDT) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id LAA06432; Fri, 7 Apr 2000 11:40:05 +1000 (EST) Message-ID: <38ED3A9A.748A@natsoft.com.au> Date: Fri, 07 Apr 2000 11:32:10 +1000 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Jorge Aldana Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, Paul Ganter Subject: Re: 3Com NIC PC-Card on 4.0-20000317-STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this problem with a Compaq Armada E700. The problem was due to the default memory address of 0xd0000, pccardd found the PCMIA card after changing the pccard_mem="DEFAULT" to pccard_mem="0xd4000" in rc.conf For some reason the system did not like the default of 0xd0000 I hope this helps. Craig Wilson National Software Pty Ltd Jorge Aldana wrote: > > On attempting to insert a 3Com Fast Ethernet PC-Card on an Isperion Dell > portable with FreeBSD 4.0-Stable I get the following from pccardd when I > insert my pc-card: > > No card in database for ""("") > > It does not identify it, has anyone seen this problem or know of a > solution? > I've copied the sample pccard.conf.sample to pccard.conf and started > pccardd, I even added a "device 0x1 "ep0" 10" to the kernal config file as > suggested in a previous attempt by someone to fix this, still same > result. Also, added PC-Card support in the kernel, the network dongle > LED's turn on but for both 10 and 100 base-t. > > Can anyone help! > > Jorge > > 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-current" in the body of the message From owner-freebsd-current Thu Apr 6 19:53:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E110E37BC04 for ; Thu, 6 Apr 2000 19:53:25 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id WAA24127 for ; Thu, 6 Apr 2000 22:53:25 -0400 (EDT) Date: Thu, 6 Apr 2000 22:53:24 -0400 (EDT) From: "Matthew N. Dodd" To: current@freebsd.org Subject: All PCI DPT adapter users! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just updated the DPT PCI front end to be 'newbus' compliant but lack the hardware to test my changes. It should work just fine but I'd appriciate a quick 'it works!' from someone with hardware just to be sure. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 19:54:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from tesla.salk.edu (tesla.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A0B437C208; Thu, 6 Apr 2000 19:54:49 -0700 (PDT) (envelope-from jorge@salk.edu) Received: from merckx.salk.edu (merckx.salk.edu [198.202.70.90]) by tesla.salk.edu (8.7.5/8.7.3) with ESMTP id TAA17187; Thu, 6 Apr 2000 19:54:35 -0700 (PDT) Date: Thu, 6 Apr 2000 19:54:34 -0700 (PDT) From: Jorge Aldana To: Craig Wilson Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, Paul Ganter Subject: Re: 3Com NIC PC-Card on 4.0-20000317-STABLE In-Reply-To: <38ED3A9A.748A@natsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No luck, with the pccard_mem option in rc.conf, we still get the "","" identification. Jorge On Fri, 7 Apr 2000, Craig Wilson wrote: > I had this problem with a Compaq Armada E700. > The problem was due to the default memory address of 0xd0000, > pccardd found the PCMIA card after changing the > pccard_mem="DEFAULT" to pccard_mem="0xd4000" in rc.conf > For some reason the system did not like the default of 0xd0000 > > I hope this helps. > > Craig Wilson > National Software Pty Ltd > > Jorge Aldana wrote: > > > > On attempting to insert a 3Com Fast Ethernet PC-Card on an Isperion Dell > > portable with FreeBSD 4.0-Stable I get the following from pccardd when I > > insert my pc-card: > > > > No card in database for ""("") > > > > It does not identify it, has anyone seen this problem or know of a > > solution? > > I've copied the sample pccard.conf.sample to pccard.conf and started > > pccardd, I even added a "device 0x1 "ep0" 10" to the kernal config file as > > suggested in a previous attempt by someone to fix this, still same > > result. Also, added PC-Card support in the kernel, the network dongle > > LED's turn on but for both 10 and 100 base-t. > > > > Can anyone help! > > > > Jorge > > > > 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-current" in the body of the message From owner-freebsd-current Thu Apr 6 20: 7:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CE5AB37B62A; Thu, 6 Apr 2000 20:07:37 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA04020; Thu, 6 Apr 2000 21:06:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA95791; Thu, 6 Apr 2000 21:05:57 -0600 (MDT) Message-Id: <200004070305.VAA95791@harmony.village.org> To: Jorge Aldana Subject: Re: 3Com NIC PC-Card on 4.0-20000317-STABLE Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, Paul Ganter In-reply-to: Your message of "Thu, 06 Apr 2000 18:01:12 PDT." References: Date: Thu, 06 Apr 2000 21:05:57 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jorge Aldana writes: : On attempting to insert a 3Com Fast Ethernet PC-Card on an Isperion Dell : portable with FreeBSD 4.0-Stable I get the following from pccardd when I : insert my pc-card: What kind of card is this? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 20: 7:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 78AD237BFF1; Thu, 6 Apr 2000 20:07:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA04025; Thu, 6 Apr 2000 21:07:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA95804; Thu, 6 Apr 2000 21:06:44 -0600 (MDT) Message-Id: <200004070306.VAA95804@harmony.village.org> To: Jorge Aldana Subject: Re: 3Com NIC PC-Card on 4.0-20000317-STABLE Cc: Craig Wilson , current@FreeBSD.ORG, stable@FreeBSD.ORG, Paul Ganter In-reply-to: Your message of "Thu, 06 Apr 2000 19:54:34 PDT." References: Date: Thu, 06 Apr 2000 21:06:44 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jorge Aldana writes: : No luck, with the pccard_mem option in rc.conf, we still get the "","" : identification. What's the card number? Is it the 574 or 575? The 574 works, while the 575 is cardbus and thus not supported yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 20:48:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 6772037C030 for ; Thu, 6 Apr 2000 20:48:34 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual.pacbell.net (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id UAA00252; Thu, 6 Apr 2000 20:48:21 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.3.1.2.20000406203931.00b826b0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 06 Apr 2000 20:48:21 -0700 To: "Matthew N. Dodd" , current@FreeBSD.ORG From: Manfred Antar Subject: Re: All PCI DPT adapter users! In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:53 PM 4/6/2000 -0400, Matthew N. Dodd wrote: >I've just updated the DPT PCI front end to be 'newbus' compliant but lack >the hardware to test my changes. It should work just fine but I'd >appriciate a quick 'it works!' from someone with hardware just to be sure. It hangs here :( the boot gets to: dpt0 port 0xff80-0xff9f irq 16 at device11.0 on pci0 and just stalls. The controller is a DPT PM2124 with 2 4gig seagate drives in a RAID 1 setup. The motherboard is an Intel PR440FX Dual pentium pro with 2 200mhz cpu's I can't get to the debugger it just freezes. I removed the line options COMPAT_OLDPCI from my config file before I built the kernel that doesn't work Here is what comes up an my old kernel: dpt0: port 0xff80-0xff9f irq 16 at device 11.0 on pci0 dpt0: DPT PM2124A/9X-R FW Rev. 07CK, 1 channel, 64 CCBs dpt0: driver is using old-style compatability shims Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 21:21:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3BCC737BD57; Thu, 6 Apr 2000 21:21:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA25898; Thu, 6 Apr 2000 21:21:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 6 Apr 2000 21:21:12 -0700 (PDT) From: Kris Kennaway To: "Alexander N. Kabaev" Cc: FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Alexander N. Kabaev wrote: > According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's source > tree already. OpenBSD don't even try to make their "bundled software" comply with the rest of the system build architecture - they basically just import the perl distribution into gnu/usr.bin/, munge some of the build bits, and let the software build the way it wants to. Needless to say, thats not an acceptable style for FreeBSD, not to mention probably breaking certain features we support such as cross-compilation :-) Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 21:24:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 59D5337B992 for ; Thu, 6 Apr 2000 21:24:20 -0700 (PDT) (envelope-from mantar@pacbell.net) Received: from dual.pacbell.net (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id VAA00289; Thu, 6 Apr 2000 21:24:17 -0700 (PDT) (envelope-from mantar@pacbell.net) Message-Id: <4.3.1.2.20000406212245.00b88718@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 06 Apr 2000 21:24:16 -0700 To: "Matthew N. Dodd" , current@FreeBSD.ORG From: Manfred Antar Subject: Re: All PCI DPT adapter users! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:53 PM 4/6/2000 -0400, Matthew N. Dodd wrote: >I've just updated the DPT PCI front end to be 'newbus' compliant but lack >the hardware to test my changes. It should work just fine but I'd >appriciate a quick 'it works!' from someone with hardware just to be sure. It hangs here :( the boot gets to: dpt0 port 0xff80-0xff9f irq 16 at device11.0 on pci0 and just stalls. The controller is a DPT PM2124 with 2 4gig seagate drives in a RAID 1 setup. The motherboard is an Intel PR440FX Dual pentium pro with 2 200mhz cpu's I can't get to the debugger it just freezes. I removed the line options COMPAT_OLDPCI from my config file before I built the kernel that doesn't work Here is what comes up an my old kernel: dpt0: port 0xff80-0xff9f irq 16 at device 11.0 on pci0 dpt0: DPT PM2124A/9X-R FW Rev. 07CK, 1 channel, 64 CCBs dpt0: driver is using old-style compatability shims Manfred As a footnote A new kernel with: options COMPAT_OLDPCI does the same thing -- freezes. ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 21:57:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from msk1.mail.ru (mx1.mail.ru [194.67.23.32]) by hub.freebsd.org (Postfix) with ESMTP id 3450737B83F; Thu, 6 Apr 2000 21:57:41 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by msk1.mail.ru with esmtp (Exim 3.02 #173) id 12dQwW-000KUe-00; Fri, 07 Apr 2000 09:04:28 +0400 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id AAA00420; Fri, 7 Apr 2000 00:57:17 -0400 (EDT) (envelope-from kan) 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: Fri, 07 Apr 2000 00:57:16 -0400 (EDT) From: "Alexander N. Kabaev" To: Kris Kennaway Subject: Re: Perl 5.6.0? Cc: FreeBSD-Current , "Alexander N. Kabaev" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am perfectly aware of the way OpenBSD builds contrib software. I am just making a point that they have found perl 5.6.0 is stable enough to be included into their OS. On 07-Apr-00 Kris Kennaway wrote: > On Thu, 6 Apr 2000, Alexander N. Kabaev wrote: > >> According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's >> source >> tree already. > > OpenBSD don't even try to make their "bundled software" comply with the > rest of the system build architecture - they basically just import the > perl distribution into gnu/usr.bin/, munge some of the build bits, and let > the software build the way it wants to. Needless to say, thats not an > acceptable style for FreeBSD, not to mention probably breaking certain > features we support such as cross-compilation :-) > > Kris > > ---- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Apr-00 Time: 00:51:49 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 22:29:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B4DB737BF8F for ; Thu, 6 Apr 2000 22:29:27 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id AAA04120 for freebsd-current@freebsd.org; Fri, 7 Apr 2000 00:29:22 -0500 (CDT) Date: Fri, 7 Apr 2000 00:29:22 -0500 (CDT) From: Mohit Aron Message-Id: <200004070529.AAA04120@cs.rice.edu> To: freebsd-current@freebsd.org Subject: error reports by rshd in /var/log/messages Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using FreeBSD-4.0-RELEASE on a Xeon processor. The following messages have been appearing in my /var/log/messages file apparently upon an rlogin to the machine: Apr 7 00:23:16 idli rshd[236]: no modules loaded for `rshd' service Apr 7 00:23:16 idli rshd[236]: auth_pam: Permission denied Apr 7 00:23:16 idli rshd[236]: PAM authentication failed Can someone suggest if there's anything that needs fixing in the system. Thanks, - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 22:53:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id BFA9B37C278 for ; Thu, 6 Apr 2000 22:53:10 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 12dRhY-0003hj-00; Thu, 6 Apr 2000 22:53:05 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.1b+Sun/8.9.1) with SMTP id WAA18351; Thu, 6 Apr 2000 22:52:59 -0700 (PDT) Date: Thu, 6 Apr 2000 22:52:58 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: Perl 5.6.0? To: Brad Knowles Cc: "Jeroen C. van Gelderen" , Nick Hibma , Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3-Apr-00 at 10:09, Brad Knowles (blk@skynet.be) wrote: > At 11:59 AM -0400 2000/4/3, Jeroen C. van Gelderen wrote: > > > PERL is not just used by the FreeBSD system, it's also used by many > > applications ran on top of FreeBSD. Those applications are more likely > > to require an up-to-date version of PERL. We for one need the (overly > > late) 64-bit support in PERL. > > MMMkay. Try this: cd /usr/ports/lang/perl && make install ===> perl5.00502 is forbidden. perl is in system. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 22:53:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 7A47337C271 for ; Thu, 6 Apr 2000 22:53:12 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 12dRhd-0003hl-00; Thu, 6 Apr 2000 22:53:10 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.1b+Sun/8.9.1) with SMTP id WAA18355; Thu, 6 Apr 2000 22:53:07 -0700 (PDT) Date: Thu, 6 Apr 2000 22:53:07 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: Perl 5.6.0? To: Nick Hibma Cc: Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3-Apr-00 at 02:56, Nick Hibma (n_hibma@calcaphon.com) wrote: > > Are there actually any good reasons why we _should_ upgrade in the first > place? Security fixes, added functionality we require, etc. The perl we > have is stable and the problems it has are well known, which is good > enough in 99% of the cases. > > Including Perl in the make world build is something entirely different > from doing a make install /usr/ports, I'm sure. You can't just make install in /usr/ports/lang/perl any more - there's a FORBIDDEN in there. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 23:17:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A372D37C0EE; Thu, 6 Apr 2000 23:17:28 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA04730; Fri, 7 Apr 2000 00:17:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA97726; Fri, 7 Apr 2000 00:16:37 -0600 (MDT) Message-Id: <200004070616.AAA97726@harmony.village.org> To: Kris Kennaway Subject: Re: Perl 5.6.0? Cc: "Alexander N. Kabaev" , FreeBSD-Current In-reply-to: Your message of "Thu, 06 Apr 2000 21:21:12 PDT." References: Date: Fri, 07 Apr 2000 00:16:37 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : acceptable style for FreeBSD, not to mention probably breaking certain : features we support such as cross-compilation :-) One can almost cross compile OpenBSD. But the almost is due to the zillions of imported files that use the "native" build for the product in question, sometimes slightly tweaked for bmake vs gmake issue. Of course not all of these packages obey things like NOMAN and other settings that the rest fo the system obeys, and every time I've fixed it in the past for some package, a new version of it comes into the tree, or another package crops up, so I stopped after getting stepped on twice. Given how they do things, I'm surprised that cross compiling works as well as it does. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 23:35:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 14BB537C254; Thu, 6 Apr 2000 23:35:23 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA37395; Thu, 6 Apr 2000 23:35:12 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 6 Apr 2000 23:35:12 -0700 (PDT) From: Kris Kennaway To: patl@phoenix.volant.org Cc: Nick Hibma , Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000 patl@phoenix.volant.org wrote: > > Including Perl in the make world build is something entirely different > > from doing a make install /usr/ports, I'm sure. > > You can't just make install in /usr/ports/lang/perl any more - there's > a FORBIDDEN in there. Right, because we actually have a later version in the base system (5.005_03 vs 5.005_02 ;-) If the port were to be updated, the FORBIDDEN tag would be removed. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 6 23:45:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 586E937C06C; Thu, 6 Apr 2000 23:44:56 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 12dSVW-0003mu-00; Thu, 6 Apr 2000 23:44:43 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.1b+Sun/8.9.1) with SMTP id XAA18467; Thu, 6 Apr 2000 23:44:39 -0700 (PDT) Date: Thu, 6 Apr 2000 23:44:38 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: Perl 5.6.0? To: Kris Kennaway Cc: patl@phoenix.volant.org, Nick Hibma , Christopher Masto , Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6-Apr-00 at 23:35, Kris Kennaway (kris@FreeBSD.org) wrote: > On Thu, 6 Apr 2000 patl@phoenix.volant.org wrote: > > You can't just make install in /usr/ports/lang/perl any more - there's > > a FORBIDDEN in there. > > Right, because we actually have a later version in the base system > (5.005_03 vs 5.005_02 ;-) > > If the port were to be updated, the FORBIDDEN tag would be removed. Ah ha! In that case, I definately vote for updating the port to 5.6.0 so that the braver (or more needy) among us can thrash on it a bit before the eventual update in the base system. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 0:28:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id C6B9837C1FB for ; Fri, 7 Apr 2000 00:28:17 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12dTBf-0009zw-0B; Fri, 7 Apr 2000 07:28:16 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA49853; Fri, 7 Apr 2000 08:33:46 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 7 Apr 2000 08:34:31 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: Alfred Perlstein , Greg Lehey , current@freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 support.s src/sys/kern init_sysent.c kern_prot.c kern_sig.c In-Reply-To: <200004061757.KAA89372@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Apr 2000, Matthew Dillon wrote: > > :The version of Linux kernel source that I have uses the first: > : > :asmlinkage long sys_getppid(void) > :{ > : int pid; > : struct task_struct * me = current; > : struct task_struct * parent; > : > : parent = me->p_opptr; > : for (;;) { > : pid = parent->pid; > :#if __SMP__ > :{ > : struct task_struct *old = parent; > : mb(); > : parent = me->p_opptr; > : if (old != parent) > : continue; > :} > :#endif > : break; > : } > : return pid; > :} > : > :I like it. mb() is most certainly a "memory barrier" inline to > :force ordering constraints. interesting how they don't use > :volatile for the pointer though: > > mb() just prevents the compiler from optimizing access to the > structural fields (otherwise it might move the accesses outside > the for() loop and you would get an infinite loop. From the > compiler's point of view, mb() is a subroutine call (I assume > in the headers it's a volatile __asm). > > We can either use an mb() type of thing, or we can declare the structural > field volatile, or we can cast the access to be volatile. It also forces the cpu to drain writes and prevents reads from being re-ordered before the mb(). This is mainly a hint for alpha processors but I think it is relavent to other architectures. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 0:57: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from ugly.prth.tensor.pgs.com (ugly.prth.tensor.pgs.com [157.147.225.240]) by hub.freebsd.org (Postfix) with ESMTP id 7A5DC37C295 for ; Fri, 7 Apr 2000 00:56:59 -0700 (PDT) (envelope-from shocking@ugly.prth.tensor.pgs.com) Received: from ugly (IDENT:shocking@localhost.prth.tensor.pgs.com [127.0.0.1]) by ugly.prth.tensor.pgs.com (8.9.3/8.9.3) with ESMTP id PAA30392 for ; Fri, 7 Apr 2000 15:56:52 +0800 Message-Id: <200004070756.PAA30392@ugly.prth.tensor.pgs.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Versions of gas that support 3dnow!? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Apr 2000 15:56:52 +0800 From: Stephen Hocking-Senior Programmer PGS SPS Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been following the GLX stuff for Matrox G400s and noticed that there's now a version of gas that supports 3dnow! instructions without bugs. It's one of the snapshots by H.J. Lu - 2.9.5.0.34, found at ftp://ftp.varesearch.com/pub/support/hjl/binutils/ Any chance of this making its way into current? Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 1:19:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0943137B6FA for ; Fri, 7 Apr 2000 01:19:48 -0700 (PDT) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (trang.cdrom.com [204.216.28.153]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA33081; Fri, 7 Apr 2000 01:19:47 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA01210; Fri, 7 Apr 2000 01:19:16 -0700 (PDT) (envelope-from obrien) Date: Fri, 7 Apr 2000 01:19:16 -0700 From: "David O'Brien" To: Stephen Hocking-Senior Programmer PGS SPS Perth Cc: current@freebsd.org Subject: Re: Versions of gas that support 3dnow!? Message-ID: <20000407011916.A1180@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200004070756.PAA30392@ugly.prth.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004070756.PAA30392@ugly.prth.tensor.pgs.com>; from shocking@ugly.prth.tensor.pgs.com on Fri, Apr 07, 2000 at 03:56:52PM +0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 07, 2000 at 03:56:52PM +0800, Stephen Hocking-Senior Programmer PGS SPS Perth wrote: > now a version of gas that supports 3dnow! instructions without bugs. It's one The base Binutils (which includes gas) is being upgraded. There are several groups that need to be addressed in the upgrade, so I don't yet know which version will be used in the upgrade. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 1:42: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 763E837B684; Fri, 7 Apr 2000 01:41:52 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca5-83.ix.netcom.com [209.109.234.83]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id EAA30800; Fri, 7 Apr 2000 04:41:49 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id BAA88805; Fri, 7 Apr 2000 01:41:19 -0700 (PDT) Date: Fri, 7 Apr 2000 01:41:19 -0700 (PDT) Message-Id: <200004070841.BAA88805@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: current@FreeBSD.org, stable@FreeBSD.org Subject: HEADS UP: ports Makefiles being updated soon (forwarded) From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI. -PW === From: asami@freebsd.org (Satoshi Asami) Subject: HEADS UP: ports Makefiles being updated soon To: ports@freebsd.org CC: committers@freebsd.org Date: Fri, 7 Apr 2000 01:15:16 -0700 (PDT) Message-Id: <200004070815.BAA88701@silvia.hip.berkeley.edu> Hello world, As we have been discussing on the ports list, we have decided to introduce a slight syntax change to the port Makefiles regarding DISTNAME and PKGNAME. This change will be done this weekend. I will freeze the ports tree Friday night (U.S. Pacific Time) and a small group of volunteers will convert the entire tree in one pass. I will then unfreeze the tree and we can go back to business. I don't expect anything to break but since we are talking about over 3,000 ports, I can't guarantee that everything will go smooth. If you haven't cvsupped ports for a while, you may want to do it now. After the conversion, "old style" ports will no longer be accepted. Please read the handbook's porting section at, for instance, http://www.FreeBSD.org/handbook/porting.html#PORTING-SAMPLEM for details. (The above page seems to be still showing the old version -- the documentation change was committed today, so please check back later.) Also, make sure that you have the latest ports/Mk/bsd.port.mk if you are using anything from ports-current. This means, if you are cvsupping individual ports collections, you need to have "ports-base" in your cvsupfile. Thanks, Satoshi (and the friendly ports team) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 2: 2:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 9DC2837B644 for ; Fri, 7 Apr 2000 02:02:37 -0700 (PDT) (envelope-from bgulla@mindspring.com) Received: from brett (user-2iveain.dialup.mindspring.com [165.247.42.87]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with SMTP id FAA05620 for ; Fri, 7 Apr 2000 05:02:32 -0400 (EDT) Reply-To: From: "Brett Gulla" To: Subject: Date: Fri, 7 Apr 2000 05:05:22 -0400 Message-ID: <000001bfa070$67b723a0$572af7a5@brett> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 6df833c4 unsubscribe freebsd-current bgulla@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 2: 3:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 5336A37B741; Fri, 7 Apr 2000 02:03:45 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-37.iptelecom.net.ua [212.9.227.37]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA29061; Fri, 7 Apr 2000 12:10:32 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id MAA58677; Fri, 7 Apr 2000 12:03:09 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <38EDA44A.3AC1BAB0@altavista.net> Date: Fri, 07 Apr 2000 12:03:07 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Satoshi Asami Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP: ports Makefiles being updated soon (forwarded) References: <200004070841.BAA88805@silvia.hip.berkeley.edu> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Satoshi Asami wrote: > After the conversion, "old style" ports will no longer be accepted. How about those unlucky, which are patiently waiting for their destiny in the PR database? I personally have several and would like to know if any activity from my side is reqired. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 3: 3:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from apoq.skynet.be (apoq.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 74F7837B541; Fri, 7 Apr 2000 03:03:08 -0700 (PDT) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by apoq.skynet.be (Postfix) with ESMTP id 8D3E11F231; Fri, 7 Apr 2000 12:03:06 +0200 (MET DST) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 7 Apr 2000 11:56:15 +0200 To: "Alexander N. Kabaev" , Kris Kennaway From: Brad Knowles Subject: Re: Perl 5.6.0? Cc: FreeBSD-Current , "Alexander N. Kabaev" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:57 AM -0400 2000/4/7, Alexander N. Kabaev wrote: > I am perfectly aware of the way OpenBSD builds contrib software. I am just > making a point that they have found perl 5.6.0 is stable enough to be > included into their OS. It's my understanding that we already have a better and cleaner way of handling international versus US crypto issues with OpenSSH than they do, thanks to the stubs that were put into place in the libraries. Given this, and given the level of tight integration we have elsewhere with those things that we have taken the somewhat unusual step of integrating into FreeBSD, I don't take their inclusion of Perl 5.6.0 to be a necessary and sufficient condition for us to do the same. Just because someone else jumped off a bridge and has survived (so far), does this necessarily mean it's a good idea for us to try to follow suit at this stage? -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 4:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 5722D37B8D2; Fri, 7 Apr 2000 04:23:23 -0700 (PDT) (envelope-from tobez@plab.ku.dk) Received: (from tobez@localhost) by plab.ku.dk (8.9.3/8.9.3) id NAA10617; Fri, 7 Apr 2000 13:24:34 +0200 (CEST) (envelope-from tobez) Date: Fri, 7 Apr 2000 13:24:34 +0200 From: Anton Berezin To: "Alexander N. Kabaev" Cc: Kris Kennaway , FreeBSD-Current , "Alexander N. Kabaev" Subject: Re: Perl 5.6.0? Message-ID: <20000407132434.B10322@plab.ku.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kabaev@mail.ru on Fri, Apr 07, 2000 at 12:57:16AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 07, 2000 at 12:57:16AM -0400, Alexander N. Kabaev wrote: > I am perfectly aware of the way OpenBSD builds contrib software. I am > just making a point that they have found perl 5.6.0 is stable enough > to be included into their OS. It is an issue of personal relationships and politics, not the technical one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other way around). Cheers, -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 4:41:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id 0645337B9CD for ; Fri, 7 Apr 2000 04:41:34 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 12dX8h-0005ir-0C; Fri, 7 Apr 2000 11:41:29 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id MAA78305; Fri, 7 Apr 2000 12:44:11 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Fri, 7 Apr 2000 12:38:16 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: USB BSD list Cc: FreeBSD CURRENT Mailing List Subject: USB To Do list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If've put up a list of things that need to be done still in the FreeBSD USB stack. The list is _big_. I'll be adding things as they come up. http://www.etla.net/~n_hibma/usb/usb.pl A lot of the items are not that difficult to do and if you feel like taking up a little project, start working on something and send patches/source as you work through them. It might change the short term priority list a bit to include your toy :-) The Todo list is included below. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Do list for the USB project: Let meknow if you would like to participate in any way, or you have done one of the items below! - Short term priority list - Finish off the import of the urio driver. Update the license in rio500_usb.h. - Finish the synchronisation with NetBSD - Split umass into two parts: wire (BBB, CBI) and command protocols - Investigate panic on close of interrupt pipe with low frequency. - Finally checkout the umodem driver and include it in the tree. - USB base stack and general items. - Fix/check suspend on UHCI and OHCI controllers, especially on laptops. - Use a kthread to handle the 'Done Queue'. - OHCI connection problems - Check out the manpages available. Add new ones where appropriate. - Generic driver should be available for all devices, not only for the ones that nothing else attaches to. - Possibility of locking pipes, interfaces & devices to make sure no concurrent accesses are done (confusing a device, e.g. e-shuttle USB) - Implement poll/select for generic device. Idea: When select is called for reading and no read is in progress a read for MaxPacketSize with SHORT PACKET OK set is initiated. Select for writing always succeeds. - One shot transfers on interrupt pipes (needed for 'bulk' outs on low speed devices for example). - USB userland utility (usbcontrol) - The word 'class' is used in usb.h. This is a problem for c++ compilers. Change the whole interface for usbdevs/usbd to something sensible. - Create a usbcontrol util combining all the functionality of usb_dump.c, usbdevs and the usb*something* utility in NetBSD into one. - USB Serial port driver (usio) driver (by Doug Ambrisko) - Check out the version of sdcc that is in ports nowadays. - Check out which dongles the usio driver works with - Usio manpage. - USB Mass Storage (umass) driver - Check out the file system corruption problems under heavy load / added load of a USB ethernet dongle. - Check out support for ATAPI devices. - Convert Read/Write_6 to Read/Write_10 in transform. This avoids having to quirk every single UFI compliant device. - USB Keyboards - Keyboard in DDB debugger does not work. - USB printer port support - Bi-directional support - Is the manual page up to date? Does it specify all the flags you can set on the device minor number? - Related: - PCI/USB/PCCard/PCMCIA/other vendor, product and revision Id matching code should be made generic, so that drivers can match in a more generic way. The ID's should be collected into one location to make the addition of new Id's more generic. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 5:15:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id E315C37BB2C for ; Fri, 7 Apr 2000 05:15:11 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:9jcEH2ZaMEhUGROKYf1zDPR5orMZQbXt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id VAA08096; Fri, 7 Apr 2000 21:13:49 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA16818; Fri, 7 Apr 2000 21:20:17 +0900 (JST) Message-Id: <200004071220.VAA16818@zodiac.mech.utsunomiya-u.ac.jp> To: usb-bsd@egroups.com Cc: FreeBSD CURRENT Mailing List , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: [usb-bsd] USB To Do list In-reply-to: Your message of "Fri, 07 Apr 2000 12:38:16 +0100." References: Date: Fri, 07 Apr 2000 21:20:16 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >To Do list for the USB project: > >Let meknow if you would like to participate in any way, or you have >done one of the items below! [...] >- USB Keyboards > - Keyboard in DDB debugger does not work. In what configuration does it not work? I can use my USB keyboard in DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel PIIX3 here... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 5:23:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id EF4F037BA6F for ; Fri, 7 Apr 2000 05:23:01 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1) id 12dXmq-00034E-00 for freebsd-current@FreeBSD.ORG; Fri, 07 Apr 2000 14:22:56 +0200 From: Sheldon Hearn To: FreeBSD-Current Subject: Re: Perl 5.6.0? Date: Fri, 07 Apr 2000 14:22:55 +0200 Message-ID: <11793.955110175@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We want to update our system perl5. It'll take some work. If you want to do the work, your patches will be greatly appreciated by our perl5 maintainer, Mark Murray . Since nobody here has offered to do any _work_ on incorporating perl 5.6.0 into FreeBSD 5.0-CURRENT, please would you all just shut up about it? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 5:23:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id C8EF937B9CD for ; Fri, 7 Apr 2000 05:23:06 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:xVcK52L/8s/6kWtJIE5hX1xGPN3PSLqq@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id VAA08166; Fri, 7 Apr 2000 21:23:00 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA17024; Fri, 7 Apr 2000 21:29:27 +0900 (JST) Message-Id: <200004071229.VAA17024@zodiac.mech.utsunomiya-u.ac.jp> To: usb-bsd@egroups.com Cc: FreeBSD CURRENT Mailing List , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: SMP problem? (was: Re: [usb-bsd] USB To Do list) In-reply-to: Your message of "Fri, 07 Apr 2000 12:38:16 +0100." References: Date: Fri, 07 Apr 2000 21:29:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >To Do list for the USB project: [...] >- USB base stack and general items. I am currently having trouble with Gigabyte GA-6BXD, dual Pentium III motherboard. If I boot a UP kernel (5.0-CURRENT), the PIIX4 USB controller works fine. If I boot a SMP kernel (the only difference from the UP kernel is support for SMP), the kernel seems unable to communicate with the USB device. When I plug a USB keyboard, I get uhci_timeout: ii=0xc0a601c0 uhci_timeout: ii=0xc0a601c0 uhci_timeout: ii=0xc0a601c0 usbd_new_device: addr=2, getting first desc failed uhub_explore: usb_new_device failed, error=TIMEOUT uhub0: device problem, disabling port 1 I vaguely remember someone also reported similar problems with the SMP kernel in the past.... Interesting thing is that I have another SMP box, and its USB works fine. The version is 4.0-STABLE. The USB controller is VIA 83c572. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 6:10:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id F330537BC10 for ; Fri, 7 Apr 2000 06:10:37 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 12dYWy-000DiP-0V; Fri, 7 Apr 2000 14:10:36 +0100 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id OAA79754; Fri, 7 Apr 2000 14:13:32 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Fri, 7 Apr 2000 14:07:36 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: usb-bsd@egroups.com Cc: FreeBSD CURRENT Mailing List , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: [usb-bsd] USB To Do list In-Reply-To: <200004071220.VAA16818@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >- USB Keyboards > > - Keyboard in DDB debugger does not work. > > In what configuration does it not work? I can use my USB keyboard in > DDB without problems on a dual PPro box (4.0-STABLE) with a UHCI > controller (VIA 83c572) card and a Pentium box (3.4-STABLE) with Intel > PIIX3 here... I've seen it run away like mad (like pressing Return a hundred times a second). Maybe that was just a glitch (on UHCI hardware). I've seen this same behaviour on an iMac running NetBSD. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 6:11:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id B8C5B37B586 for ; Fri, 7 Apr 2000 06:11:25 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 12dYXj-000I5x-0B; Fri, 7 Apr 2000 13:11:23 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id OAA79768; Fri, 7 Apr 2000 14:14:21 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Fri, 7 Apr 2000 14:08:25 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: usb-bsd@egroups.com Cc: FreeBSD CURRENT Mailing List , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP problem? (was: Re: [usb-bsd] USB To Do list) In-Reply-To: <200004071229.VAA17024@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does it say before this info? Shared interrupt? USB does work on SMP (or at least in some cases). > uhci_timeout: ii=0xc0a601c0 > uhci_timeout: ii=0xc0a601c0 > uhci_timeout: ii=0xc0a601c0 > usbd_new_device: addr=2, getting first desc failed > uhub_explore: usb_new_device failed, error=TIMEOUT > uhub0: device problem, disabling port 1 > > I vaguely remember someone also reported similar problems with the SMP > kernel in the past.... > > Interesting thing is that I have another SMP box, and its USB works fine. > The version is 4.0-STABLE. The USB controller is VIA 83c572. > > Kazu > > ------------------------------------------------------------------------ > @Backup- Protect and Access your data any time, any where on the net. > Try @Backup FREE and recieve 300 points from mypoints.com Install now: > http://click.egroups.com/1/2345/6/_/85983/_/955110182/ > ------------------------------------------------------------------------ > > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 6:47:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 913CE37BD6C; Fri, 7 Apr 2000 06:47:24 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F54AF.dip0.t-ipconnect.de [193.159.84.175]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id OAA01302; Fri, 7 Apr 2000 14:46:28 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 6ADC4AC2C; Fri, 7 Apr 2000 15:49:13 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id PAA24178; Fri, 7 Apr 2000 15:46:22 +0200 (CEST) (envelope-from alex) Date: Fri, 7 Apr 2000 15:46:21 +0200 From: Alexander Langer To: Maxim Sobolev Cc: Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP: ports Makefiles being updated soon (forwarded) Message-ID: <20000407154621.E17612@cichlids.cichlids.com> Mail-Followup-To: Maxim Sobolev , Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG References: <200004070841.BAA88805@silvia.hip.berkeley.edu> <38EDA44A.3AC1BAB0@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38EDA44A.3AC1BAB0@altavista.net>; from sobomax@altavista.net on Fri, Apr 07, 2000 at 12:03:07PM +0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Maxim Sobolev (sobomax@altavista.net): > How about those unlucky, which are patiently waiting for their destiny in the > PR database? I personally have several and would like to know if any activity > from my side is reqired. Let the committers do that. It's a trivial fix. If you change stuff anyway (e.g. new version has been made available in the meanwhile), you can correct this in the new PR. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 8:39:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 70DCA37B965 for ; Fri, 7 Apr 2000 08:39:34 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 26183 invoked from network); 7 Apr 2000 15:39:33 -0000 Received: from lcb89.cvzoom.net (HELO cvzoom.net) (63.65.159.89) by ns.cvzoom.net with SMTP; 7 Apr 2000 15:39:33 -0000 Message-ID: <38EE011D.B81BA63C@cvzoom.net> Date: Fri, 07 Apr 2000 11:39:09 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Overwhelming messages from /sys/netinet/if_ether.c Content-Type: multipart/mixed; boundary="------------ABD696746D33D54680111FE2" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------ABD696746D33D54680111FE2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Since I started using a cable modem and dhclient, my system has been literally overwhelmed with messages like: /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! Man, these messages were pouring out of syslogd like mad, and my /var/log/messages* files had to be deleted, because they were growing so huge. There were literally hundreds of these messages pouring out via syslogd per second, and they were coming non-stop. There were so many messages coming out, my hard drive was overwhelmed until dhclient finally obtain/ed a lease. That said, I suggest we make the following patch to /sys/netinet/if_ether.c: --- if_ether.c.orig Wed Mar 29 02:50:39 2000 +++ if_ether.c Fri Apr 7 11:24:54 2000 @@ -554,9 +554,9 @@ return; } if (isaddr.s_addr == myaddr.s_addr) { - log(LOG_ERR, + /* log(LOG_ERR, "arp: %6D is using my IP address %s!\n", - ea->arp_sha, ":", inet_ntoa(isaddr)); + ea->arp_sha, ":", inet_ntoa(isaddr)); */ itaddr = myaddr; goto reply; } - Donn --------------ABD696746D33D54680111FE2 Content-Type: text/plain; charset=us-ascii; name="if_ether.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="if_ether.diff" --- if_ether.c.orig Wed Mar 29 02:50:39 2000 +++ if_ether.c Fri Apr 7 11:24:54 2000 @@ -554,9 +554,9 @@ return; } if (isaddr.s_addr == myaddr.s_addr) { - log(LOG_ERR, + /* log(LOG_ERR, "arp: %6D is using my IP address %s!\n", - ea->arp_sha, ":", inet_ntoa(isaddr)); + ea->arp_sha, ":", inet_ntoa(isaddr)); */ itaddr = myaddr; goto reply; } --------------ABD696746D33D54680111FE2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 8:52:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id A6F7537B574 for ; Fri, 7 Apr 2000 08:52:07 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id LAA68160; Fri, 7 Apr 2000 11:52:05 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <38EE011D.B81BA63C@cvzoom.net> Date: Fri, 07 Apr 2000 11:52:04 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Donn Miller Subject: RE: Overwhelming messages from /sys/netinet/if_ether.c Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The message in question can be extremely useful in case there is IP address clash on the local network. I suggest we just change the code in question to ignore clashes over 0.0.0.0 address only. On 07-Apr-00 Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has been > literally overwhelmed with messages like: > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > > Man, these messages were pouring out of syslogd like mad, and my > /var/log/messages* files had to be deleted, because they were growing > so huge. There were literally hundreds of these messages pouring out > via syslogd per second, and they were coming non-stop. There were so > many messages coming out, my hard drive was overwhelmed until dhclient > finally obtain/ed a lease. That said, I suggest we make the following > patch to /sys/netinet/if_ether.c: > > --- if_ether.c.orig Wed Mar 29 02:50:39 2000 > +++ if_ether.c Fri Apr 7 11:24:54 2000 > @@ -554,9 +554,9 @@ > return; > } > if (isaddr.s_addr == myaddr.s_addr) { > - log(LOG_ERR, > + /* log(LOG_ERR, > "arp: %6D is using my IP address %s!\n", > - ea->arp_sha, ":", inet_ntoa(isaddr)); > + ea->arp_sha, ":", inet_ntoa(isaddr)); */ > itaddr = myaddr; > goto reply; > } > > > - Donn ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Apr-00 Time: 11:49:33 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 8:57:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from milquetoast.cs.mcgill.ca (milquetoast.CS.McGill.CA [132.206.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 9FB7137BE68 for ; Fri, 7 Apr 2000 08:57:40 -0700 (PDT) (envelope-from mat@milquetoast.cs.mcgill.ca) Received: (from mat@localhost) by milquetoast.cs.mcgill.ca (8.9.3/8.9.3) id LAA13731; Fri, 7 Apr 2000 11:57:30 -0400 (EDT) Date: Fri, 7 Apr 2000 11:57:30 -0400 From: Mathew Kanner To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Message-ID: <20000407115730.B10907@cs.mcgill.ca> References: <38EE011D.B81BA63C@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: Donn Miller's message [Overwhelming messages from /sys/netinet/if_ether.c] as of Fri, Apr 07, 2000 at 11:39:09AM -0400 Organization: SOCS, McGill University, Montreal, CANADA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 07, Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has been > literally overwhelmed with messages like: > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > I haven't tried this but how about changing the /sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up the interface. --Mat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 9:24:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 23BF837B6CE for ; Fri, 7 Apr 2000 09:24:42 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA09236; Fri, 7 Apr 2000 09:24:41 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA27951; Fri, 7 Apr 2000 09:24:40 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 7 Apr 2000 09:24:40 -0700 (PDT) Message-Id: <200004071624.JAA27951@vashon.polstra.com> To: ak03@gte.com Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Alexander N. Kabaev wrote: > The message in question can be extremely useful in case there is IP address > clash on the local network. I suggest we just change the code in question to > ignore clashes over 0.0.0.0 address only. I agree. John -- John Polstra jdp@polstra.com 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-current" in the body of the message From owner-freebsd-current Fri Apr 7 9:38:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 6CC7637B574 for ; Fri, 7 Apr 2000 09:38:41 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id MAA72442; Fri, 7 Apr 2000 12:37:31 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.0.FreeBSD:000407123730:68156=_" In-Reply-To: <200004071624.JAA27951@vashon.polstra.com> Date: Fri, 07 Apr 2000 12:37:30 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: John Polstra Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.0.FreeBSD:000407123730:68156=_ Content-Type: text/plain; charset=us-ascii Trivial patch attached :) On 07-Apr-00 John Polstra wrote: > In article , > Alexander N. Kabaev wrote: >> The message in question can be extremely useful in case there is IP address >> clash on the local network. I suggest we just change the code in question to >> ignore clashes over 0.0.0.0 address only. > > I agree. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa --_=XFMail.1.4.0.FreeBSD:000407123730:68156=_ Content-Disposition: attachment; filename="if_ether.diff" Content-Transfer-Encoding: base64 Content-Description: if_ether.diff Content-Type: application/octet-stream; name=if_ether.diff; SizeOnDisk=516 SW5kZXg6IGlmX2V0aGVyLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL3Vzci9uY3ZzL3NyYy9zeXMv bmV0aW5ldC9pZl9ldGhlci5jLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjY4CmRpZmYgLXUgLXIx LjY4IGlmX2V0aGVyLmMKLS0tIGlmX2V0aGVyLmMJMjAwMC8wMy8yOSAwNzo1MDozOQkxLjY4Cisr KyBpZl9ldGhlci5jCTIwMDAvMDQvMDcgMTY6Mjk6NDkKQEAgLTU1Myw3ICs1NTMsNyBAQAogCQlt X2ZyZWVtKG0pOwogCQlyZXR1cm47CiAJfQotCWlmIChpc2FkZHIuc19hZGRyID09IG15YWRkci5z X2FkZHIpIHsKKwlpZiAoaXNhZGRyLnNfYWRkciA9PSBteWFkZHIuc19hZGRyICYmIGlzYWRkci5z X2FkZHIgKSB7CiAJCWxvZyhMT0dfRVJSLAogCQkgICAiYXJwOiAlNkQgaXMgdXNpbmcgbXkgSVAg YWRkcmVzcyAlcyFcbiIsCiAJCSAgIGVhLT5hcnBfc2hhLCAiOiIsIGluZXRfbnRvYShpc2FkZHIp KTsK --_=XFMail.1.4.0.FreeBSD:000407123730:68156=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 9:54:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 284C737C307; Fri, 7 Apr 2000 09:54:42 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id JAA69667; Fri, 7 Apr 2000 09:54:42 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 7 Apr 2000 09:54:41 -0700 (PDT) From: Kris Kennaway To: Maxim Sobolev Cc: Satoshi Asami , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP: ports Makefiles being updated soon (forwarded) In-Reply-To: <38EDA44A.3AC1BAB0@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, Maxim Sobolev wrote: > > After the conversion, "old style" ports will no longer be accepted. > > How about those unlucky, which are patiently waiting for their destiny in the > PR database? I personally have several and would like to know if any activity > from my side is reqired. I think Satoshi was just referring to newly-submitted ports. Existing queued ones won't need to be changed. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 10: 7:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id D4C9D37BA19 for ; Fri, 7 Apr 2000 10:07:53 -0700 (PDT) (envelope-from julian@elischer.org) Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id BAA08990 for ; Sat, 8 Apr 2000 01:07:43 +0800 Received: from jules.elischer.org (reggae-20-174.nv.iinet.net.au [203.59.85.174]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id BAA28086 for ; Sat, 8 Apr 2000 01:07:42 +0800 Message-ID: <38EE15B6.63DECDAD@elischer.org> Date: Fri, 07 Apr 2000 10:07:02 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: new device/bus stuff Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a howto on how to convert drivers from the old to new form? for example if_sr.c no longer shows up (or is even probed) in 4.0-stable. I've looked here and there but I can't figure out if there is some ISA_SHIM option needed (it's not in LINT if so). There seemes to be lotsa complicated man pages but I haven't found a brief "here's what you probably need to do" doc.. I'm looking for something that doesn't require rewriting the whole thing.. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 10:10:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 645EC37BF1C for ; Fri, 7 Apr 2000 10:10:25 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12dcGt-000NNU-0K; Fri, 7 Apr 2000 17:10:20 +0000 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id SAA86855; Fri, 7 Apr 2000 18:12:47 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Fri, 7 Apr 2000 18:06:48 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Alexander N. Kabaev" Cc: FreeBSD-Current Subject: Re: Perl 5.6.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could we stop this nonsense thread now? No one is against it. The only reason why it is not in the tree is that no one has the time to actually implement the change. If someone wants it in the tree, do the work and submit it to the current maintainer of Perl in FreeBSD. Thanks in advance. Nick On Thu, 6 Apr 2000, Alexander N. Kabaev wrote: > According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's source > tree already. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 10:10:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4DAB937BEBE for ; Fri, 7 Apr 2000 10:10:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA12517; Fri, 7 Apr 2000 10:10:49 -0700 Date: Fri, 7 Apr 2000 10:10:51 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: new device/bus stuff In-Reply-To: <38EE15B6.63DECDAD@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, Julian Elischer wrote: > Is there a howto on how to convert drivers from the old to new > form? > > for example if_sr.c no longer shows up (or is even probed) in > 4.0-stable. I've looked here and there but I can't figure out if there > is some ISA_SHIM option needed (it's not in LINT if so). COMPAT_OLDISA? > > There seemes to be lotsa complicated man pages but I haven't found > a brief "here's what you probably need to do" doc.. > > I'm looking for something that doesn't require rewriting the whole > thing.. > > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 11:33:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 4FAEB37BA30 for ; Fri, 7 Apr 2000 11:33:40 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA41098; Fri, 7 Apr 2000 11:33:30 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004071833.LAA41098@gndrsh.dnsmgr.net> Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: from "Alexander N. Kabaev" at "Apr 7, 2000 11:52:04 am" To: ak03@gte.com (Alexander N. Kabaev) Date: Fri, 7 Apr 2000 11:33:29 -0700 (PDT) Cc: dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The message in question can be extremely useful in case there is IP address > clash on the local network. I suggest we just change the code in question to > ignore clashes over 0.0.0.0 address only. No, don't do that, anyone arping 0.0.0.0 on any network around here I sure as heck want to know about it asap! Someone someplace on that stupid telco's DSL bridged network is mis-configured and sending out arp messages for the 0 addresses. Easy enough to cause though: ifconfig xx0 0.0.0.0 up should do the trick... > On 07-Apr-00 Donn Miller wrote: > > Since I started using a cable modem and dhclient, my system has been > > literally overwhelmed with messages like: > > > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > > > > Man, these messages were pouring out of syslogd like mad, and my > > /var/log/messages* files had to be deleted, because they were growing > > so huge. There were literally hundreds of these messages pouring out > > via syslogd per second, and they were coming non-stop. There were so > > many messages coming out, my hard drive was overwhelmed until dhclient > > finally obtain/ed a lease. That said, I suggest we make the following > > patch to /sys/netinet/if_ether.c: > > > > --- if_ether.c.orig Wed Mar 29 02:50:39 2000 > > +++ if_ether.c Fri Apr 7 11:24:54 2000 > > @@ -554,9 +554,9 @@ > > return; > > } > > if (isaddr.s_addr == myaddr.s_addr) { > > - log(LOG_ERR, > > + /* log(LOG_ERR, > > "arp: %6D is using my IP address %s!\n", > > - ea->arp_sha, ":", inet_ntoa(isaddr)); > > + ea->arp_sha, ":", inet_ntoa(isaddr)); */ > > itaddr = myaddr; > > goto reply; > > } > > > > > > - Donn > > ---------------------------------- > E-Mail: Alexander N. Kabaev > Date: 07-Apr-00 > Time: 11:49:33 > ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 11:59:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 2766237B7BC for ; Fri, 7 Apr 2000 11:59:49 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id OAA73007; Fri, 7 Apr 2000 14:59:10 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <200004071833.LAA41098@gndrsh.dnsmgr.net> Date: Fri, 07 Apr 2000 14:59:10 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: "Rodney W. Grimes" Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Cc: (Donn Miller) , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT in order to bring interface up. Windows seems to do that as well or there is no sane explanation for the relatively big number of these nasty messages I am getting every time MediaOne network goes down and several PCs sharing the same cable network segment attempt to renew their lease at the same time. On 07-Apr-00 Rodney W. Grimes wrote: >> The message in question can be extremely useful in case there is IP address >> clash on the local network. I suggest we just change the code in question to >> ignore clashes over 0.0.0.0 address only. > > No, don't do that, anyone arping 0.0.0.0 on any network around here > I sure as heck want to know about it asap! Someone someplace on > that stupid telco's DSL bridged network is mis-configured and > sending out arp messages for the 0 addresses. Easy enough to > cause though: > > ifconfig xx0 0.0.0.0 up > > should do the trick... > ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Apr-00 Time: 14:35:14 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12: 9:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9C5A237BE7E for ; Fri, 7 Apr 2000 12:09:36 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00729; Fri, 7 Apr 2000 12:14:18 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004071914.MAA00729@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rodney W. Grimes" Cc: ak03@gte.com (Alexander N. Kabaev), dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-reply-to: Your message of "Fri, 07 Apr 2000 11:33:29 PDT." <200004071833.LAA41098@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Apr 2000 12:14:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The message in question can be extremely useful in case there is IP address > > clash on the local network. I suggest we just change the code in question to > > ignore clashes over 0.0.0.0 address only. > > No, don't do that, anyone arping 0.0.0.0 on any network around here > I sure as heck want to know about it asap! Then use a tool designed for the job. You'll only get this message on a system that's a DHCP client and currently trying to get a lease. I don't think that you would ever get any utility from the code as it stands, so the change is not going to affect you. (Note that if you were to configure a system to listen on 0.0.0.0 in order to use this message, you would then be arping for 0.0.0.0, which would appear to defeat your purpose.) Can I kindly suggest that you go find a bridge or a dam or some gun-control law to go oppose for a few months? This random sniper activity is pretty irritating. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:25:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 382EA37C05A for ; Fri, 7 Apr 2000 12:25:09 -0700 (PDT) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA10921; Fri, 7 Apr 2000 12:24:56 -0700 (PDT) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id MAA00849; Fri, 7 Apr 2000 12:24:57 -0700 (PDT) Message-Id: <200004071924.MAA00849@papermill.wrs.com> To: Donn Miller Cc: freebsd-current@freebsd.org From: David Holloway Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-reply-to: Your message of "Fri, 07 Apr 2000 11:39:09 EDT." <38EE011D.B81BA63C@cvzoom.net> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Fri, 07 Apr 2000 12:24:57 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have seen that situation before as well and there may be more slight tolerance-style improvements that could be made but I can't think of any at the moment. In message <38EE011D.B81BA63C@cvzoom.net>, Donn Miller writes: >This is a multi-part message in MIME format. >--------------ABD696746D33D54680111FE2 >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Since I started using a cable modem and dhclient, my system has been >literally overwhelmed with messages like: > >/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > >Man, these messages were pouring out of syslogd like mad, and my >/var/log/messages* files had to be deleted, because they were growing >so huge. There were literally hundreds of these messages pouring out >via syslogd per second, and they were coming non-stop. There were so >many messages coming out, my hard drive was overwhelmed until dhclient >finally obtain/ed a lease. That said, I suggest we make the following >patch to /sys/netinet/if_ether.c: > >--- if_ether.c.orig Wed Mar 29 02:50:39 2000 >+++ if_ether.c Fri Apr 7 11:24:54 2000 >@@ -554,9 +554,9 @@ > return; > } > if (isaddr.s_addr == myaddr.s_addr) { >- log(LOG_ERR, >+ /* log(LOG_ERR, > "arp: %6D is using my IP address %s!\n", >- ea->arp_sha, ":", inet_ntoa(isaddr)); >+ ea->arp_sha, ":", inet_ntoa(isaddr)); */ > itaddr = myaddr; > goto reply; > } > > >- Donn >--------------ABD696746D33D54680111FE2 >Content-Type: text/plain; charset=us-ascii; > name="if_ether.diff" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline; > filename="if_ether.diff" > >--- if_ether.c.orig Wed Mar 29 02:50:39 2000 >+++ if_ether.c Fri Apr 7 11:24:54 2000 >@@ -554,9 +554,9 @@ > return; > } > if (isaddr.s_addr == myaddr.s_addr) { >- log(LOG_ERR, >+ /* log(LOG_ERR, > "arp: %6D is using my IP address %s!\n", >- ea->arp_sha, ":", inet_ntoa(isaddr)); >+ ea->arp_sha, ":", inet_ntoa(isaddr)); */ > itaddr = myaddr; > goto reply; > } > >--------------ABD696746D33D54680111FE2-- > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:26:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 3E7F137B611 for ; Fri, 7 Apr 2000 12:26:29 -0700 (PDT) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA11443; Fri, 7 Apr 2000 12:26:26 -0700 (PDT) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id MAA00894; Fri, 7 Apr 2000 12:26:28 -0700 (PDT) Message-Id: <200004071926.MAA00894@papermill.wrs.com> To: Mathew Kanner Cc: current@FreeBSD.ORG From: David Holloway Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-reply-to: Your message of "Fri, 07 Apr 2000 11:57:30 EDT." <20000407115730.B10907@cs.mcgill.ca> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Fri, 07 Apr 2000 12:26:27 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No... In message <20000407115730.B10907@cs.mcgill.ca>, Mathew Kanner writes: >On Apr 07, Donn Miller wrote: >> Since I started using a cable modem and dhclient, my system has been >> literally overwhelmed with messages like: >> >> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! >> > > I haven't tried this but how about changing the >/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up >the interface. > > --Mat > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:42:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.wrs.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 2CCA437C123 for ; Fri, 7 Apr 2000 12:42:30 -0700 (PDT) (envelope-from davidhol@windriver.com) Received: from papermill.wrs.com (papermill [147.11.48.34]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA17053; Fri, 7 Apr 2000 12:42:27 -0700 (PDT) Received: from papermill (localhost [127.0.0.1]) by papermill.wrs.com (8.9.1/8.9.0) with ESMTP id MAA01133; Fri, 7 Apr 2000 12:42:28 -0700 (PDT) Message-Id: <200004071942.MAA01133@papermill.wrs.com> To: "Alexander N. Kabaev" Cc: dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG From: David Holloway Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-reply-to: Your message of "Fri, 07 Apr 2000 14:59:10 EDT." Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Fri, 07 Apr 2000 12:42:28 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I say with 99% certainty that assigning 0.0.0.0 to the interface is a requirement of dhcp. You can't stop using it and expect dhcp to work. In message , "Alexander N. Kabaev" writes: >FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT >in order to bring interface up. Windows seems to do that as well or >there is no sane explanation for the relatively big number of these nasty >messages I am getting every time MediaOne network goes down and several PCs >sharing the same cable network segment attempt to renew their lease at the sam >e >time. > > >On 07-Apr-00 Rodney W. Grimes wrote: >>> The message in question can be extremely useful in case there is IP address >>> clash on the local network. I suggest we just change the code in question t >o >>> ignore clashes over 0.0.0.0 address only. >> >> No, don't do that, anyone arping 0.0.0.0 on any network around here >> I sure as heck want to know about it asap! Someone someplace on >> that stupid telco's DSL bridged network is mis-configured and >> sending out arp messages for the 0 addresses. Easy enough to >> cause though: >> >> ifconfig xx0 0.0.0.0 up >> >> should do the trick... >> >---------------------------------- >E-Mail: Alexander N. Kabaev >Date: 07-Apr-00 >Time: 14:35:14 >---------------------------------- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:46:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 3CEE837C068 for ; Fri, 7 Apr 2000 12:46:10 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id PAA73179; Fri, 7 Apr 2000 15:45:30 -0400 (EDT) (envelope-from ak03) 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: <200004071942.MAA01133@papermill.wrs.com> Date: Fri, 07 Apr 2000 15:45:30 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: David Holloway Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Cc: current@FreeBSD.ORG, (Donn Miller) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same impression fom reading dhclient sources. On 07-Apr-00 David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. > ---------------------------------- E-Mail: Alexander N. Kabaev Date: 07-Apr-00 Time: 15:44:39 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:46:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 22A6D37C068 for ; Fri, 7 Apr 2000 12:46:21 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA41238; Fri, 7 Apr 2000 12:46:07 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004071946.MAA41238@gndrsh.dnsmgr.net> Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: from "Alexander N. Kabaev" at "Apr 7, 2000 02:59:10 pm" To: ak03@gte.com (Alexander N. Kabaev) Date: Fri, 7 Apr 2000 12:46:07 -0700 (PDT) Cc: dmmiller@cvzoom.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT > in order to bring interface up. Windows seems to do that as well or > there is no sane explanation for the relatively big number of these nasty > messages I am getting every time MediaOne network goes down and several PCs > sharing the same cable network segment attempt to renew their lease at the same > time. Ahhh... then perhaps a better fix is to change the gratitious arp routine to _not_ emit the bogus arp who-has arp-i-am when an interface is ifconfig'ed to 0.0.0.0 rather than cause the error logging code to be disabled? > > > On 07-Apr-00 Rodney W. Grimes wrote: > >> The message in question can be extremely useful in case there is IP address > >> clash on the local network. I suggest we just change the code in question to > >> ignore clashes over 0.0.0.0 address only. > > > > No, don't do that, anyone arping 0.0.0.0 on any network around here > > I sure as heck want to know about it asap! Someone someplace on > > that stupid telco's DSL bridged network is mis-configured and > > sending out arp messages for the 0 addresses. Easy enough to > > cause though: > > > > ifconfig xx0 0.0.0.0 up > > > > should do the trick... > > > ---------------------------------- > E-Mail: Alexander N. Kabaev > Date: 07-Apr-00 > Time: 14:35:14 > ---------------------------------- > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:47: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 3828E37B766; Fri, 7 Apr 2000 12:47:05 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id E37BE24E35; Fri, 7 Apr 2000 15:47:00 -0400 (EDT) Received: by osaka.louisville.edu (Postfix, from userid 15) id 1D2FA1860F; Fri, 7 Apr 2000 15:47:00 -0400 (EDT) Date: Fri, 7 Apr 2000 15:47:00 -0400 From: Keith Stevenson To: markm@freebsd.org Cc: freebsd-current@freebsd.org Subject: Perl 5.6.0 Message-ID: <20000407154659.A41477@osaka.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark, I had some free time today so I started converting perl 5.6.0 to bmake. So far, I've gotten libperl to build and plan to keep at the rest of it. Given my schedule, it will probably take me another week to get the build right and another week or so to test its integration with build/installworld. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 12:58:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id F0B2A37BABF; Fri, 7 Apr 2000 12:58:47 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA41284; Fri, 7 Apr 2000 12:58:46 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004071958.MAA41284@gndrsh.dnsmgr.net> Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004071914.MAA00729@mass.cdrom.com> from Mike Smith at "Apr 7, 2000 12:14:18 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Fri, 7 Apr 2000 12:58:46 -0700 (PDT) Cc: ak03@gte.com (Alexander N. Kabaev), dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The message in question can be extremely useful in case there is IP address > > > clash on the local network. I suggest we just change the code in question to > > > ignore clashes over 0.0.0.0 address only. > > > > No, don't do that, anyone arping 0.0.0.0 on any network around here > > I sure as heck want to know about it asap! > > Then use a tool designed for the job. You'll only get this message on a > system that's a DHCP client and currently trying to get a lease. I don't > think that you would ever get any utility from the code as it stands, so > the change is not going to affect you. I get plenty of utility from it as it stands. Any time I see one of these in a syslog I go track it down and shoot the cause. > (Note that if you were to configure a system to listen on 0.0.0.0 in > order to use this message, you would then be arping for 0.0.0.0, which > would appear to defeat your purpose.) My use of the message has nothing to do with wanting to use 0.0.0.0, it's another part of the diagnostics used in maintaining networks for people. Knowing that someone is arping 0.0.0.0 lets me know someone has jacked into one of the networks and trying to either use DHCP or has mis-configured thier box, or is trying to hack. I won't object to the change if a sysctl knob is put around it, that defaults to the way things are now, if someone doesn't care to see these messages due to being on borked networks, fine, let them turn it off. > Can I kindly suggest that you go find a bridge or a dam or some > gun-control law to go oppose for a few months? This random sniper > activity is pretty irritating. 8( It is not random sniper activity. I've been on this list since it was created. I respond when I have something to say and am silent when I have nothing to say. Also that comment is un-called for, it's on the edge of policy violation, and I expect to be respected, no matter how much you may dislike me. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 13: 1:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B633C37C314 for ; Fri, 7 Apr 2000 13:01:15 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id NAA41303; Fri, 7 Apr 2000 13:00:59 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200004072000.NAA41303@gndrsh.dnsmgr.net> Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004071926.MAA00894@papermill.wrs.com> from David Holloway at "Apr 7, 2000 12:26:27 pm" To: davidhol@windriver.com (David Holloway) Date: Fri, 7 Apr 2000 13:00:58 -0700 (PDT) Cc: mat@cs.mcgill.ca (Mathew Kanner), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No... Yes... that is just the type of thing the link local RFC reserved address space is for. > In message <20000407115730.B10907@cs.mcgill.ca>, Mathew Kanner writes: > >On Apr 07, Donn Miller wrote: > >> Since I started using a cable modem and dhclient, my system has been > >> literally overwhelmed with messages like: > >> > >> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > >> > > > > I haven't tried this but how about changing the > >/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes up > >the interface. > > > > --Mat > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 13:28:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E15DD37B535 for ; Fri, 7 Apr 2000 13:28:10 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id WAA68056; Fri, 7 Apr 2000 22:27:55 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004072027.WAA68056@zibbi.mikom.csir.co.za> Subject: Re: new device/bus stuff In-Reply-To: <38EE15B6.63DECDAD@elischer.org> from Julian Elischer at "Apr 7, 2000 10:07:02 am" To: julian@elischer.org (Julian Elischer) Date: Fri, 7 Apr 2000 22:27:55 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a howto on how to convert drivers from the old to new > form? Hmmm, I would be interested too. I would like to convert the if_ar and if_sr drivers, but they are not as straight foward as the "normal" drivers, because a chip can have two channels and a card can have two chips. Or maybe I'm just thinking too complicated about it? > > for example if_sr.c no longer shows up (or is even probed) in > 4.0-stable. I've looked here and there but I can't figure out if there > is some ISA_SHIM option needed (it's not in LINT if so). Oops, I forgot about the if_sr driver. Just change the line struct isa_driver srdriver = {srprobe, srattach_isa, "src"}; to struct isa_driver srdriver = {srprobe, srattach_isa, "sr"}; I'll do it when I remove all the frame relay hooks out of the driver. It has never been used outside SDL and they are not interested in make it available. If anyone want to use frame relay they can use the netgraph stuff. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 14:37:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 2E25F37BF48 for ; Fri, 7 Apr 2000 14:37:42 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id XAA08457 for ; Fri, 7 Apr 2000 23:32:24 +0200 Message-Id: <200004072132.XAA08457@rccr1.rccr.cremona.it> To: current@freebsd.org From: mirko.viviani@rccr.cremona.it Subject: 4.0 problems... Date: Fri, 7 Apr 2000 23:32:25 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ciao! I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev and new /etc but now I'm getting these errors: rey:~/Sources/gnustep/core/base> uname -a FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03 CEST 2000 mirko@rey.procom2.it:/mnt/amy/lpub/freebsd/usr/obj/mnt/amy/lpub/freebsd/usr/src/sys/rey i386 rey:/usr/home/mirko> top top: nlist failed rey:/usr/home/mirko> vmstat vmstat: undefined symbols: _cp_time _kmemstatistics _bucket _zlist Any ideas ? Thanks. -- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 15:12:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D27D337C1D6; Fri, 7 Apr 2000 15:12:25 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07827; Fri, 7 Apr 2000 16:12:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA02682; Fri, 7 Apr 2000 16:11:24 -0600 (MDT) Message-Id: <200004072211.QAA02682@harmony.village.org> To: Anton Berezin Subject: Re: Perl 5.6.0? Cc: "Alexander N. Kabaev" , Kris Kennaway , FreeBSD-Current , "Alexander N. Kabaev" In-reply-to: Your message of "Fri, 07 Apr 2000 13:24:34 +0200." <20000407132434.B10322@plab.ku.dk> References: <20000407132434.B10322@plab.ku.dk> Date: Fri, 07 Apr 2000 16:11:24 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000407132434.B10322@plab.ku.dk> Anton Berezin writes: : It is an issue of personal relationships and politics, not the technical : one. Tom Christiansen uses OpenBSD and advocates Perl to it (and other : way around). tchrist lives in Boulder, as does millert (Todd Miller) and the high tech comminuty here is tight nit. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 15:15: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5A4CC37C318 for ; Fri, 7 Apr 2000 15:15:01 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07836; Fri, 7 Apr 2000 16:14:59 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA02713; Fri, 7 Apr 2000 16:14:07 -0600 (MDT) Message-Id: <200004072214.QAA02713@harmony.village.org> To: Julian Elischer Subject: Re: new device/bus stuff Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Apr 2000 10:07:02 PDT." <38EE15B6.63DECDAD@elischer.org> References: <38EE15B6.63DECDAD@elischer.org> Date: Fri, 07 Apr 2000 16:14:07 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38EE15B6.63DECDAD@elischer.org> Julian Elischer writes: : Is there a howto on how to convert drivers from the old to new : form? Not completely. Just look at ep or ed drivers and do it the same way :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 15:28:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 38EB237B9F9 for ; Fri, 7 Apr 2000 15:28:53 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup2-47.iptelecom.net.ua [212.9.226.111]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id BAA03450; Sat, 8 Apr 2000 01:33:42 +0300 (EEST) Message-ID: <38EE61B6.45DF22E1@altavista.net> Date: Sat, 08 Apr 2000 01:31:18 +0300 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: mirko.viviani@rccr.cremona.it Cc: current@FreeBSD.ORG Subject: Re: 4.0 problems... References: <200004072132.XAA08457@rccr1.rccr.cremona.it> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mirko.viviani@rccr.cremona.it wrote: > Ciao! > > I've upgraded my system from 3.4 to 4.0-stable last night, with new /dev > and new /etc but now I'm getting these errors: > > rey:~/Sources/gnustep/core/base> uname -a > FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03 > CEST 2000 > mirko@rey.procom2.it:/mnt/amy/lpub/freebsd/usr/obj/mnt/amy/lpub/freebsd/usr/src/sys/rey > i386 > > rey:/usr/home/mirko> top > top: nlist failed > rey:/usr/home/mirko> vmstat > vmstat: undefined symbols: > _cp_time _kmemstatistics _bucket _zlist Hi, I heard rumors that this problem occurs when you doesn't use /boot/loader to boot your kernel. If so, it is bad practice and totally unsupported. Some day you wouldn't be able even boot it this way. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 16:19: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 3FB8A37BECC for ; Fri, 7 Apr 2000 16:18:52 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id BAA20034; Sat, 8 Apr 2000 01:13:31 +0200 Message-Id: <200004072313.BAA20034@rccr1.rccr.cremona.it> To: Maxim Sobolev Cc: current@FreeBSD.ORG From: mirko.viviani@rccr.cremona.it Subject: Re: 4.0 problems... Date: Sat, 8 Apr 2000 01:13:31 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You wrote: > > rey:/usr/home/mirko> top > > top: nlist failed > > rey:/usr/home/mirko> vmstat > > vmstat: undefined symbols: > > _cp_time _kmemstatistics _bucket _zlist > > I heard rumors that this problem occurs when you doesn't use /boot/loader to > boot your > kernel. If so, it is bad practice and totally unsupported. Some day you > wouldn't be able even boot it this way. Hmmm... Here the only not standard thing is the mbr that comes from NeXT. If I remember correctly the only time I have updated the loader was at the beginning of the 3.0 era. -- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 16:19:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 6019E37BE63 for ; Fri, 7 Apr 2000 16:19:25 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa16-56.ix.netcom.com [207.93.148.184]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA11429; Fri, 7 Apr 2000 19:19:22 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.9.3) id QAA74474; Fri, 7 Apr 2000 16:19:17 -0700 (PDT) (envelope-from tomdean) Date: Fri, 7 Apr 2000 16:19:17 -0700 (PDT) Message-Id: <200004072319.QAA74474@ix.netcom.com> From: "Thomas D. Dean" To: mirko.viviani@rccr.cremona.it Cc: current@FreeBSD.ORG In-reply-to: <200004072132.XAA08457@rccr1.rccr.cremona.it> (mirko.viviani@rccr.cremona.it) Subject: Re: 4.0 problems... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had this problem a week ago. It was caused by my booting the kernel directly. 0:da(0,a)/kernel Using 0:da(0,a)/boot/loader cures the symptoms. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 16:45:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id E7A9737BE91 for ; Fri, 7 Apr 2000 16:45:09 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf.eng.demon.net (fanf.eng.demon.net [195.11.55.89]) by internal.mail.demon.net with ESMTP id AAA01237; Sat, 8 Apr 2000 00:45:06 +0100 (BST) Received: from fanf by fanf.eng.demon.net with local (Exim 3.12 #3) id 12diQw-000Ebm-00; Sat, 08 Apr 2000 00:45:02 +0100 To: freebsd@gndrsh.dnsmgr.net From: Tony Finch Cc: current@freebsd.org Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004072000.NAA41303@gndrsh.dnsmgr.net> References: <200004071926.MAA00894@papermill.wrs.com> Message-Id: Date: Sat, 08 Apr 2000 00:45:02 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: >David Holloway wrote: >>>Mathew Kanner wrote: >>>I haven't tried this but how about changing the >>>/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes >>>up the interface. >> >> No... > >Yes... that is just the type of thing the link local RFC reserved address >space is for. No... IP address 0 is reserved for "me" so its use in DHCP makes sense. Tony. -- f.a.n.finch fanf@demon.net dot@dotat.at 393 dirt clods in your fuel rods To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 17: 7:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3B53037BB74; Fri, 7 Apr 2000 17:07:53 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA51276; Fri, 7 Apr 2000 20:07:41 -0400 (EDT) Message-Id: <200004080007.UAA51276@cs.rpi.edu> To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org, ragnar@sysabend.org, vladimir-bsd-stable@math.uic.edu, Doug@gorean.org, gallatin@cs.duke.edu, dillon@backplane.com Subject: lockd-0.2 released! Date: Fri, 07 Apr 2000 20:07:40 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I apologize profusely for the delay of this, but lockd-0.2 is out. The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz A couple of notes on this release: 1) the statd hooks to lockd are not yet done (or started) 2) you need a patched libc (for XDR64 types). I have included the xdr patch as part of this release, you need to do the following to apply it: > cd /usr/src/lib/libc/xdr > patch -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 17:13:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 055D137C2F9 for ; Fri, 7 Apr 2000 17:13:41 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id BAA26383; Sat, 8 Apr 2000 01:12:16 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sat, 8 Apr 2000 01:12:15 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: David Holloway Cc: "Rodney W. Grimes" , current@freebsd.org Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004071942.MAA01133@papermill.wrs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. Yes, RFC2131 clause 4.1 says: DHCP messages broadcast by a client prior to that client obtaining its IP address must have the source address field in the IP header set to 0. RFC951 clause 7.1 says the same thing for BOOTP (though BOOTP and DHCP are really the same protocol). However, this isn't really an excuse for issuing ARP with a source address of zero: the initial DHCP exchange is done with broadcasts (so doesn't need ARP), and after that the address is known. The problem presumably arises due to other traffic trying to go out while DHCP is still configuring the interface. This is analgous to the situation with PPP and dynamic assignment - and there isn't an easy solution because by the time you have a packet in your hand it is much too late to fix everything (you've probably got a socket bound to the bogus address, for example). On Fri, 7 Apr 2000, Rodney W. Grimes wrote: > > Ahhh... then perhaps a better fix is to change the gratitious arp > routine to _not_ emit the bogus arp who-has arp-i-am when an interface > is ifconfig'ed to 0.0.0.0 rather than cause the error logging code to be > disabled? The fix you suggest appears to have been implemented long ago: =================================================================== RCS file: /repository/src/sys/netinet/if_ether.c,v retrieving revision 1.39 retrieving revision 1.40 diff -r1.39 -r1.40 34c34 < * $Id$ --- > * $Id: if_ether.c,v 1.39 1997/02/22 09:41:24 peter Exp $ 633,634c633,635 < arprequest(ac, &(IA_SIN(ifa)->sin_addr.s_addr), < &(IA_SIN(ifa)->sin_addr.s_addr), ac->ac_enaddr); --- > if (ntohl(IA_SIN(ifa)->sin_addr.s_addr) != INADDR_ANY) > arprequest(ac, &(IA_SIN(ifa)->sin_addr.s_addr), > &(IA_SIN(ifa)->sin_addr.s_addr), ac->ac_enaddr); It is still appropriate to fix the error logging code: saying "xxx is using the same address as me" when the address in question is 0.0.0.0 is not useful: this _isn't_ a general catch for people ARP-ing for zero - it only serves that purpose when the local machine is also mis-configured. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 17:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id DC45E37BEF9 for ; Fri, 7 Apr 2000 17:28:39 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03588; Fri, 7 Apr 2000 17:32:47 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004080032.RAA03588@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gordon Cc: David Holloway , "Rodney W. Grimes" , current@freebsd.org Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-reply-to: Your message of "Sat, 08 Apr 2000 01:12:15 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 07 Apr 2000 17:32:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, 7 Apr 2000, David Holloway wrote: > > > I say with 99% certainty that assigning 0.0.0.0 to > > the interface is a requirement of dhcp. > > > > You can't stop using it and expect dhcp to work. > > Yes, RFC2131 clause 4.1 says: > > DHCP messages broadcast by a client prior to that client obtaining > its IP address must have the source address field in the IP header > set to 0. > > RFC951 clause 7.1 says the same thing for BOOTP (though BOOTP and DHCP are > really the same protocol). > > > However, this isn't really an excuse for issuing ARP with a source address > of zero: the initial DHCP exchange is done with broadcasts (so doesn't > need ARP), and after that the address is known. The problem presumably > arises due to other traffic trying to go out while DHCP is still > configuring the interface. If you look at the original error message, you'll note that it's actually due to seeing another packet which claims the same Ip address. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 17:45: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F1D6337BBD6 for ; Fri, 7 Apr 2000 17:45:04 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 UAA26183; Fri, 7 Apr 2000 20:45:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA35707; Fri, 7 Apr 2000 20:44:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Apr 2000 20:44:33 -0400 (EDT) To: "David E. Cross" Cc: freebsd-current@freebsd.org Subject: Re: lockd-0.2 released! In-Reply-To: <200004080007.UAA51276@cs.rpi.edu> References: <200004080007.UAA51276@cs.rpi.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14574.32380.49809.847803@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This might be a bit touchy, but I'm rather curious -- how will the BSDI merger affect your lockd work? It seems like your work on lockd (esp. client side & statd interoperation issues) could be speeded up if you had access to the BSDI sources.. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 18:42:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [203.2.75.105]) by hub.freebsd.org (Postfix) with ESMTP id 7B0F737BBE7 for ; Fri, 7 Apr 2000 18:42:12 -0700 (PDT) (envelope-from diskiller@borg-cube.com) Received: from bender (adlax2-058.dialup.optusnet.com.au [198.142.52.58]) by mail02.syd.optusnet.com.au (8.9.3/8.9.3) with ESMTP id LAA14697 for ; Sat, 8 Apr 2000 11:41:57 +1000 Date: Sat, 8 Apr 2000 11:11:20 +0930 (CST) From: Martin Minkus X-Sender: diskiller@bender.on.diskiller.net Cc: current@FreeBSD.ORG Subject: Re: 4.0 problems... In-Reply-To: <200004072319.QAA74474@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, Thomas D. Dean wrote: > I had this problem a week ago. > > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. Ooooohhh!! This explains why i get the same top: nlist failed error in 5.0. That machine's BIOS won't boot the hdd for some reason (beats the heck out o me, worked a few days ago), so i use a boot disk to boot FreeBSD 5.0 and Win2k. I just use 0:ad(0,a)/kernel. No wonder :) martin. -- Martin Minkus aka DiSKiLLeR Email: diskiller@borg-cube.com Web: http://www.diskiller.net I live in a world of paradox... my willingness to destroy is your chance for improvement, my hate is your faith, my failure is your victory - a victory that won't last. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 19:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from christel.heitec.net (christel.heitec.net [212.204.92.3]) by hub.freebsd.org (Postfix) with ESMTP id 65AD137B50D for ; Fri, 7 Apr 2000 19:57:17 -0700 (PDT) (envelope-from bernd.luevelsmeyer@heitec.net) Received: from heitec.net (paladin.heitec.net [212.204.92.251]) by christel.heitec.net (Postfix) with ESMTP id 15D2235480F; Sat, 8 Apr 2000 04:59:52 +0200 (CEST) Message-ID: <38EEA003.1EE1A680@heitec.net> Date: Sat, 08 Apr 2000 04:57:07 +0200 From: Bernd Luevelsmeyer Organization: Heitec AG X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: "Thomas D. Dean" Cc: mirko.viviani@rccr.cremona.it, current@FreeBSD.ORG Subject: Re: 4.0 problems... References: <200004072319.QAA74474@ix.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas D. Dean wrote: > > I had this problem a week ago. > > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. There's a PR on it, including a patch. See http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422 The patch works for me just fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 21:23:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3E91C37B651; Fri, 7 Apr 2000 21:23:18 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA57091; Sat, 8 Apr 2000 00:23:15 -0400 (EDT) Message-Id: <200004080423.AAA57091@cs.rpi.edu> To: "David E. Cross" Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, ragnar@sysabend.org, vladimir-bsd-stable@math.uic.edu, Doug@gorean.org, gallatin@cs.duke.edu, dillon@backplane.com, crossd@cs.rpi.edu Subject: lockd-0.2a released! In-Reply-To: Message from "David E. Cross" of "Fri, 07 Apr 2000 20:07:40 EDT." <200004080007.UAA51276@cs.rpi.edu> Date: Sat, 08 Apr 2000 00:23:14 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, I seem to have made a mistake in the XDR patch that I included with lockd-0.2. I have re-rolled the patch with a corrected patch. As such, and to avoid confusion, I have re-labeled this as lockd-0.2a. Once again, the URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2a.tar.gz Have fun. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 22:15:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id E1B9837BCB9 for ; Fri, 7 Apr 2000 22:15:46 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:aejDyI7uMWDngAW7EsyCdMXwL1Dw8Jjs@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA09490; Sat, 8 Apr 2000 14:13:01 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA02320; Sat, 8 Apr 2000 14:19:29 +0900 (JST) Message-Id: <200004080519.OAA02320@zodiac.mech.utsunomiya-u.ac.jp> To: Nick Hibma Cc: usb-bsd@egroups.com, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP problem? (was: Re: [usb-bsd] USB To Do list) In-reply-to: Your message of "Fri, 07 Apr 2000 14:08:25 +0100." References: Date: Sat, 08 Apr 2000 14:19:28 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What does it say before this info? In dmesg.boot (after `boot -v' at the loader prompt): uhci0: port 0xe000-0xe01f irq 15 at device 7.2 on pci0 uhci0: LegSup = 0x00000010 uhci_run: setting run=0 uhci_run: done cmd=0x80 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered Both uhci and usb drivers are statically linked to the kernel. When I connected a USB keyboard, I got the messages in my previous mail below. >Shared interrupt? No shared interrupt. Both IDE channels are disabled by BIOS, thus, irq 15 is free. After all, The USB drivers work if I run a UP kernel on the same machine. >USB does work on SMP (or at least in some cases). I know. It works on my another SMP box running 4.0-STABLE ;-< Kazu >> uhci_timeout: ii=0xc0a601c0 >> uhci_timeout: ii=0xc0a601c0 >> uhci_timeout: ii=0xc0a601c0 >> usbd_new_device: addr=2, getting first desc failed >> uhub_explore: usb_new_device failed, error=TIMEOUT >> uhub0: device problem, disabling port 1 >> >> I vaguely remember someone also reported similar problems with the SMP >> kernel in the past.... >> >> Interesting thing is that I have another SMP box, and its USB works fine. >> The version is 4.0-STABLE. The USB controller is VIA 83c572. >> >> Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 7 23:34:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id F329837BD54 for ; Fri, 7 Apr 2000 23:34:46 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e386YgF00382; Sat, 8 Apr 2000 02:34:42 -0400 (EDT) Date: Sat, 8 Apr 2000 02:34:42 -0400 (EDT) From: Trevor Johnson To: David Holloway Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004071942.MAA01133@papermill.wrs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. The Linux folks stopped doing it: 2.0 supported the net interface 0.0.0.0 IP address convention (meaning the kernel should accept all IP packets). 2.[12] don't, hence things like many bootp/dhcp configurations which used this feature break. The proper fix is to modify bootp/dhcp clients to accomplish the same thing using raw sockets instead. I think dhcpcd () already works this way, but bootpc hasn't been updated yet. --message from David Wragg (dpw@doc.ic.ac.uk) at http://www.tux.org/hypermail/linux-kernel/1999week05/0601.html __ Trevor Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 1: 7: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id C3E3037B641 for ; Sat, 8 Apr 2000 01:07:00 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id RAA27174; Sat, 8 Apr 2000 17:36:50 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id RAA11844; Sat, 8 Apr 2000 17:36:43 +0930 (CST) (envelope-from darius) 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, 08 Apr 2000 17:36:43 +0930 (CST) From: "Daniel O'Connor ,Daniel O'Connor" To: Nick Hibma Subject: Re: SMP problem? (was: Re: [usb-bsd] USB To Do list) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, FreeBSD CURRENT Mailing List , usb-bsd@egroups.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-00 Nick Hibma wrote: > What does it say before this info? Shared interrupt? I have the same problem.. The USB controller in on IRQ 10. (Its the PIIX4 one) > USB does work on SMP (or at least in some cases). Not me :) Works under UP nicely. uhci0: port 0xe000-0xe01f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered There is nothing else on irq 10. I can do tests if you need to :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 2:38:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 7497037B52A for ; Sat, 8 Apr 2000 02:38:38 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from rccr.cremona.it (modem-1-2.rccr.cremona.it [192.168.2.12]) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with ESMTP id LAA18739; Sat, 8 Apr 2000 11:33:21 +0200 Received: (from mirko@localhost) by rccr.cremona.it (8.9.3/8.9.3) id LAA01100; Sat, 8 Apr 2000 11:37:51 +0200 (MET DST) Message-Id: <200004080937.LAA01100@rccr.cremona.it> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v148.2.1) In-Reply-To: <200004072319.QAA74474@ix.netcom.com> X-Nextstep-Mailer: Mail 3.3 (Enhance 2.1) Received: by NeXT.Mailer (1.148.2.1) From: Mirko Viviani Date: Sat, 8 Apr 2000 11:37:49 +0200 To: "Thomas D. Dean" Subject: Re: 4.0 problems... Cc: current@FreeBSD.org Reply-To: mirko.viviani@rccr.cremona.it References: <200004072319.QAA74474@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, "Thomas D. Dean" wrote: > It was caused by my booting the kernel directly. > > 0:da(0,a)/kernel > > Using > > 0:da(0,a)/boot/loader > > cures the symptoms. But here it doesn't seem to work... :( 0:da(1,a)/boot/loader loaded... ok boot can't load 'kernel' no bootable kernel ok boot /kernel can't find /kernel ok ls open '/' failed: no such file or directory ok help verbose help not available ok lsdev disk @ ... disk0: BIOS A: disk1: BIOS C: disk1s3a: FFS disk1s3b: swap disk2: BIOS D: Info ?? --- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 3: 6:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail159.nifty.com (mail159.nifty.com [202.248.37.151]) by hub.freebsd.org (Postfix) with ESMTP id 2EA5337B602 for ; Sat, 8 Apr 2000 03:06:44 -0700 (PDT) (envelope-from mami@tokimeki.goldmoon.org) Received: from tokimeki.goldmoon.org by mail159.nifty.com (8.9.3+3.2W/3.7W-10/13/99) with ESMTP id TAA22032; Sat, 8 Apr 2000 19:06:39 +0900 Message-Id: <200004081006.TAA22032@mail159.nifty.com> Date: Sat, 08 Apr 2000 19:06:36 +0900 From: yuuki@goldmoon.org (Yuuki SAWADA) To: current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP problem? (was: Re: [usb-bsd] USB To Do list) In-Reply-To: In your message of "Fri, 07 Apr 2000 21:29:26 +0900" <200004071229.VAA17024@zodiac.mech.utsunomiya-u.ac.jp> References: <200004071229.VAA17024@zodiac.mech.utsunomiya-u.ac.jp> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) Emacs/20.6 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, At Fri, 07 Apr 2000 21:29:26 +0900, Kazutaka YOKOTA wrote: > I am currently having trouble with Gigabyte GA-6BXD, dual Pentium III > motherboard. If I boot a UP kernel (5.0-CURRENT), the PIIX4 USB > controller works fine. I use same mainboard GA-6BXD with dual Celeron, and I had pluged and used the IntelliMouse Explorer attached to USB hub locates on the display TOTOKU CV821X. Currently dmesg shows: uhci0: port 0xb000-0xb01f irq 11 at de vice 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Totoku Electric TMH01, class 9/0, rev 1.00/0.00, addr 2 uhub1: 5 ports with 4 removable, self powered But, MPS version configration in BIOS settings remains 1.4 by default, that makes USB not work (I don't know causes). It must be 1.1. Thanks, -- yuuki@goldmoon.org (Yuuki SAWADA) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 4:15:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from grimreaper.grondar.za (grimreaper.grondar.za [196.7.18.138]) by hub.freebsd.org (Postfix) with ESMTP id 22C7237B5D1; Sat, 8 Apr 2000 04:15:35 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grimreaper.grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.9.3/8.9.3) with ESMTP id NAA02448; Sat, 8 Apr 2000 13:15:50 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200004081115.NAA02448@grimreaper.grondar.za> To: Keith Stevenson Cc: markm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Perl 5.6.0 References: <20000407154659.A41477@osaka.louisville.edu> In-Reply-To: <20000407154659.A41477@osaka.louisville.edu> ; from Keith Stevenson "Fri, 07 Apr 2000 15:47:00 -0400." Date: Sat, 08 Apr 2000 13:15:50 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had some free time today so I started converting perl 5.6.0 to bmake. > So far, I've gotten libperl to build and plan to keep at the rest of it. > Given my schedule, it will probably take me another week to get the build > right and another week or so to test its integration with build/installworld. Cool! :-) M PS - how is the audit website going? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 4:21:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id ADFD137B63A; Sat, 8 Apr 2000 04:21:50 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id MAA29490; Sat, 8 Apr 2000 12:22:03 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sat, 8 Apr 2000 12:22:03 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Mike Smith Cc: David Holloway , "Rodney W. Grimes" , current@freebsd.org Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004080032.RAA03588@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, Mike Smith wrote: > > > > However, this isn't really an excuse for issuing ARP with a source address > > of zero: the initial DHCP exchange is done with broadcasts (so doesn't > > need ARP), and after that the address is known. The problem presumably > > arises due to other traffic trying to go out while DHCP is still > > configuring the interface. > > If you look at the original error message, you'll note that it's actually > due to seeing another packet which claims the same Ip address. Yes, but what caused that packet to be sent? Plainly, with only a single machine (and all others correctly configured) you'll never see the error. If you've got one machine configured to do DHCP, you've probably got several - and so if two boot at the same time you have the conditions to generate the error. On the other hand, this isn't really a plausible explanation for "overwhelming" numbers of errors - unless perhaps the DHCP server is dead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 5:53: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id C567A37B7B4 for ; Sat, 8 Apr 2000 05:52:57 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12dujM-000Kf4-0X; Sat, 8 Apr 2000 13:52:52 +0100 Received: from henny.qubesoft.com (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id NAA60613; Sat, 8 Apr 2000 13:55:59 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Sat, 8 Apr 2000 13:49:51 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: usb-bsd@egroups.com Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP problem? (was: Re: [usb-bsd] USB To Do list) In-Reply-To: <200004080519.OAA02320@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > uhci0: port 0xe000-0xe01f irq 15 at device 7.2 on pci0 > uhci0: LegSup = 0x00000010 ^^^^^^^^^^ PIRQDEN (IRQ's Enable) bit is not set by default. We set it right afterwards, but you you might want to check this out by copying the device_printf. The value should be 0x2000. In uhci_pci.c: * anymore if it is connected to the ports of the root hub? */ #ifdef UHCI_DEBUG if (pci_read_config(self, PCI_LEGSUP, 4)!=PCI_LEGSUP_USBPIRQDEN) device_printf(self, "LegSup = 0x%08x\n", pci_read_config(self, PCI_LEGSUP, 4)); #endif pci_write_config(self, PCI_LEGSUP, PCI_LEGSUP_USBPIRQDEN, 4); + device_printf(self, "LegSup = 0x%08x\n", + pci_read_config(self, PCI_LEGSUP, 4)); err = uhci_init(sc); > >Shared interrupt? > > No shared interrupt. Both IDE channels are disabled by BIOS, thus, > irq 15 is free. After all, The USB drivers work if I run a UP kernel > on the same machine. Um, no, it still might conflict. Could you assign 14 and 15 to legacy ISA, or move the UHCI controller onto a different interrupt and try again? > I know. It works on my another SMP box running 4.0-STABLE ;-< There is no difference between 5.0 nd 4.0 that could create this problem, so it must be a difference in hardware. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 7:28: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [194.84.67.11]) by hub.freebsd.org (Postfix) with ESMTP id 5C1A137BA6F for ; Sat, 8 Apr 2000 07:27:35 -0700 (PDT) (envelope-from osa@ozz.freebsd.org.ru) Received: (from osa@localhost) by ozz.freebsd.org.ru (8.9.3/8.9.3) id SAA44918 for current@FreeBSD.org; Sat, 8 Apr 2000 18:27:29 +0400 (MSD) (envelope-from osa) Date: Sat, 8 Apr 2000 18:27:29 +0400 From: Sergey Osokin To: current@FreeBSD.org Subject: make buildworld failed... Message-ID: <20000408182729.A44903@freebsd.org.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! After CVSup at my FreeBSD 5.0-CURRENT #0: Sun Apr 2 17:54:04 MSD 2000 i try to run make buildworld: .... /usr/src/sys/boot/i386/loader/main.c:80: warning: return type of `main' is not `int' /usr/src/sys/boot/i386/loader/main.c: In function `extract_currdev': /usr/src/sys/boot/i386/loader/main.c:163: warning: `biosdev' might be used uninitialized in this function In file included from /usr/src/sys/boot/i386/loader/../libi386/pxe.c:52: /usr/src/sys/boot/i386/loader/../libi386/pxe.h:459: conflicting types for `t_PXENV_UDP_WRITE' /usr/src/sys/boot/i386/loader/../libi386/pxe.h:448: previous declaration of `t_PXENV_UDP_WRITE' *** Error code 1 cc -O2 -pipe -march=pentium -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../ficl/i386 -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../../../../lib/libstand/ -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/loader/../../common/interp.c 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Rgdz, Sergey A. Osokin, osa@freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 7:46:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.menzor.dk (menzor.org [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id ABF5037B552; Sat, 8 Apr 2000 07:46:31 -0700 (PDT) (envelope-from morten@seeberg.dk) Received: from sos (fw.micon.dk [195.249.147.131]) by www.menzor.dk (8.8.8/8.8.8) with SMTP id RAA21579; Sat, 8 Apr 2000 17:06:05 +0200 (CEST) (envelope-from morten@seeberg.dk) Message-ID: <014801bfa168$fc5e9170$d10ba8c0@sos> From: "Morten Seeberg" To: , , Subject: New info from Compaq regarding IDA RAID controllers Date: Sat, 8 Apr 2000 16:44:44 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Note: Every user of IDA controllers on FreeBSD please read :) ) Hi, I would have released this info 2 weeks ago, but my laptop with all my personal info and mails were stolen from me, and as you know, real men do do backup - until now! :) I had a talk with the Danish Compaq Storage representative, after complaining about the lack of support for configuring Smart-2 controllers in non-Compaq equipment. He told me that the reason for this is, that Compaq politics doesn´t allow for sale of Compaq RAID storage for use in non-Compaq systems. He also told me, that he was a firm believer that this would change within 6 months (according to things he heard internally), thereby solving our problem with configuring the controllers. Now as you will find on my website, older controller can be configured in non-Compaq systems (link below). Now I´ve been encouraging people to submit their systems to me, so that I can publish them on my website, and thereby show my Compaq friends that we really like their hardware :) Because of the loss of my laptop I´ve lost all mails from you guys running the hardware out there, before I had time to update the website. Please, if you run a FreeBSD system on a Compaq RAID controller, fill out the form on http://seeberg.dk/freebsd/idaraid I then promise that I will set the time off, that it takes to test 4.0 on my RAID controller, and update the website with all the new features implemented in BSD 4.0R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 9: 5:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 106FF37BB0C for ; Sat, 8 Apr 2000 09:05:38 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa16-56.ix.netcom.com [207.93.148.184]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA00464; Sat, 8 Apr 2000 12:05:28 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.9.3) id JAA77901; Sat, 8 Apr 2000 09:05:15 -0700 (PDT) (envelope-from tomdean) Date: Sat, 8 Apr 2000 09:05:15 -0700 (PDT) Message-Id: <200004081605.JAA77901@ix.netcom.com> From: "Thomas D. Dean" To: mirko.viviani@rccr.cremona.it Cc: current@FreeBSD.ORG In-reply-to: <200004080937.LAA01100@rccr.cremona.it> (message from Mirko Viviani on Sat, 8 Apr 2000 11:37:49 +0200) Subject: Re: 4.0 problems... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try 1:da(1,a)/boot/loader :(,) 1 da 1 a /boot/loader tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 9:24:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id A6D9F37BB70; Sat, 8 Apr 2000 09:24:26 -0700 (PDT) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.251.88] by wcn4.wcnet.net with ESMTP (SMTPD32-6.00) id AD3468BB022C; Sat, 08 Apr 2000 11:24:20 -0500 Message-ID: <38EF5E0D.1B06FDD5@wcnet.net> Date: Sat, 08 Apr 2000 11:27:57 -0500 From: John Estess X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, adrian@freebsd.org, kris@freebsd.org, freebsd-fs@freebsd.org, freebsd@unix-consult.org Subject: UNIONFS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Timo, Please send your crash dump to me. While I have yet to cause a panic using unionfs, I've noticed a few interesting things - like the inability to umount(no kidding - am I doing something wrong?). Also, a whiteout file was affected. Yes, I'll recheck that - that didn't make sense. I've perused the mailing lists for the union fs and read the scant info in the D&I book, but I want to make sure there isn't a RFC or something for this fs. Is there some guidance besides the source code for this thing or is this a "let your conscience be your guide" scenario? Also, I've switched back to 4.0-Stable because I don't want to ride out the significant 5.0-Current changes coming down the pike . Since the Unionfs doesn't work anyway, can the powers-that-be update both Current and Stable in this case? It would be nice to development this in a working environment. Also, is the vfs code slated for massive overhaul soon? This thread needs to go to freebsd-fs. John Estess jestess@wcnet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 10:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from c292731-a.crvlls1.or.home.com (c292731-a.crvlls1.or.home.com [24.12.164.91]) by hub.freebsd.org (Postfix) with ESMTP id 28B9E37BBB7; Sat, 8 Apr 2000 10:44:38 -0700 (PDT) (envelope-from gablek@chem.orst.edu) Received: from chem.orst.edu (c292731-a.crvlls1.or.home.com [127.0.0.1]) by c292731-a.crvlls1.or.home.com (8.9.3/8.9.3) with ESMTP id KAA31452; Sat, 8 Apr 2000 10:44:33 -0700 (PDT) (envelope-from gablek@chem.orst.edu) Message-ID: <38EF7000.7BDAB933@chem.orst.edu> Date: Sat, 08 Apr 2000 10:44:32 -0700 From: Kevin Gable X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: CD problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have problems with cd's since upgrading from 3.4 to 4.0. I have two CD drives, one a CD-RW drive. The output from dmesg is: acd0: CD-RW at ata0-slave using PIO4 acd1: CDROM at ata1-slave using PIO4 Problem 1: (This was mentioned recently in -current concerning an HP8100) Trying to write a CD on the HP 7500 leads to the following: burncd -f /dev/acd0c data backup0408.ISO fixate next writeable LBA 0 writing from file backup0408.ISO size 537592 KB written this track 537592 KB (100%) total 537592 KB fixating CD, please wait.. burncd: ioctl(CDRIOCCLOSEDISK): Input/output error The message log has the following after this: Apr 8 09:17:12 c292731-a /kernel: acd0: CLOSE_TRACK/SESSION - ILLEGAL REQUEST asc=64 ascq=00 error=04 Apr 8 09:17:12 c292731-a /kernel: acd0: PREVENT_ALLOW - ILLEGAL REQUEST asc=64 ascq=00 error=04 Problem 2: If I am foolish enough to have a disk in either of the drives when I boot, it is impossible to mount them. For acd0c I get "device busy" unless I do a umount -f /dev/acd0c, but at that point trying to mount gives me mount_cd9660 /dev/acd0c /cdrom mount:cd9660: .: Not a directory (Prior to the umount, df shows the disk is mounted, but ls /cdrom shows nothing.) If I ensure the drives are empty on boot, I can at least mount and read disks. I have tried this with several different disks. My drives both worked fine under 3.4 (grumble, grumble...) Help or advice would be appreciated. (I know, I know, I can always wipe my system and do a clean reinstall of 3.4, but that seems like a solution dreamt up by the boys in Redmond.) Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 11:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 1A3B337B58A for ; Sat, 8 Apr 2000 11:53:39 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id UAA02338; Sat, 8 Apr 2000 20:48:19 +0200 Message-Id: <200004081848.UAA02338@rccr1.rccr.cremona.it> To: "Thomas D. Dean" Cc: current@FreeBSD.ORG From: mirko.viviani@rccr.cremona.it Subject: Re: 4.0 problems... Date: Sat, 8 Apr 2000 20:48:20 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You wrote: > Try 1:da(1,a)/boot/loader > > > :(,) > 1 da 1 a /boot/loader It does not work: Invalid label Invalid label No /boot/loader FYI I have an AHA 2940UW with 2 hd: - ID 0: NEXTSTEP - ID 1: FreeBSD and others To boot FreeBSD I change the boot ID in the 2940 bios. Other ideas ? -- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 11:55:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 6007C37B5CD for ; Sat, 8 Apr 2000 11:55:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11984; Sat, 8 Apr 2000 11:55:09 -0700 (PDT) (envelope-from dillon) Date: Sat, 8 Apr 2000 11:55:09 -0700 (PDT) From: Matthew Dillon Message-Id: <200004081855.LAA11984@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: linux emulation problems - path length restrictions in linux_rename Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed that the reserved area of the user stack that the linux emulator uses to copy modified paths is only 256 bytes long. linux_rename() makes two calls to the path munging code, which means that the two path arguments are limited in aggregate to 256 bytes, which is wrong. I've also noted another major issue with the linux emulation, and that is with shell script execution. If you are running a linux binary which then fork/exec's a shell script, the interpreter path at the top of the shell script does not undergo the path munging code, which breaks the script out of the linux emulation mode (because it runs the FreeBSD /bin/sh, /bin/csh, etc instead of the linux version). I have a fix for the latter problem. It's fairly trivial. Without a fix the only way one can reliably run serious linux apps (like an oracle install for example) under linux emulation is to chroot into /compat/linux. I would appreciate a review: http://www.backplane.com/FreeBSD4/linux-script-01.diff (No, this fix alone isn't enough to do an oracle install, it's just too grungy a beast). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 12:18:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id B691537BC07 for ; Sat, 8 Apr 2000 12:18:28 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa16-56.ix.netcom.com [207.93.148.184]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id PAA12836; Sat, 8 Apr 2000 15:18:25 -0400 (EDT) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.9.3) id MAA78182; Sat, 8 Apr 2000 12:18:12 -0700 (PDT) (envelope-from tomdean) Date: Sat, 8 Apr 2000 12:18:12 -0700 (PDT) Message-Id: <200004081918.MAA78182@ix.netcom.com> From: "Thomas D. Dean" To: mirko.viviani@rccr.cremona.it Cc: current@FreeBSD.ORG In-reply-to: <200004081848.UAA02338@rccr1.rccr.cremona.it> (mirko.viviani@rccr.cremona.it) Subject: Re: 4.0 problems... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If 1:da(1,a)/boot/loader does not work, what is in the /boot directory on da1? Is the FreeBSD root directory on da1s1a? What does 'mount' show? tomdean # ls -l /boot total 1 -r--r--r-- 1 root wheel 512 Apr 4 11:23 boot0 -r--r--r-- 1 root wheel 512 Apr 4 11:23 boot1 -r--r--r-- 1 root wheel 7680 Apr 4 11:23 boot2 -r-xr-xr-x 1 root wheel 149504 Apr 4 11:23 cdboot* drwxr-xr-x 2 root wheel 512 Apr 4 11:23 defaults/ -rw-r--r-- 1 root wheel 154 Apr 3 16:55 kernel.conf -r-xr-xr-x 1 root wheel 147456 Apr 4 11:23 loader* -r--r--r-- 1 root wheel 5951 Apr 4 11:23 loader.4th -rw-r--r-- 1 root wheel 86 Apr 3 16:55 loader.conf -r--r--r-- 1 root wheel 11908 Apr 4 11:23 loader.help -r-xr-xr-x 1 root wheel 131072 Dec 29 18:23 loader.old* -r--r--r-- 1 root wheel 342 Dec 29 18:23 loader.rc -r--r--r-- 1 root wheel 512 Apr 4 11:23 mbr -r-xr-xr-x 1 root wheel 149504 Apr 4 11:23 pxeboot* -r--r--r-- 1 root wheel 24983 Apr 4 11:23 support.4th c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 13:12:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id CA5DB37B5CD for ; Sat, 8 Apr 2000 13:12:10 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id WAA04952; Sat, 8 Apr 2000 22:06:50 +0200 Message-Id: <200004082006.WAA04952@rccr1.rccr.cremona.it> To: "Thomas D. Dean" Cc: current@FreeBSD.ORG From: mirko.viviani@rccr.cremona.it Subject: Re: 4.0 problems... Date: Sat, 8 Apr 2000 22:06:51 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You wrote: > If > > 1:da(1,a)/boot/loader > > does not work, what is in the /boot directory on da1? rey:/usr/home/mirko> list /boot total 514 drwxr-xr-x 3 root wheel 512 Apr 7 02:02 ./ drwxr-xr-x 27 root wheel 1024 Apr 7 11:29 ../ -r--r--r-- 1 root wheel 512 Apr 7 02:02 boot0 -r--r--r-- 1 root wheel 512 Apr 7 02:02 boot1 -r--r--r-- 1 root wheel 7680 Apr 7 02:02 boot2 -r-xr-xr-x 1 root wheel 145408 Apr 7 02:02 cdboot* drwxr-xr-x 2 root wheel 512 Apr 7 02:02 defaults/ -r-xr-xr-x 1 root wheel 143360 Apr 7 02:02 loader* -r--r--r-- 1 root wheel 5951 Apr 7 01:40 loader.4th -r--r--r-- 1 root wheel 11908 Apr 7 01:40 loader.help -r-xr-xr-x 1 root wheel 143360 Apr 7 01:40 loader.old* -r--r--r-- 1 root wheel 171 Jul 8 1999 loader.rc -r--r--r-- 1 root wheel 512 Apr 7 02:02 mbr -r--r--r-- 1 root wheel 24983 Apr 7 01:40 support.4th rey:/usr/home/mirko> cat /boot.config 0:da(1,a)kernel > Is the FreeBSD root directory on da1s1a? What does 'mount' show? No, da1s3a. rey:/usr/home/mirko> mount /dev/da1s3a on / (ufs, local, writes: sync 656 async 9412, reads: sync 3839 async 252) procfs on /proc (procfs, local) /dev/da1s2 on /dos (msdos, local, reads: sync 1 async 0) amy:/pub on /mnt/amy/pub (nfs) amy:/local/pub on /mnt/amy/lpub (nfs) amy:/LocalApps on /mnt/amy/LocalApps (nfs) amy:/Users on /mnt/amy/Users (nfs) -- Bye, Mirko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 13:22:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 7B02337B726; Sat, 8 Apr 2000 13:22:38 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id WAA05269; Sat, 8 Apr 2000 22:17:21 +0200 Message-Id: <200004082017.WAA05269@rccr1.rccr.cremona.it> To: current@FreeBSD.org Cc: obrien@FreeBSD.org From: mirko.viviani@rccr.cremona.it Subject: 4.0 possible compiler bug ? Date: Sat, 8 Apr 2000 22:17:21 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ciao! I'm testing the __builtin_apply() to make a patch to GNUstep, but I'm getting in troubles. rey:/tmp/tmp> gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) rey:/tmp/tmp> uname -a FreeBSD rey.procom2.it 4.0-STABLE FreeBSD 4.0-STABLE #0: Fri Apr 7 01:02:03 CEST 2000 mirko@rey.procom2.it:/mnt/amy/lpub/freebsd/usr/obj/mnt/amy/lpub/freebsd/usr/src/sys/rey i386 rey:/tmp/tmp> gcc -o test contest_i.c -Wall contest_i.c: In function `main': contest_i.c:37: warning: implicit declaration of function `printf' rey:/tmp/tmp> ./test Segmentation fault (core dumped) If the sizeof struct p is up to 8 bytes it returns the struct on the stack, else it cores. But it dumps only with the __builtin_apply(), if you define 'pippo' it works. Tested also on 3.4-stable with system gcc and it dumps. I hope I'm wrong, since I need it. Any hints ? <-*- cut -*-> #include struct p { char p[10]; }; struct p p; struct p *value = &p; struct p floatValue() { p.p[0] = 0x20; p.p[1] = 3; p.p[2] = 4; p.p[3] = 0x21; p.p[9] = 0xfe; return p; } int main() { int i; char *(imp) = (char *)floatValue; void* retframe; void* frame = __builtin_apply_args(); //malloc(116); *(void**)frame = 0; #ifdef pippo retframe=frame; floatValue(); #else retframe = __builtin_apply((void(*)(void))imp, frame, 0); #endif for(i=0; i < 40; i++) printf("%02x ", ((unsigned char *)retframe)[i]); printf("\n"); for(i=0; i < 4; i++) printf("%02x ", ((unsigned char *)&value)[i]); printf("\n"); exit(0); } <-*- cut -*-> -- Bye, Mirko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 15:51: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from oldserver.demon.nl (oldserver.demon.nl [212.238.105.241]) by hub.freebsd.org (Postfix) with ESMTP id 341E437B640 for ; Sat, 8 Apr 2000 15:50:58 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from localhost (localhost [127.0.0.1]) by oldserver.demon.nl (8.9.3/8.9.3) with ESMTP id AAA51860; Sun, 9 Apr 2000 00:50:20 +0200 (CEST) (envelope-from marc@oldserver.demon.nl) Date: Sun, 9 Apr 2000 00:50:20 +0200 (CEST) From: Marc Schneiders X-Sender: marc@propro.freebeastie.org To: Sergey Osokin Cc: current@freebsd.org Subject: Re: make buildworld failed... In-Reply-To: <20000408182729.A44903@freebsd.org.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Apr 2000, Sergey Osokin wrote: > Hello! > After CVSup at my FreeBSD 5.0-CURRENT #0: Sun Apr 2 17:54:04 MSD 2000 i try to run > make buildworld: > > .... > /usr/src/sys/boot/i386/loader/main.c:80: warning: return type of `main' is not `int' > /usr/src/sys/boot/i386/loader/main.c: In function `extract_currdev': > /usr/src/sys/boot/i386/loader/main.c:163: warning: `biosdev' might be used uninitialized in this function > In file included from /usr/src/sys/boot/i386/loader/../libi386/pxe.c:52: > /usr/src/sys/boot/i386/loader/../libi386/pxe.h:459: conflicting types for `t_PXENV_UDP_WRITE' > /usr/src/sys/boot/i386/loader/../libi386/pxe.h:448: previous declaration of `t_PXENV_UDP_WRITE' > *** Error code 1 > cc -O2 -pipe -march=pentium -DLOADER_NFS_SUPPORT -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../ficl/i386 -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../../../../lib/libstand/ -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sys/boot/i386/loader/../../common/interp.c > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > I've tried to locate an earlier message about this, as I saw no reply to the above. Couldn't find it. So: "me too!" (without the cc ... -march=pentium ... and the error 2's) Both on 4.0 current of half way January and 5.0 of a week ago. -- Marc Schneiders --- marc@venster.nl --- marc@dotje.com FreeBSD propro.freebeastie.org 5.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 15:57:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id D5E6B37B68B for ; Sat, 8 Apr 2000 15:57:23 -0700 (PDT) (envelope-from mirko.viviani@rccr.cremona.it) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id AAA09164; Sun, 9 Apr 2000 00:52:03 +0200 Message-Id: <200004082252.AAA09164@rccr1.rccr.cremona.it> To: "Thomas D. Dean" Cc: current@FreeBSD.org From: mirko.viviani@rccr.cremona.it Subject: Re: 4.0 problems... Date: Sun, 9 Apr 2000 00:52:03 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You wrote: > Try > 1:da(3,a)/boot/loader Maybe I'm a bit boring but it does not work ! :( After some tests, these are the results: 1:da(0 to 3,a)/boot/loader Invalid label Invalid label No /boot/loader 2:da(0 to 3,a)/boot/loader (NEXTSTEP disk) LBA error (don't remember correctly) 0:da(0,a)/boot/loader It does not find the kernel nor '/'. 0:da(1 to 3,a)/boot/loader It try to read from the floppy but it does not find the kernel nor '/'. 0:da(3,a)/kernel It stops after scanning aha devices and exits with mountroot: mountroot> ufs:/dev/da1s3a and it continues correctly with kmem and other stuff broken. 0:da(1,a)/kernel It load with no problems, apart the kmem stuff and other problems. Does not seem to me a good thing... -- bye, Mirko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 8 18:12:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id 7370337B55B; Sat, 8 Apr 2000 18:12:32 -0700 (PDT) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.199.76] (mheffner@mailandnews.com); Sat, 8 Apr 2000 21:12:30 -0400 X-WM-Posted-At: MailAndNews.com; Sat, 8 Apr 00 21:12:30 -0400 Content-Length: 1104 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200004082017.WAA05269@rccr1.rccr.cremona.it> Date: Sat, 08 Apr 2000 21:11:58 -0400 (EDT) Reply-To: Mike Heffner From: Mike Heffner To: mirko.viviani@rccr.cremona.it Subject: RE: 4.0 possible compiler bug ? Cc: obrien@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Apr-2000 mirko.viviani@rccr.cremona.it wrote: | Ciao! | | I'm testing the __builtin_apply() to make a patch to GNUstep, but I'm | getting | in troubles. | Since you're on the subject, there are also two other bugs with __builtin_apply() in FBSD that I know of. 1) you can't pass float values, they become written over on the stack and therefore don't get passed correctly 2) In conjunction with __builtin_return(), you cannot nest calls with __builtin_apply() or the return from the second called function with give you a floating point error. The easy hack to fix 2 is to remove FP_X_INV from the floating point mask -- but this is not the right way to do it. 1 can be fixed by passing a pointer of a float. I tried investigating into it a while back, but didn't have any luck. I know that 2 isn't a problem in 3-stable. /**************************************** * Mike Heffner * * Fredericksburg, VA ICQ# 882073 * * Sent at: 08-Apr-2000 -- 20:57:23 EST * * http://my.ispchannel.com/~mheffner * ****************************************/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message