From owner-freebsd-current Sun Aug 22 0: 8:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 5181D14D7C; Sun, 22 Aug 1999 00:08:32 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA68419; Sun, 22 Aug 1999 09:08:21 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908220708.JAA68419@gratis.grondar.za> To: Andrzej Bialecki Cc: Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 Date: Sun, 22 Aug 1999 09:08:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyway, this module was meant more as a joke, but if you guys like it so > much you could vote for putting it in the tree... My vote is a resounding "Yes!". M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 1: 2:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3ABB514F99 for ; Sun, 22 Aug 1999 01:02:10 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id AAA63126; Sun, 22 Aug 1999 00:59:06 -0700 (PDT) Date: Sun, 22 Aug 1999 01:00:37 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp Cc: Bruce Evans , jb@cimlogic.com.au, atrens@nortelnetworks.com, current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: problem with vnconfig -s labels ... In-Reply-To: <11263.935217470@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999, Poul-Henning Kamp wrote: > In message <199908210630.QAA05678@godzilla.zeta.org.au>, Bruce Evans writes: > >>Hmmm, I know this is your code, but are you sure? 8-). My understanding of > >>dkmodslice() and friends is that they manipulate dev_t entries, but don't > >>actually initialise them. Since the subr_diskslice code takes a dev_t > > > >dkmodslice() once just manipulated bits in dev_t scalars. Now that dev_t > >is a pointer, dkmodslice() has to create something for the pointer to > >point to. That something needs to be fully initialised and not created > >more than once. The initialisation is apparently incomplete. Multiple > >creation is avoided by searching the list of previously created entries. > > > >Now I understand why my memory is filling up with unused dev_t > >entries :-). subr_diskslice churns through a not insignificant part > >of the per-drive minor number space (32 slices * 8 partitions * {raw, > >buffered}), using dkmodslice to create new dev_t's. > > yes, this is the remaining sticky issue, and the only cure I know for > this and for the DEVFS issue is to relayer the slice/label processing > out of the device driver entirely. This is now almost possible to do. Ehem... it was all working before it was ripped out... that's EXACTLY what SLICE was. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 1:13: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3CD69150BB for ; Sun, 22 Aug 1999 01:13:03 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-156.skylink.it [194.185.55.156]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id KAA07906; Sun, 22 Aug 1999 10:13:05 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id KAA20942; Sun, 22 Aug 1999 10:03:43 +0200 (CEST) Date: Sun, 22 Aug 1999 10:03:43 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Chris Dillon Cc: Andrzej Bialecki , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 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 > > Anyway, this module was meant more as a joke, but if you guys like it so > > much you could vote for putting it in the tree... > > It's extremely small, so why not? Got my vote. :-) Yes, you have my 7 votes as well (my department thinks it is cool as well. Or at least that is what I think they will think, so I vote for them :-). Cheers, Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 1:22:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C9CD214F10 for ; Sun, 22 Aug 1999 01:22:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA12277; Sun, 22 Aug 1999 17:51:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA80525; Sun, 22 Aug 1999 17:50:59 +0930 (CST) Date: Sun, 22 Aug 1999 17:50:59 +0930 From: Greg Lehey To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Panic with NFSv3 on a CURRENT/SMP system Message-ID: <19990822175059.H14964@freebie.lemis.com> References: <199908220230.WAA08616@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908220230.WAA08616@lor.watermarkgroup.com>; from Luoqi Chen on Sat, Aug 21, 1999 at 10:30:54PM -0400 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 Saturday, 21 August 1999 at 22:30:54 -0400, Luoqi Chen wrote: >> I'm generating a core dump. Please note that as tara is my test machine, I use >> "INVARIANT" & "INVARIANT_SUPPORT". Should I remove them ? >> >> It seems that from my reading of the code, the panic would not had happened >> without INVARIANT. > > It is these options that caused the panic, you either remove them from the > kernel proper, or compile the kld with them. In all likelihood, these options didn't "cause" the panic, they just made another bug more visible. That's what they're there for. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 3:34:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 0DB0614ECC for ; Sun, 22 Aug 1999 03:34:12 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup2-39.iptelecom.net.ua [212.42.74.103]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA16872 for ; Sun, 22 Aug 1999 13:34:06 +0300 (EEST) Message-ID: <37BFD2E4.370EA4A4@altavista.net> Date: Sun, 22 Aug 1999 13:37:24 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Sync(8) doesn't have any effect on softupdates-enabled filesystem Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do not know if it is bug or feature, but it seems that sync(8) command doesn't really flushing write buffers for softdep enabled f/s. IMHO this behavior is not very friendly for the notebooks and ATX owners because before putting computer into sleep mode OS preferably should try to write as many as possible unflushed buffers to disk (see /etc/rc.suspend). Following is simple showcase for above described (mis)behaviour: bash-2.03# mount ; df; dd if=/dev/zero of=bigfile bs=1m count=50 ; df ; rm bigfile; sync;sync;sync ; sleep 5; df /dev/wd0s2a on / (local, noatime, soft-updates, writes: sync 3 async 913) procfs on /proc (local) Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s2a 908319 538529 297125 64% / procfs 4 4 0 100% /proc 50+0 records in 50+0 records out 52428800 bytes transferred in 10.366562 secs (5057492 bytes/sec) Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s2a 908319 590217 245437 71% / procfs 4 4 0 100% /proc Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s2a 908319 589769 245885 71% / procfs 4 4 0 100% /proc Any comments? Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 4:42:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id F11A014D11; Sun, 22 Aug 1999 04:42:29 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 862931912; Sun, 22 Aug 1999 13:40:45 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 853D9499A; Sun, 22 Aug 1999 13:40:45 +0200 (CEST) Date: Sun, 22 Aug 1999 13:40:45 +0200 (CEST) From: Andrzej Bialecki To: Kevin Day Cc: "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <4.2.0.58.19990821224324.00ac9230@nfs.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999, Kevin Day wrote: > A> Anyway, this module was meant more as a joke, but if you guys like it so > > > much you could vote for putting it in the tree... > > > >What do you mean "vote"? I was waiting for it to show up on my tree > >after a cvsup! > > I hate to keep bringing things like this up, or start a legal war, but this > screensaver is more than likely a copyright and/or trademark violation, and > bringing it into the source tree may not be a good idea. Yes, lots of > people may be making things like this, but it would probably be best to > distance FreeBSD itself from such a thing. You can trademark the title "The Matrix", but you can't trademark a common word "matrix". That's the only word I use for the name of the module. As Daniel mentioned, they even can't claim that it's their idea. So I think I can pretty safely import 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 Sun Aug 22 4:55:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 78705155DD; Sun, 22 Aug 1999 04:55:42 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id OAA05848; Sun, 22 Aug 1999 14:55:06 +0300 (EEST) Date: Sun, 22 Aug 1999 14:55:06 +0300 (EEST) From: Narvi To: Andrzej Bialecki Cc: Kevin Day , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Aug 1999, Andrzej Bialecki wrote: > On Sat, 21 Aug 1999, Kevin Day wrote: > > > > > I hate to keep bringing things like this up, or start a legal war, but this > > screensaver is more than likely a copyright and/or trademark violation, and > > bringing it into the source tree may not be a good idea. Yes, lots of > > people may be making things like this, but it would probably be best to > > distance FreeBSD itself from such a thing. > > You can trademark the title "The Matrix", but you can't trademark a common > word "matrix". That's the only word I use for the name of the module. As > Daniel mentioned, they even can't claim that it's their idea. > > So I think I can pretty safely import it. > If we wanted to be legally paranoid we would call it the "letter" saver and add as the comment the words "Falling letters like in the movie with red bills" > 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/ ---- Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 6:52:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (Postfix) with SMTP id 9B6EC14E4B for ; Sun, 22 Aug 1999 06:52:43 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA05282; Sun, 22 Aug 1999 13:15:19 +0200 From: Luigi Rizzo Message-Id: <199908221115.NAA05282@labinfo.iet.unipi.it> Subject: Re: problem with vnconfig -s labels ... To: julian@whistle.com (Julian Elischer) Date: Sun, 22 Aug 1999 13:15:18 +0200 (MET DST) Cc: phk@critter.freebsd.dk, bde@zeta.org.au, jb@cimlogic.com.au, atrens@nortelnetworks.com, current@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Aug 22, 99 01:00:18 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 303 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About the vnconfig/disklabel problem, i don't understand one thing: the sequence that causes the reboot is the same used to produce the boot floppy images. How comes that it is still possible to produce snapshots for -current ? Are they cross-built on an older version of the system ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 8: 2: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id DD86C14E69; Sun, 22 Aug 1999 08:02:03 -0700 (PDT) (envelope-from toasty@dragondata.com) Received: from dino (dino [204.137.237.6]) by home.dragondata.com (8.9.2/8.9.2) with ESMTP id KAA23426; Sun, 22 Aug 1999 10:00:45 -0500 (CDT) Message-Id: <4.2.0.58.19990822095052.00ad17c0@nfs.dragondata.com> X-Sender: toasty@nfs.dragondata.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 22 Aug 1999 10:00:37 -0500 To: Narvi , Andrzej Bialecki From: Kevin Day Subject: Re: "The Matrix" screensaver, v.0.2 Cc: Kevin Day , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sun, 22 Aug 1999, Andrzej Bialecki wrote: > > > On Sat, 21 Aug 1999, Kevin Day wrote: > > > > > > > > I hate to keep bringing things like this up, or start a legal war, > but this > > > screensaver is more than likely a copyright and/or trademark > violation, and > > > bringing it into the source tree may not be a good idea. Yes, lots of > > > people may be making things like this, but it would probably be best to > > > distance FreeBSD itself from such a thing. > > > > You can trademark the title "The Matrix", but you can't trademark a common > > word "matrix". That's the only word I use for the name of the module. As > > Daniel mentioned, they even can't claim that it's their idea. > > > > So I think I can pretty safely import it. > > > >If we wanted to be legally paranoid we would call it the "letter" saver >and add as the comment the words It's not just the name "Matrix" though. Make a screen saver of the Superman 'S' logo, and see how quickly a certain comic book company comes after you. :) Making a derivative work based on something that was in a movie probably is a copyright violation. Warner Brothers could easily say that you've copied an element from their movie (even if it's not the entire movie), and even go so far as to get a judge to get any CD-ROM distributors of FreeBSD to recall all unsold CD's, and destroy them. As for the trademark issue, it doesn't have to be a name to be trademarked. Logos, effects, and even sounds can be trademarked. I'm really not trying to be annoying about things like this, but I already had to fight for the ability to be able to use FreeBSD at work, after they discovered other copyright/trademark violations in the source tree.. (Trek, etc). "If they'll steal things here, how do we know the entire kernel isn't stolen from somewhere else?" Yes, it's silly logic, but they do sort of have a point. We're selling a product with FreeBSD embedded in it. Should some copyright/patent holder come up proving that the VM system is his, and FreeBSD stole it from him, they could legally force us to recall every machine we've sold, and replace it with non-infringing materials. Obviously we're not shipping 'trek' on our system, and wouldn't include the matrix saver anyway, but I (for completely selfish reasons) would like to keep FreeBSD distanced from anything that could possibly be infringing on anything, and let you download it from somewhere else if you want it. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 8:20:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 25E5F15495 for ; Sun, 22 Aug 1999 08:20:23 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 QAA91144; Sun, 22 Aug 1999 16:29:19 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 22 Aug 1999 16:29:19 +0100 (BST) From: Doug Rabson To: Mike Smith Cc: Warner Losh , current@freebsd.org Subject: Re: HEADS UP: at_shutdown going away In-Reply-To: <199908211951.MAA00837@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999, Mike Smith wrote: > > In message <199908190737.AAA04137@dingo.cdrom.com> Mike Smith writes: > > : Seriously though, I'm in the process of replacing a number of the > > : ad-hoc event handler callout lists in the kernel (most notably the > > : at_shutdown and apm* lists) with a generic implementation. > > > > Shouldn't the apm stuff use the new-bus hooks? I've migraded a couple > > of uses in pccard to using that now that I have newbus node to hang > > them off of... > > APM is only attached to the ISA bus for crufty reasons; I'm going to > take it off shortly and use the kernel environment to pass it options. APM is attached directly to nexus0 in the device tree. -- 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 Aug 22 8:26:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1225C1516F; Sun, 22 Aug 1999 08:26:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 QAA91151; Sun, 22 Aug 1999 16:34:42 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 22 Aug 1999 16:34:42 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: "John S. Dyson" , Alfred Perlstein , Eivind Eklund , Peter Wemm , current@freebsd.org Subject: Re: NFS HEADS UP (was Re: cvs commit: src/sys/nfs nfsm_subs.h xdr_subs.h) In-Reply-To: <199908211649.JAA73759@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 Sat, 21 Aug 1999, Matthew Dillon wrote: > :> Well, the issue with converting many of the macros to inline functions > :> is with the embedded goto's and references to variables defined outside > :> the macros. Converting them to functions would basically require > :> rewriting a huge chunk of NFS code. > :> > :My working kernel runs with a few strategic NFS macros being converted > :to functions, and the size improvement is about 50K or so (maybe more!!!) > : > :John > > If you want to port some of it in that part of the source tree will be > available in a month or two, depending on how quickly the other stuff in > my queue gets committed. I've got two patch sets currently under test > related to other NFS issues and a third one in the wings. > > Hey, speaking of NFS ... I'm working on optimizing the commit rpc and > I noticed something interesting. The commit rpc includes an offset and > a length field. > > Does anyone know why our NFS clients are sending a separate RPC for each > 8K buffer? If the dirty space is contiguous across a number of buffers > we should be able to send a *SINGLE* commit rpc to the server. That would > greatly reduce system overhead on both the client and server when writing > a large file over NFS. This would seem to be an almost free optimization > that would mesh extremely well with the nfsrv_commit optimizations I'm > making right now. > > At the moment I can saturate a 100BaseTX with NFS writes and get > 10 MBytes/sec to the platter on the server, but the cpu required on both > the client and server to do that is well over 60% of a Pentium III-450. I worked on reducing the number of commit rpcs a while ago. The best I could come up with was to use the B_CLUSTEROK flag to get vfs_bio.c to aggregate several buffers together to make a single large commit. Does that code still work? It made a big difference to the number of commit rpcs at the time. -- 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 Aug 22 9:39:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id DD73814F84 for ; Sun, 22 Aug 1999 09:39:08 -0700 (PDT) (envelope-from kfarmer@sympatico.ca) Received: from sympatico.ca (ppp12987.on.bellglobal.com [206.172.162.186]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id MAA07361; Sun, 22 Aug 1999 12:42:04 -0400 (EDT) Message-ID: <37C027DF.6338FEDA@sympatico.ca> Date: Sun, 22 Aug 1999 16:39:59 +0000 From: Kelvin Farmer X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mitsuru IWASAKI , freebsd-current@freebsd.org Subject: Re: apm problems. References: <37B8EB8F.F7DA55B1@sympatico.ca> <199908211908.EAA24374@tasogare.imasy.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mitsuru IWASAKI wrote: > Ah, If you want to reject the standby request from BIOS while the > system is active, then apmd would be useful. You can configure it like > this: > in /etc/apmd.conf: > apm_event PMEV_STANDBYREQ { > reject; Thanks. > I guess your disks are still in a SLEEP after a resume or > I/O interrupts were lost during suspend/resume or something. > Anyone suggestions? > > > ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK > > ad0: ATA-? disk at ata0 as master > > ad0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: piomode=4, dmamode=2, udmamode=-1 > > ad0: 16 secs/int, 0 depth queue, DMA mode > > If your problem is related with disks, have you tried wd device driver > instead of ata? wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: drive speed 1378KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (wd2): wd2: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S now, after resuming from apm -z, theres a pause then the message: wd2: interrupt timeout (status 58 ) wd2: timeout () DMA status 4 and things seem to work ok again. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 9:43:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id D5EF614F7F; Sun, 22 Aug 1999 09:43:41 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 8C9F51912; Sun, 22 Aug 1999 18:44:04 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 8BB9D499A; Sun, 22 Aug 1999 18:44:04 +0200 (CEST) Date: Sun, 22 Aug 1999 18:44:00 +0200 (CEST) From: Andrzej Bialecki To: Kevin Day Cc: Narvi , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <4.2.0.58.19990822095052.00ad17c0@nfs.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Aug 1999, Kevin Day wrote: [trademark violation warning] Ok, maybe you have a point - I dont know, I'm not a lawyer. But with this line of reasoning they could claim that anything using falling letters effect on your screen partly violates they trademarked special effect, which is silly. What can we do, then? Why don't we ask them politely if it's ok? 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 Sun Aug 22 9:56:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id DC9AB15518; Sun, 22 Aug 1999 09:56:37 -0700 (PDT) (envelope-from toasty@dragondata.com) Received: from dino (dino [204.137.237.6]) by home.dragondata.com (8.9.2/8.9.2) with ESMTP id LAA01802; Sun, 22 Aug 1999 11:56:31 -0500 (CDT) Message-Id: <4.2.0.58.19990822114423.00ad3cc0@nfs.dragondata.com> X-Sender: toasty@nfs.dragondata.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Sun, 22 Aug 1999 11:56:29 -0500 To: Andrzej Bialecki , Kevin Day From: Kevin Day Subject: Re: "The Matrix" screensaver, v.0.2 Cc: Narvi , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG In-Reply-To: References: <4.2.0.58.19990822095052.00ad17c0@nfs.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:44 PM 8/22/99 +0200, Andrzej Bialecki wrote: >On Sun, 22 Aug 1999, Kevin Day wrote: > >[trademark violation warning] > >Ok, maybe you have a point - I dont know, I'm not a lawyer. But with this >line of reasoning they could claim that anything using falling letters >effect on your screen partly violates they trademarked special effect, >which is silly. > >What can we do, then? Why don't we ask them politely if it's ok? > >Andrzej Bialecki While I can't speak for how Warner Brothers' lawyers are, as a general rule.. "It's much easier to say No, than it is to say Yes, and regret it later." If you ask, you'll probably get a No. It's not that you made a falling letter effect, it's that you made a falling letter effect to copy the effect in the movie, and it does look very much like what's in the movie. That could be called willful infringement. While I doubt they'd stop a fan from making something like this, (I don't know this for a fact though, see what Paramount did with Trek sites before, or Mattel with Barbie) they may be more led to taking action against a product being sold that contains it. (FreeBSD being sold by Walnut Creek and others). If this is distributed as a fan based thing, the worst they'd likely do is say "Take it down.". If this is on thousands of FreeBSD cd's, it could become a financial problem if they want to take it far enough. This is just my opinion though, and not to be used as legal advice for anyone. I just don't want FreeBSD to become a ball of intellectual property infringements. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 10: 1:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id D651315518; Sun, 22 Aug 1999 10:01:18 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id TAA01252; Sun, 22 Aug 1999 19:59:50 +0300 (EEST) Date: Sun, 22 Aug 1999 19:59:50 +0300 (EEST) From: Narvi To: Kevin Day Cc: Andrzej Bialecki , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <4.2.0.58.19990822095052.00ad17c0@nfs.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Aug 1999, Kevin Day wrote: > > >On Sun, 22 Aug 1999, Andrzej Bialecki wrote: > > > > > On Sat, 21 Aug 1999, Kevin Day wrote: > > > > > > > > > > > I hate to keep bringing things like this up, or start a legal war, > > but this > > > > screensaver is more than likely a copyright and/or trademark > > violation, and > > > > bringing it into the source tree may not be a good idea. Yes, lots of > > > > people may be making things like this, but it would probably be best to > > > > distance FreeBSD itself from such a thing. > > > > > > You can trademark the title "The Matrix", but you can't trademark a common > > > word "matrix". That's the only word I use for the name of the module. As > > > Daniel mentioned, they even can't claim that it's their idea. > > > > > > So I think I can pretty safely import it. > > > > > > >If we wanted to be legally paranoid we would call it the "letter" saver > >and add as the comment the words > > It's not just the name "Matrix" though. Make a screen saver of the Superman > 'S' logo, and see how quickly a certain comic book company comes after you. The "S" logo? We are not dealing with the "S" logo, we are dealing with a screensaver that displays an ordinary rotation S on the screen. > :) Making a derivative work based on something that was in a movie probably > is a copyright violation. Warner Brothers could easily say that you've Is it derived from the movie? Says who? It rather reminds me of an old virus that made letters fall on the screen... > copied an element from their movie (even if it's not the entire movie), and > even go so far as to get a judge to get any CD-ROM distributors of FreeBSD > to recall all unsold CD's, and destroy them. > > As for the trademark issue, it doesn't have to be a name to be trademarked. > Logos, effects, and even sounds can be trademarked. > Uhhh.... Depends on where. Sounds can't be trademarked everywhere. > I'm really not trying to be annoying about things like this, but I already > had to fight for the ability to be able to use FreeBSD at work, after they > discovered other copyright/trademark violations in the source tree.. (Trek, > etc). "If they'll steal things here, how do we know the entire kernel isn't They aren't violations until the judge says so. If it is not true in the legalsystem you are in, I suggest moving to another one. > stolen from somewhere else?" Yes, it's silly logic, but they do sort of > have a point. We're selling a product with FreeBSD embedded in it. Should > some copyright/patent holder come up proving that the VM system is his, and > FreeBSD stole it from him, they could legally force us to recall every > machine we've sold, and replace it with non-infringing materials. Obviously > we're not shipping 'trek' on our system, and wouldn't include the matrix > saver anyway, but I (for completely selfish reasons) would like to keep > FreeBSD distanced from anything that could possibly be infringing on > anything, and let you download it from somewhere else if you want it. :) > > Kevin Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 10:26:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3AC5815540 for ; Sun, 22 Aug 1999 10:26:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA80221; Sun, 22 Aug 1999 10:24:16 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 10:24:16 -0700 (PDT) From: Matthew Dillon Message-Id: <199908221724.KAA80221@apollo.backplane.com> To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem References: <37BFD2E4.370EA4A4@altavista.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I do not know if it is bug or feature, but it seems that sync(8) command :doesn't really flushing write buffers for softdep enabled f/s. IMHO this :behavior is not very friendly for the notebooks and ATX owners because :before putting computer into sleep mode OS preferably should try to :write as many as possible unflushed buffers to disk (see :/etc/rc.suspend). Following is simple showcase for above described :(mis)behaviour: It's a bug, one that I've brought up with Kirk. The problem is that the structures used internally by softupdates are not condusive to doing a hard-sync. This creates other problems, too -- when the kernel bawrite()'s a buffer softupdates may write something different to the disk and then re-dirty the buffer, so performance will drop if the buffer cache becomes saturated and you are doing a lot of ops that require softupdates-related buffer rewriting. Kirk has been looking for a solution. -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 Aug 22 10:27: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id EF40D155E0 for ; Sun, 22 Aug 1999 10:26:56 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA06850 for ; Sun, 22 Aug 1999 13:25:15 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA10752 for ; Sun, 22 Aug 1999 13:25:15 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA10748 for ; Sun, 22 Aug 1999 13:25:15 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 22 Aug 1999 13:25:15 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: gcc back? 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 just wondering but I noticed when I cvsupped a few minutes ago that gcc is back in the source tree. I was wondering if there were plans to keep gcc in the source now. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 10:38:23 1999 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 CD29714F82 for ; Sun, 22 Aug 1999 10:38:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA04138; Sun, 22 Aug 1999 19:34:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-reply-to: Your message of "Sun, 22 Aug 1999 10:24:16 PDT." <199908221724.KAA80221@apollo.backplane.com> Date: Sun, 22 Aug 1999 19:34:38 +0200 Message-ID: <4136.935343278@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908221724.KAA80221@apollo.backplane.com>, Matthew Dillon writes: > > It's a bug, one that I've brought up with Kirk. The problem is that the > structures used internally by softupdates are not condusive to doing a > hard-sync. I gues sync needs to set a flag which makes the sync'er go through all buckets with no delay and then wake the sync'ing process afterwards... -- 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 Sun Aug 22 10:51:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 47FF314F82 for ; Sun, 22 Aug 1999 10:51:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA07014; Sun, 22 Aug 1999 10:45:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908221745.KAA07014@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: gcc back? In-reply-to: Your message of "Sun, 22 Aug 1999 13:25:15 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Aug 1999 10:45:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm just wondering but I noticed when I cvsupped a few minutes ago that > gcc is back in the source tree. I was wondering if there were plans to > keep gcc in the source now. If you are tracking -current, you should be reading the commit messages. egcs has become gcc. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 10:58:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2869D14F72 for ; Sun, 22 Aug 1999 10:58:17 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA80382; Sun, 22 Aug 1999 10:58:10 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 10:58:10 -0700 (PDT) From: Matthew Dillon Message-Id: <199908221758.KAA80382@apollo.backplane.com> To: Poul-Henning Kamp Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem References: <4136.935343278@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> structures used internally by softupdates are not condusive to doing a :> hard-sync. : :I gues sync needs to set a flag which makes the sync'er go through all :buckets with no delay and then wake the sync'ing process afterwards... : :-- :Poul-Henning Kamp FreeBSD coreteam member It won't help. What needs to happen is for the VOP_FSYNC in ffs to figure out buffer<->buffer dependancies - something which is not being recorded in the structures currently. Kirk indicated to me in our discussions a few weeks ago that it would be relatively easy to figure out *some* of the dependancies and write the buffers out in the correct order, but not all of them. There are dependancies which are much more complex and not simply a matter of writing buffers out in any particular order. -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 Aug 22 11:25:47 1999 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 0647B150AE for ; Sun, 22 Aug 1999 11:25:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA04303; Sun, 22 Aug 1999 20:23:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-reply-to: Your message of "Sun, 22 Aug 1999 10:58:10 PDT." <199908221758.KAA80382@apollo.backplane.com> Date: Sun, 22 Aug 1999 20:23:33 +0200 Message-ID: <4301.935346213@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908221758.KAA80382@apollo.backplane.com>, Matthew Dillon writes: >:> structures used internally by softupdates are not condusive to doing a >:> hard-sync. >: >:I gues sync needs to set a flag which makes the sync'er go through all >:buckets with no delay and then wake the sync'ing process afterwards... >: >:-- >:Poul-Henning Kamp FreeBSD coreteam member > > It won't help. What needs to happen is for the VOP_FSYNC in ffs to > figure out buffer<->buffer dependancies But the buffer to buffer dependencies are already recorded in the sequence on the "sync-wheel" which the syncer daemon runs through, isn't 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 Sun Aug 22 11:42:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 196981559E for ; Sun, 22 Aug 1999 11:42:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA14642; Sun, 22 Aug 1999 11:39:24 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 11:39:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199908221839.LAA14642@apollo.backplane.com> To: Poul-Henning Kamp Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem References: <4301.935346213@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :But the buffer to buffer dependencies are already recorded in the :sequence on the "sync-wheel" which the syncer daemon runs through, :isn't it ? : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Only very roughly. The syncer wheel tries to order whole vnodes amoungst whole vnodes, making the distinction between vnode types VDIR, VBLK, and VREG. This helps reduce the amount of rewriting that softupdates must accomplish, but it only orders buffer dependancies in a very rough fashion. Within the dirtyblkhd list in each vnode, which lists the dirty buffers, we also do a rough ordering. If you look at reassignbuf() in vfs_subr.c you will see how this works. We attempt to sort blocks in the dirtyblkhd list and we place meta data (negative block numbers) at the end of the list instead of at the head. The idea here is to write out data blocks before writing out the meta-data. If the meta-data were to be written out first softupdates would step in and rearrange the meta-data being written to the physical media to take into account the fact that the data blocks have not yet been written. In otherwords, the metadata buffer would remain dirty. But both of these ordering cases are only rough approximations designed h to reduce the amount of work that softupdates must accomplish. Softupdates understands the concept of filesystem dependancies such as, for example, a directory entry depending on an inode. but softupdates does *NOT* directly understand 'macro' buffer<->buffer dependancies so there is no 'chain of buffers' for the flushing code to follow to get things in the right order. -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 Aug 22 11:49:11 1999 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 8A25E14C23 for ; Sun, 22 Aug 1999 11:48:59 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA04498; Sun, 22 Aug 1999 20:48:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-reply-to: Your message of "Sun, 22 Aug 1999 11:39:24 PDT." <199908221839.LAA14642@apollo.backplane.com> Date: Sun, 22 Aug 1999 20:48:20 +0200 Message-ID: <4496.935347700@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So what do we do when we halt or reboot ? -- 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 Sun Aug 22 12: 6:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2604814D60 for ; Sun, 22 Aug 1999 12:06:49 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA71413; Sun, 22 Aug 1999 11:31:03 -0700 (PDT) Date: Sun, 22 Aug 1999 11:32:38 -0700 (PDT) From: Julian Elischer To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-Reply-To: <37BFD2E4.370EA4A4@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 Sun, 22 Aug 1999, Maxim Sobolev wrote: > I do not know if it is bug or feature, but it seems that sync(8) command > doesn't really flushing write buffers for softdep enabled f/s. IMHO this > behavior is not very friendly for the notebooks and ATX owners because > before putting computer into sleep mode OS preferably should try to > write as many as possible unflushed buffers to disk (see > /etc/rc.suspend). Following is simple showcase for above described > (mis)behaviour: If you do 3 sync's WITH sleep (1) you should start to see the freeing of space. Each sync will flush out one layer on the dependency tree. The freeing of blocks is dependent on two other dependecies happenning first. Sync tells the filesystem to flush all it can at this time... things that have unsatisfied dependencies cannot happen. so try adding some sleeps. > > bash-2.03# mount ; df; dd if=/dev/zero of=bigfile bs=1m count=50 ; df ; > rm bigfile; sync;sync;sync ; sleep 5; df > /dev/wd0s2a on / (local, noatime, soft-updates, writes: sync 3 async > 913) > procfs on /proc (local) > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s2a 908319 538529 297125 64% / > procfs 4 4 0 100% /proc > 50+0 records in > 50+0 records out > 52428800 bytes transferred in 10.366562 secs (5057492 bytes/sec) > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s2a 908319 590217 245437 71% / > procfs 4 4 0 100% /proc > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s2a 908319 589769 245885 71% / > procfs 4 4 0 100% /proc > > Any comments? > > Sincerely, > > Maxim > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 12:12:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 6B348155C4 for ; Sun, 22 Aug 1999 12:11:36 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA28654; Sun, 22 Aug 1999 15:07:45 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA14344; Sun, 22 Aug 1999 15:07:44 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA14340; Sun, 22 Aug 1999 15:07:44 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 22 Aug 1999 15:07:44 -0400 (EDT) From: Kenneth Wayne Culver To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: gcc back? In-Reply-To: <199908221745.KAA07014@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm just wondering but I noticed when I cvsupped a few minutes ago that > > gcc is back in the source tree. I was wondering if there were plans to > > keep gcc in the source now. > > If you are tracking -current, you should be reading the commit messages. > > egcs has become gcc. I must have accidentally missed that one. Especially since egcs is still in my source tree after cvsupping. Ken Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 12:12:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9D82E14C19 for ; Sun, 22 Aug 1999 12:11:43 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA71629; Sun, 22 Aug 1999 11:46:28 -0700 (PDT) Date: Sun, 22 Aug 1999 11:48:02 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp Cc: Matthew Dillon , Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-Reply-To: <4301.935346213@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes and no. the sync wheel indicates buffers to wrrite in an order that will probably ensure that early dependencies are satisfied before later ones, however even after being written, a buffer might have remaining unsatisfied dependencies that required that teh on disk and in momory version sstill do not match. In this case it will have been rewritten back to the sync-wheel further in the future. What one can do is acellerate teh speed that teh daemon goes around the wheel, but you must never go faster than the disks can write, because if you queue a block that depends on something that hasn't got to disk yet, you will be queueing the old version. On Sun, 22 Aug 1999, Poul-Henning Kamp wrote: > In message <199908221758.KAA80382@apollo.backplane.com>, Matthew Dillon writes: > >:> structures used internally by softupdates are not condusive to doing a > >:> hard-sync. > >: > >:I gues sync needs to set a flag which makes the sync'er go through all > >:buckets with no delay and then wake the sync'ing process afterwards... > >: > >:-- > >:Poul-Henning Kamp FreeBSD coreteam member > > > > It won't help. What needs to happen is for the VOP_FSYNC in ffs to > > figure out buffer<->buffer dependancies > > But the buffer to buffer dependencies are already recorded in the > sequence on the "sync-wheel" which the syncer daemon runs through, > isn't 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 12:17:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 706ED14C03 for ; Sun, 22 Aug 1999 12:17:06 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA07442; Mon, 23 Aug 1999 05:15:33 +1000 Date: Mon, 23 Aug 1999 05:15:33 +1000 From: Bruce Evans Message-Id: <199908221915.FAA07442@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, phk@critter.freebsd.dk Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem Cc: current@FreeBSD.ORG, sobomax@altavista.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So what do we do when we halt or reboot ? We unmount the file system. dounmount() calls VFS_SYNC() with the MNT_WAIT flag, and then (for ffs) ffs_unmount() calls ffs_flushfiles() or softdep_flushfiles(). I'm not sure why the latter is necessary. I don't understand this problem. sync() intentionally calls VFS_SYNC() with the MNT_NOWAIT flag to stop it from waiting for i/o to complete. It's just an implementation quirk that i/o is more likely to have completed when sync() returns for the non- softdep case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 12:18:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 15DA814F52; Sun, 22 Aug 1999 12:17:41 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id UAA72076; Sun, 22 Aug 1999 20:12:33 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id LAA90546; Sun, 22 Aug 1999 11:05:11 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Sun, 22 Aug 1999 11:05:11 +0100 From: Nik Clayton To: jack Cc: stable@FreeBSD.org, current@freebsd.org Subject: Re: Docs blows up make release Message-ID: <19990822110511.A89933@kilt.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from jack on Sat, Aug 21, 1999 at 07:54:51PM -0400 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ cc'd to -current ] On Sat, Aug 21, 1999 at 07:54:51PM -0400, jack wrote: > > Will support for building release docs in English only be > revived? > For the immediate future, it looks like it will -- it seems as though we don't have the man power to make the necessary changes to sysinstall to support "installing the docs as packages", so I'm going to fix up src/release/Makefile as necessary to cope with the new directory structure. I will find this much, much, much easier if someone could e-mail me a directory listing of what the contents of ${RD}/trees looks like after the src/release/Makefile:doc.1 target has been run. This saves me having to scrounge together the necessary resources to actually be able to build a release on my home system. It would also help if someone who knows the release build stuff could let me know whether or not this directory structure is simply splatted on to the disk at install time and then left alone, or whether any other parts of the install process rely on being able to find the files in particular locations under /usr/share/doc. Many thanks, N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 12:50:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from par28.ma.ikos.com (par28.ma.ikos.com [137.103.105.228]) by hub.freebsd.org (Postfix) with ESMTP id 296C814DC0; Sun, 22 Aug 1999 12:50:40 -0700 (PDT) (envelope-from tich@par28.ma.ikos.com) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by par28.ma.ikos.com (8.8.7/8.8.7) id PAA07360; Sun, 22 Aug 1999 15:49:42 -0400 From: Richard Cownie To: obrien@freebsd.org, "David O'Brien" Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT Date: Sun, 22 Aug 1999 15:43:47 -0400 X-Mailer: KMail [version 1.1.0] Content-Type: text/plain Cc: tich@par28.ma.ikos.com, current@freebsd.org References: <19990821015744.B57737@dragon.nuxi.com> MIME-Version: 1.0 Message-Id: <99082215494200.07180@par28.ma.ikos.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999, David O'Brien wrote: > Are you saying 4.17 is better than 4.18 for debugging C++? Or are you > saying you didn't know FreeBSD comes with gdb: gdb-4.18 is badly broken on all platforms (at least for C++). You can't call methods from the gdb command line, and also it frequently freezes to the point where you have to kill the window. gdb-4.17 is much better for C++. Richard Cownie (tich@ma.ikos.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 13: 2:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id E92D614C3B for ; Sun, 22 Aug 1999 13:02:42 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 56B0C76A; Sun, 22 Aug 1999 13:02:42 -0700 (PDT) Date: Sun, 22 Aug 1999 13:02:42 -0700 From: Chris Piazza To: Kenneth Wayne Culver Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: gcc back? Message-ID: <19990822130242.A23957@norn.ca.eu.org> References: <199908221745.KAA07014@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kenneth Wayne Culver on Sun, Aug 22, 1999 at 03:07:44PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 22, 1999 at 03:07:44PM -0400, Kenneth Wayne Culver wrote: > > > I'm just wondering but I noticed when I cvsupped a few minutes ago that > > > gcc is back in the source tree. I was wondering if there were plans to > > > keep gcc in the source now. > > > > If you are tracking -current, you should be reading the commit messages. > > > > egcs has become gcc. > > I must have accidentally missed that one. Especially since egcs is still > in my source tree after cvsupping. There wasn't one. At least not here. I remember when egcs was imported it was the same thing. -Chris -- cpiazza@home.net cpiazza@FreeBSD.org "It's better to be quotable than to be honest." --Tom Stoppard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 13:13:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B911F1559D for ; Sun, 22 Aug 1999 13:13:30 -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 CA4281C1F; Mon, 23 Aug 1999 04:12:43 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Piazza Cc: Kenneth Wayne Culver , Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: gcc back? In-reply-to: Your message of "Sun, 22 Aug 1999 13:02:42 MST." <19990822130242.A23957@norn.ca.eu.org> Date: Mon, 23 Aug 1999 04:12:43 +0800 From: Peter Wemm Message-Id: <19990822201243.CA4281C1F@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Piazza wrote: > On Sun, Aug 22, 1999 at 03:07:44PM -0400, Kenneth Wayne Culver wrote: > > > > I'm just wondering but I noticed when I cvsupped a few minutes ago that > > > > gcc is back in the source tree. I was wondering if there were plans to > > > > keep gcc in the source now. > > > > > > If you are tracking -current, you should be reading the commit messages. > > > > > > egcs has become gcc. > > > > I must have accidentally missed that one. Especially since egcs is still > > in my source tree after cvsupping. > > There wasn't one. At least not here. I remember when egcs was imported > it was the same thing. Don't sweat, it's just been "un-deleted". David will be doing the transition over the next week or so via several steps so we don't loose history. Give him a bit of room to move while doing it, it's quite fiddly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 13:20:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1F7BF1559D for ; Sun, 22 Aug 1999 13:20:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA92717; Sun, 22 Aug 1999 13:20:45 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 13:20:45 -0700 (PDT) From: Matthew Dillon Message-Id: <199908222020.NAA92717@apollo.backplane.com> To: Bruce Evans Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG, sobomax@altavista.net Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem References: <199908221915.FAA07442@godzilla.zeta.org.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>So what do we do when we halt or reboot ? : :We unmount the file system. dounmount() calls VFS_SYNC() with the :MNT_WAIT flag, and then (for ffs) ffs_unmount() calls ffs_flushfiles() :or softdep_flushfiles(). I'm not sure why the latter is necessary. : :I don't understand this problem. sync() intentionally calls :VFS_SYNC() with the MNT_NOWAIT flag to stop it from waiting for :i/o to complete. It's just an implementation quirk that i/o is :more likely to have completed when sync() returns for the non- :softdep case. : :Bruce In the non-softdep case, when you write out a buffer, the buffer is truely written out and becomes clean. In the softupdates case, when you write out a buffer softupdates may *redirty* it. The buffer may *NOT* become clean. Specifically, if the buffer contains dependancies softupdates will write the non-dependant version of the buffer rather then the actual contents of the buffer, and then re-dirty the buffer as an indication that the buffer still has dependancies and cannot be marked clean yet. When you sync() with MNT_NOWAIT, a single pass through the dirty buffers occurs. In a non-softupdates filesystem all the buffers will be clean after this pass. In a softupdates filesystem many of the buffers will remain dirty after this pass - mainly when you have done complex directory interactions with file creation and deletion. When you umount, the sync code cycles through the dirty buffer list at full speed and keeps cycling until there are no dirty buffers left. Depending on how complex the dependancy lists are, this can take a very short time or it can take a very long time. It can be very inefficient, in fact, and write the same buffer out many times before all the related dependancies are flushed out. In fact, we had to fix a number of infinite-loop cases with the VOP_FSYNC code for ffs on softupdates-mounted partitions. This is why the B_SCANNED flag had to be added to the scanning code in ffs_fsync(). Changes also had to be made to getnewbuf(), the syncer (Kirk's circle queue), and other places. -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 Aug 22 13:38:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 6A0C814F8E; Sun, 22 Aug 1999 13:38:45 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id WAA03698; Sun, 22 Aug 1999 22:38:31 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id WAA01578; Sun, 22 Aug 1999 22:21:03 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990822222102.32308@breizh.teaser.fr> Date: Sun, 22 Aug 1999 22:21:02 +0200 From: Nicolas Souchu To: freebsd-current@FreeBSD.ORG Cc: soren@FreeBSD.ORG Subject: problem with the ata driver Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, hi Soren, First of all, the dump. >>>> Preloaded elf kernel "kernel" at 0xc0302000. Intel Pentium detected, installing workaround for F00F bug Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ahc0: irq 3 at device 9.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: irq 11 at device 11.0 on pci0 fxp0: irq 9 at device 12.0 on pci0 fxp0: Ethernet address 00:90:27:3d:36:f9 devclass_alloc_unit: npx0 already exists, using next available unit number isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER HP ENHANCED PCL5,PJL plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 isic0 at port 0x268 irq 5 flags 0x7 on isa0 isic0: USRobotics Sportster ISDN TA intern isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0xc268) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x268, AddrB=0x4268) pca0 at port 0x40 on isa0 pca0: PC speaker audio driver ed0 at port 0x300-0x31f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:37:f2:d0, type SMC8216/SMC8216C (16 bit) ep0: not probed (disabled) ata0: unwanted interrupt 1 status = ff i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached acd0: CDROM drive at ata0 as master acd0: drive speed 0KB/sec acd0: supported read types: acd0: Mechanism: caddy acd0: Medium: CD-ROM unknown medium Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4067MB (8330542 512 byte sectors: 255H 63S/T 518C) <<<< As you can see the drive is not properly detected. Note the "ata0: unwanted interrupt 1 status = ff" Any clue? The drive was running flawlessly with the old wdc driver and with various primary releases of the new ata driver (some, not all). Nicholas -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 13:56:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 004D8155DB for ; Sun, 22 Aug 1999 13:56:22 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA03174 for freebsd-current@FreeBSD.ORG; Sun, 22 Aug 1999 22:56:38 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E8F56870A; Sun, 22 Aug 1999 22:24:33 +0200 (CEST) Date: Sun, 22 Aug 1999 22:24:33 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Panic with NFSv3 on a CURRENT/SMP system Message-ID: <19990822222433.A11209@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199908220230.WAA08616@lor.watermarkgroup.com> <19990822175059.H14964@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <19990822175059.H14964@freebie.lemis.com>; from Greg Lehey on Sun, Aug 22, 1999 at 05:50:59PM +0930 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Greg Lehey: > In all likelihood, these options didn't "cause" the panic, they just > made another bug more visible. That's what they're there for. That's what I'm thinking but compiling NFS into the kernel "fixed" my panic. The weird part is that I'm still using INVARIANT. I don't see why the condition is not met when compiling all these together and is when using the kld. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 13:56:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 94E7E15605 for ; Sun, 22 Aug 1999 13:56:26 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA03175 for freebsd-current@FreeBSD.ORG; Sun, 22 Aug 1999 22:56:43 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6FAF3870A; Sun, 22 Aug 1999 22:26:11 +0200 (CEST) Date: Sun, 22 Aug 1999 22:26:11 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 Message-ID: <19990822222611.B11209@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: ; from Narvi on Sun, Aug 22, 1999 at 02:55:06PM +0300 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Narvi: > "Falling letters like in the movie with red bills" Pill :) That very important... The screensaver triggered me to see the movie again. Ahhhh. I love it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:20:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B33B514BE2 for ; Sun, 22 Aug 1999 14:14:50 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id RAA69608; Sun, 22 Aug 1999 17:02:00 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 22 Aug 1999 17:02:00 -0400 (EDT) From: Chuck Robey To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <19990822222611.B11209@keltia.freenix.fr> 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, 22 Aug 1999, Ollivier Robert wrote: > According to Narvi: > > "Falling letters like in the movie with red bills" > > Pill :) > > That very important... The screensaver triggered me to see the movie > again. Ahhhh. I love it. Yeah, it's gotta be the perfect hacker's movie. Maybe we *should* go approach the producers? I have gone to that movie several times, and I keep on enjoying it, so this is GOOD PR for them. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E74CE14BE2; Sun, 22 Aug 1999 14:26:21 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA03168; Sun, 22 Aug 1999 14:25:52 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nik Clayton Cc: jack , current@FreeBSD.ORG Subject: Re: Docs blows up make release In-reply-to: Your message of "Sun, 22 Aug 1999 11:05:11 BST." <19990822110511.A89933@kilt.nothing-going-on.org> Date: Sun, 22 Aug 1999 14:25:52 -0700 Message-ID: <3164.935357152@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For the immediate future, it looks like it will -- it seems as though > we don't have the man power to make the necessary changes to sysinstall > to support "installing the docs as packages", so I'm going to fix up > src/release/Makefile as necessary to cope with the new directory structure. I also should note that there's nothing to preclude supplying the docs as packages *also*, assuming that they appear in the INDEX and get built as part of Satoshi's ports build. Then the user could have at least the option of visiting the packages menu and selecting docsets, if not in english then at least all the other languages (we could leave english excluded for as long as it remains "part of the system" in the doc dist). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id BDCD314DC1 for ; Sun, 22 Aug 1999 14:34:59 -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 EB76D1C1F; Mon, 23 Aug 1999 05:34:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey Cc: Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Sun, 22 Aug 1999 17:02:00 -0400." Date: Mon, 23 Aug 1999 05:34:41 +0800 From: Peter Wemm Message-Id: <19990822213441.EB76D1C1F@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Sun, 22 Aug 1999, Ollivier Robert wrote: > > > According to Narvi: > > > "Falling letters like in the movie with red bills" > > > > Pill :) > > > > That very important... The screensaver triggered me to see the movie > > again. Ahhhh. I love it. > > Yeah, it's gotta be the perfect hacker's movie. > > Maybe we *should* go approach the producers? I have gone to that movie > several times, and I keep on enjoying it, so this is GOOD PR for them. Tell them there will be a reference to the movie web site or something. ;-) Hmm, do any of the commercial Linux dists distribute the X version? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:44:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 782AC14FC2; Sun, 22 Aug 1999 14:44:41 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-152.skylink.it [194.185.55.152]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA18162; Sun, 22 Aug 1999 23:43:17 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id VAA22671; Sun, 22 Aug 1999 21:42:41 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 22 Aug 1999 21:42:41 GMT Date: Sun, 22 Aug 1999 23:42:41 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Kevin Day Cc: Andrzej Bialecki , Narvi , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <4.2.0.58.19990822114423.00ad3cc0@nfs.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1215345684-935358161=:21921" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1215345684-935358161=:21921 Content-Type: TEXT/PLAIN; charset=US-ASCII > This is just my opinion though, and not to be used as legal advice for > anyone. I just don't want FreeBSD to become a ball of intellectual property > infringements. :) And to be honest, you are arguing well. It's also fairly easy to implement a patchset for this and keep the source separate, off the CD. All we need is one screensaver that displays the URL to all the others (attached; kld's are cool! :-). Nick -- e-Mail: hibma@skylink.it --0-1215345684-935358161=:21921 Content-Type: APPLICATION/octet-stream; name="url_saver.tar.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="url_saver.tar.gz" H4sIAJVuwDcAA+1Y61PiyBafr+SvODVaM6CRh4rOqFgVQoDUQsImwVlraooN SSN9DQmVBB+74/3b95wOCCru3g/X2bp7OeWjOd3n1+fd3czioPTujQkOy8fV KrwDqBxXy6v/F1QGODo+KpePjitHVZyuoMA7qL61YkSzJHVjgHfhYMyHE/fV dX81/z9KM4x/171mIx6wt9qjgoE9PHw9/pXD6iL+R+UK5kJlv3p89A7Kb6XQ Kv2fx38rt637J9uS9FPXbNRymA6DxL1hsWRbql2DJaPoSZJhdhWjJqnNjtKy d2uwp2//XlT7VkO3HkrFoiQVeegFM5/B2TDxi9eTyC9Ors+lv9vIDb1KVP8r MX6TPf6i/o8Oj6rL/l/dx+mDg8PjTf3/CCrt7EmwA2o0vY/51TiFvFeAyufP n8Hg3jW0yWZaoAQBiAUJxCxh8Q3zi8inKYv5PEljPpylPArBDX2YJQx4CEk0 iz0mOEMeuvE9jKJ4kshwy9MxRLH4H81SQsFewUfccwlDBjdmMGXxhKcp82Ea Rzfcx0E6dlP8wxAnCKJbHl6BF4U+J6GEUEhuwtITGleKz1RLIBotdPIi7FIT DD6ak7qoK6G6w+iGpua+IBCkMEq5x2RcwRMIEI9gltsK857qhJt6gcsn2EYz CIGP0tMo4Usnhd7YDa8yR8L+S21RasVtC23RGf4MLXgbhTNV2RzJj7zZhIWp u1C6hEGLcD6GiZuymLtBsoyOiCoBr5qxyBKnrdtgm03ni2JpgOOeZV7oDa0B 9Uuc1EDpO23Tgl9/VWyc/vgRFKOBv5eg/dKzNNsG0yIcvdvr6CiFMJZiOLpm y6Abaqff0I2WDPW+A4bpQEfv6g4uc0xZoL8UIzCzCV3NUtvIUep6R3cuxa5N 3TFoxybqo0BPsRxd7XcUC3p9q2faqCua0NBttaPoXa0h4qcbuC9oF5rhgN1W Op1Vo+oaKqTUO1oGiUbhkampDqk+H2UYKnoEdenIYPc0VaeB9ouGuivWpYwe ANU0bO3nPi7CSWgoXaWl2ZB/6gHCeu4EdDee1FqX9EOz7X7ddnSn72jQMs0G eRdszbrQVc0+hY5J/m5C39aEYg3FUcT2iILOwRVkVN/WhZt0w9Esq99zdNMo QNv8gl5ATRWUbgh/mgbZnGWBZlqXBE3+EB6X4UtbQ75FLkTzHEshx9iOpavO 6jLc0jEtYdzSXjC0VkdvaYaq0QKTgL7otlbAGOk2LdDF5hh43LYvbKfAoG44 fJGYsogg6E1QGhc66T9fj2G39XmKCPep7bn35wme227GjNXtxjZ+KElSCXtm eC+a5WQYuCFVbIQsP/6N/QvqWDnMu+YfEyqkmN+BOIDlRXu65QkWMBc9jYcp liCWkhsUQcdCngV++DGFIYOhqEVqjBFkzUTU3xwEmRO82gNPIYiia8LCHjtC gTCFk70CqGPG4qSYKbz1eHdL7pPS1I3dSXF8/oyNv+kaNjbvWcDW8F3sMN5L /jWLQxashffSNXxsXgmPXvJHw4y7wp643piHrDT1StiGpoF7/2yBz25QDn9i dvUUcT5DQsl47Szph6os/gvkhLqjR1ECivM1808fmRiTGHb6Vgdq8B6a2Dwn EZ5QiYepEmYhT05gnKbTk1Lp9va2OMIJujpH8VUJ3p+uokuP17Q8tdto4Pru FHvwIIUd15/KSw0K0u9SLvEGSTRKPZpOvFNixANCo49T/EzLOfGX+vPQp9So Qfkp3+cx88QRUIMKKoVYOMIdRiiRbZMXKhj9TqdA2CPI05paxpFyOTxlZ3EI mtJSdENoMxUQe+feDPUijTKxzAJAC8RHhN07v3EHPBxFxRs+GAXuVQIf4GKg G01z0LKUXltXbdrixR5LPKwQ1KVMsFt85LMR9NTPn0iGlrBpEoWDeeIMeLb2 br+caZHL4Q1lmC/fHR6MZOQf7pOFS3bZqxyT82mMwwIq92/kfnq6aiFcztgP 0hbD83gE2CZIFapAZOMnL2CYM6KKsyyh0zph2bVnGMU+nr1eFGAqZSIYhZt0 OBBi+Q/oyL1zFJSFaynkE3f6lYz5Jgt1xI0732wNsGm2nZalXcJ3qLcG9Y6i /lSAszOYK57fwSxLbr8uA+Czu2+IydLB+HaAUUuiuJCFfa9Cv5kczWdqYgbg XGbww9No7O7CGeyvBq1M8c89BitLM/JHI3Zvhe1URcJkvAzlea18ys9qeM0I WJjHqcIp390trDhkOsOk/LCSYJlf+G6W5DKGaP/s7JOMsl/5t4LYbp7/+LJ9 zPhFGmVTuysb1moC9C7hvzH4/n1ePLXaIm1Wi2bvCR464wFYgHfk5+n4H2Tj +mR8LRe/wzIV12bi+kRcxoE6Aeq7jNLDi57EQ56ubUmiDz2F+jMcFJy8jrNO EgMaZi0RVxJEdg7hXijw/rFfvpdhoWc2op2y0fzUpS4lSw+YBLaCd5dB12z0 O1p+ZcUSHd32dz/a/otE739LUxpd7e32WL7/xVe9L77/268eP77/y5Vj+v73 YP/gB7//4yhK/2zdP/T979xP2YsX9WSCh06Chy8+9tEtBXG9jBm++FYOJlEY J9g26Y6Z/cVSRm8GgZS7DnyqUSm3hXcgvOg+vtzx9kNv9DCaPyOfXIXwmuri Q1KI03BZopJEX0dI/6TK29CGNrShDW1oQxva0IY2tKENbejH0R+/cPYnACgA AA== --0-1215345684-935358161=:21921-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:50:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 46F7E15586 for ; Sun, 22 Aug 1999 14:50:07 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3a-6.cybcon.com [205.147.75.135]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id OAA09770 for ; Sun, 22 Aug 1999 14:49:45 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 22 Aug 1999 14:49:49 -0700 (PDT) Reply-To: wwoods@cybcon.com From: william woods To: freebsd-current@freebsd.org Subject: Downgrade ???? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, this is kinda a crazy questions, but..what the hell.... We have a production machiene that runs our internal mail server that I just inherited sysadmin'ing (the other guy quit). The problem is that it is currently running 4.0-current. I like current, I run it on my test system at home, but I don't even want to run it on a production system. How possible is it to cvsup stable ( I would blow away /uusr/src first) and then do a make world and have a 3.2-stable system or should I just re-install 3.2-stable? Understand, that this system has almost 200 user accounts for mail, so I would like to keep as much of this intact as possible..... William ---------------------------------- E-Mail: william woods Date: 22-Aug-99 Time: 14:46:02 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 14:59: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B8D114FB9 for ; Sun, 22 Aug 1999 14:58:58 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-152.skylink.it [194.185.55.152]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA18333; Sun, 22 Aug 1999 23:58:00 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id VAA22698; Sun, 22 Aug 1999 21:46:14 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 22 Aug 1999 21:46:14 GMT Date: Sun, 22 Aug 1999 23:46:14 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Peter Wemm Cc: Chuck Robey , Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <19990822213441.EB76D1C1F@overcee.netplex.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 > > Maybe we *should* go approach the producers? I have gone to that movie > > several times, and I keep on enjoying it, so this is GOOD PR for them. > > Tell them there will be a reference to the movie web site or something. ;-) Or tell them that the URL to the website appears once in a while in the mishmash, sublimal advertisements. Just make sure you speak to the marketing drones at that point :-) Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 15: 5:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 4A5D914FB9 for ; Sun, 22 Aug 1999 15:05:08 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id PAA96366 for ; Sun, 22 Aug 1999 15:04:31 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 22 Aug 1999 15:04:31 -0700 (PDT) From: Doug White To: current@freebsd.org Subject: PicoBSD major update 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 Hello, I'm committing an update of the PicoBSD code tree that should allow it to build on -STABLE and take advantage of loader's new features. Luigi Rizzo did the majority of the work, I debugged. I have use of this code thus why I'm sponsoring this commit. Significant changes include: . Now builds on -STABLE (-CURRENT is broken due to bugs) . etc directory contents centrilized in /floppy.tree instead of each type directory (can exclude & override as desired) . Removed extraneous language files (lang files for rc really necessary?) . dialog-based build tool . MFS image loads as a mfs_root module instead of compiled into kernel A MFC is pending. Please send commit-related complaints to me, and other queries either to the list or both of us. Luigi is heading for the US later this week and may be out of email range. Thanks! Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | 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 Aug 22 15: 8:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from kogge.Hanse.DE (kogge.hanse.de [192.76.134.17]) by hub.freebsd.org (Postfix) with ESMTP id CCCD8155D0 for ; Sun, 22 Aug 1999 15:07:53 -0700 (PDT) (envelope-from soenksen@planlos.hanse.de) Received: from planlos.hanse.de (uucp@localhost) by kogge.Hanse.DE (8.9.3/8.9.1) with UUCP id AAA68193 for freebsd-current@FreeBSD.org; Mon, 23 Aug 1999 00:06:39 +0200 (CEST) (envelope-from soenksen@planlos.hanse.de) Received: (from soenksen@localhost) by fury.planlos.lan (8.9.3/8.9.1) id AAA00989 for freebsd-current@FreeBSD.org; Mon, 23 Aug 1999 00:06:08 +0200 (CEST) (envelope-from soenksen) Date: Mon, 23 Aug 1999 00:06:08 +0200 From: Sebastian Soenksen To: freebsd-current@FreeBSD.org Subject: Re: "The Matrix" screensaver, v.0.2 Message-ID: <19990823000608.A978@fury.planlos.lan> References: <19990822213441.EB76D1C1F@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Nick Hibma on Sun, Aug 22, 1999 at 11:46:14PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 22, 1999 at 11:46:14PM +0200, Nick Hibma wrote: > > Tell them there will be a reference to the movie web site or something. ;-) > Or tell them that the URL to the website appears once in a while in the > mishmash, sublimal advertisements. Just make sure you speak to the > marketing drones at that point :-) and also ask them for a little donation? :> bye -- Sebastian Soenksen ; soenksen@planlos.hanse.de ; diz@IRCNet ; pgpkey available commercial use of emailadresse not allowed ; http://www.planlos.hanse.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 15:25:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from mw4.texas.net (mw4.texas.net [206.127.30.14]) by hub.freebsd.org (Postfix) with ESMTP id DF1BB155E3 for ; Sun, 22 Aug 1999 15:25:48 -0700 (PDT) (envelope-from rsnow@lgc.com) Received: from basil.dympna.COM (mnet07-40.sat.texas.net [209.99.53.40]) by mw4.texas.net (2.4/2.4) with ESMTP id RAA12720; Sun, 22 Aug 1999 17:25:14 -0500 (CDT) Received: from lgc.com (IDENT:rsnow@turbo [134.132.228.6]) by basil.dympna.COM (8.9.3/8.8.7) with ESMTP id RAA00533; Sun, 22 Aug 1999 17:25:03 -0500 (CDT) (envelope-from rsnow@lgc.com) Message-ID: <37C078BE.BF519BF0@lgc.com> Date: Sun, 22 Aug 1999 17:25:02 -0500 From: Rob Snow X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.11 i686) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) References: <199908211156.GAA20231@dyson.iquest.net.> <199908211649.JAA73759@apollo.backplane.com> <37BF4420.452C5076@gorean.org> <37BF4E63.9019DD62@lgc.com> <199908220226.TAA75601@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When copying over (FreeBSD client) the multipatch from a Linux (2.2.11) box before the patch I got this garbage in the file, -current as of 4am this morning. gzip'ed version has bad crc's. Went the other way and it worked fine (Linux client), this is v2 via amd. /etc/amd.conf: ************** /defaults fs:=${autodir}/${rhost}/root/${rfs};opts:=nosuid,nodev * rhost:=${key};type:=host;rfs:=/ Update: after reboot with new kernel I get the same thing. It's reproducible. It doesn't happen between linux boxen and doesn't happen on loopback mounts. -Rob Index: nfs/nfs_serv.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_serv.c,v retrieving revision 1.83 diff -u -r1.83 nfs_serv.c --- nfs_serv.c 1999/07/29 21:42:57 1.83 +++ nfs_serv.c 1999/08/21 07:17:06 @@ -96,6 +96,7 @@ #include #include #include +#include #include #include @@ -115,6 +116,8 @@ #define nfsdbprintf(info) #endif +#define MAX_COMMIT_COUNT (1024 * 1024) + nfstype nfsv3_type[9] = { NFNON, NFREG, NFDIR, NFBLK, NFCHR, NFLNK, NFSOCK, NFFIFO, NFNON }; #ifndef NFS_NOSERVER @@ -133,6 +136,10 @@ static int nfs_async; SYSCTL_INT(_vfs_nfs, OID_AUTO, async, CTLFLAG_RW, &nfs_async, 0, ""); +static int nfs_commit_blks; +static int nfs_commit_miss; +SYSCTL_INT(_vfs_nfs, OID_AUTO, commit_blks, CTLFLAG_RW, &nfs_commit_blks, 0, "" ); +SYSCTL_INT(_vfs_nfs, OID_AUTO, commit_miss, CTLFLAG_RW, &nfs_commit_miss, 0, "" ); static int nfsrv_access __P((struct vnode *,int,struct ucred *,int, struct proc *, int)); @@ -3624,11 +3631,73 @@ goto nfsmout; } for_ret = VOP_GETATTR(vp, &bfor, cred, procp); - if (vp->v_object && - (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { + + if (cnt > MAX_COMMIT_COUNT) { + /* + * Give up and do the whole thing + */ + if (vp->v_object && + (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@requested range. Note: we are assuming that Matthew Dillon wrote: > > Ok, I have put up the current patch set -- for patching against CURRENT > only - on my web site. > > http://www.backplane.com/FreeBSD4/ > > They contain a bit more then the NFS stuff, but it's all related to > performance. It would take me too long to try to separate them out > (this is what happens when things back-up, sorry!). > > The patches have been tested only somewhat and the one that fixes > nfssrv_commit() is not 100% complete - it doesn't sync-out the file > metadata yet, only the specific data blocks being requested by the > commit rpc. > > -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 15:26: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.mel.aone.net.au (mail.mel.aone.net.au [203.12.176.157]) by hub.freebsd.org (Postfix) with ESMTP id E0FD615618 for ; Sun, 22 Aug 1999 15:25:54 -0700 (PDT) (envelope-from Tattr@CountryRoad.com.au) Received: from ntemail.countryroad.com.au (internet_gate.countryroad.com.au [203.103.166.130]) by mail.mel.aone.net.au (8.8.8/8.8.8) with ESMTP id IAA21413 for ; Mon, 23 Aug 1999 08:25:30 +1000 (EST) Received: by NTEMAIL with Internet Mail Service (5.5.2448.0) id ; Mon, 23 Aug 1999 08:25:43 +1000 Message-ID: From: Tattr To: freebsd-current@FreeBSD.ORG Subject: help Date: Mon, 23 Aug 1999 08:25:40 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi i wonder if you can help me please? my friend has just bought a cam for his pc its a webstar and we are having a problem we have loaded the cd and the cam wont work cos it keeps saying video capture devise missing i have the same cam as he and instakked it the same way i went into my control panel to multiemedia and went to video and under it was ppc2 his does not have anything under his i think we need to download this driver (if thats what it is) can you please tell me where i get it or what to do? As you can tell neither of us know too much about computers. Thanks for any help you can give. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 15:51: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 75C3D155CD for ; Sun, 22 Aug 1999 15:50:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA77319; Sun, 22 Aug 1999 15:50:24 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 15:50:24 -0700 (PDT) From: Matthew Dillon Message-Id: <199908222250.PAA77319@apollo.backplane.com> To: Rob Snow Cc: Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :When copying over (FreeBSD client) the multipatch from a Linux (2.2.11) :box before the patch I got this garbage in the file, -current as of 4am :this morning. gzip'ed version has bad crc's. Went the other way and it :worked fine (Linux client), this is v2 via amd. : :... :Update: after reboot with new kernel I get the same thing. It's :reproducible. It doesn't happen between linux boxen and doesn't happen :on loopback mounts. : :-Rob Same thing before and after the patch, so the patch itself is not the problem? Then this is a preexisting bug of some sort. Hmm. The question is how to focus on the bug. The FreeBSD 'cp' command uses mmap(). On the linux box 'cp' the file to a different name and then try using 'cat' on the freebsd client to read it, redirected to a localfile. Then see if the local file is corrupted. Copy the file to a different name on the linux box again, and this time use 'cp' on the freebsd box to see if you get the corruption. ( the act of copying the file on the linux box to a different name removes any possibility of it being already-cached on the freebsd client when we run our test ). linux> cp multipatch-1.diff test1 fbsd> cat /test1 local1 fbsd> (check for corruption in local1) linux> cp multipatch-1.diff test2 fbsd> cp /test2 local2 fbsd> (check for corruption in local2) If the corruption occurs with 'cp' but not 'cat' then we know it has something to do with mmap. If it occurs with both commands then the corruption may be a bug on the linux server. If you can repeat the corruption using the above test the next step is to try to determine whether the bug is in the linux server or the freebsd client. I kinda suspect the linux box because there are no cache interaction issues w/ the freebsd box if the client is simply reading the file. -Matt Matthew Dillon :+ if (vp->v_object && :+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { : :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@requested range. Note: we are assuming that : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 15:52:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 971A915601 for ; Sun, 22 Aug 1999 15:52:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA77357; Sun, 22 Aug 1999 15:52:34 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 15:52:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199908222252.PAA77357@apollo.backplane.com> To: Rob Snow , Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) References: <199908222250.PAA77319@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : fbsd> cat /test1 local1 Oops. I obviously meant to redirect the output for the cat's: fbsd> cat /test1 > local1 .. etc... -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 16: 1: 1 1999 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 F2C1215247; Sun, 22 Aug 1999 16:00:58 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id F11DC1C0E; Sun, 22 Aug 1999 18:00:41 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id E26633826; Sun, 22 Aug 1999 18:00:41 -0400 (EDT) Date: Sun, 22 Aug 1999 18:00:41 -0400 (EDT) From: Bill Fumerola To: Narvi Cc: Andrzej Bialecki , Kevin Day , "Daniel C. Sobral" , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Aug 1999, Narvi wrote: > If we wanted to be legally paranoid we would call it the "letter" saver > and add as the comment the words > > "Falling letters like in the movie with red bills" Red pills, rather? -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 Aug 22 16: 4:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-77.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.77]) by hub.freebsd.org (Postfix) with ESMTP id 8447215711 for ; Sun, 22 Aug 1999 16:04:45 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (root@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA13808 for ; Sun, 22 Aug 1999 23:59:14 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA45172 for ; Mon, 23 Aug 1999 00:02:19 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199908222302.AAA45172@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.org Subject: libalias or libnat. Vote ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Aug 1999 00:02:16 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This topic was discussed last January - should libalias be renamed to libnat ? As of a few days ago, ppp(8) supports the -nat flag (as well as the -alias flag for backwards compatibility), however, it's not clear that we really want to go the whole hog and change the library name & interface too. If it's changed, things will make more sense IMHO, however it'll make life difficult for applications that already use libalias (if the change is made, do we need a libalias library with stubs into libnat ?) Votes ? Silence == no change. -- 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 Sun Aug 22 16:15:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7702B155D9 for ; Sun, 22 Aug 1999 16:15:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03847; Sun, 22 Aug 1999 16:14:54 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Subject: Re: libalias or libnat. Vote ? In-reply-to: Your message of "Mon, 23 Aug 1999 00:02:16 BST." <199908222302.AAA45172@keep.lan.Awfulhak.org> Date: Sun, 22 Aug 1999 16:14:54 -0700 Message-ID: <3843.935363694@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As of a few days ago, ppp(8) supports the -nat flag (as well as > the -alias flag for backwards compatibility), however, it's not > clear that we really want to go the whole hog and change the > library name & interface too. I've been on both sides of this issue, to be sure, but I have to say that looking at it now, I can't see any reason to change the actual name of the library right now unless we're also going to go whole-hog and change the API functions to PacketNATFoo() and such, something that would only really make sense (or be worth the effort, anyway) if we had a bunch of improvements to bring in at the same time, e.g. a significant rearchitecting effort. If we don't have anything like that planned, then simply changing the user visible flags and man pages to strongly encourage use of -nat style options rather than the deprecated -alias ones will probably be enough of a step in the right direction for now. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 16:17:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 98E9C14FCA for ; Sun, 22 Aug 1999 16:17:14 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Aug 1999 00:16:57 +0100 (BST) Date: Mon, 23 Aug 1999 00:16:56 +0100 From: David Malone To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic with NFSv3 on a CURRENT/SMP system Message-ID: <19990823001656.A39559@walton.maths.tcd.ie> References: <199908220230.WAA08616@lor.watermarkgroup.com> <19990822175059.H14964@freebie.lemis.com> <19990822222433.A11209@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990822222433.A11209@keltia.freenix.fr>; from Ollivier Robert on Sun, Aug 22, 1999 at 10:24:33PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 22, 1999 at 10:24:33PM +0200, Ollivier Robert wrote: > That's what I'm thinking but compiling NFS into the kernel "fixed" my > panic. The weird part is that I'm still using INVARIANT. I don't see why the > condition is not met when compiling all these together and is when using the > kld. As I understand it, compiling the kernel with INVARIENTS makes it uncompatable with modules compiled without INVARIENTS. The reason is probably to do with inline functions and the like - I see some inline functions in vm_zone.h which set and check certain variables only when INVARIANTS is defined. The variables seem also to be set and checked in vm_zone.c. So I suppose if you use an inline function to initialise something without INVARIENTS in a module, and then it is checked by the kernel which did have INVARIENTS defined things go boom... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 16:24:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mw4.texas.net (mw4.texas.net [206.127.30.14]) by hub.freebsd.org (Postfix) with ESMTP id 291DD14BDE for ; Sun, 22 Aug 1999 16:24:29 -0700 (PDT) (envelope-from rsnow@lgc.com) Received: from basil.dympna.COM (mnet06-08.sat.texas.net [209.99.48.176]) by mw4.texas.net (2.4/2.4) with ESMTP id SAA23261; Sun, 22 Aug 1999 18:24:04 -0500 (CDT) Received: from lgc.com (IDENT:rsnow@turbo [134.132.228.6]) by basil.dympna.COM (8.9.3/8.8.7) with ESMTP id SAA00930; Sun, 22 Aug 1999 18:23:57 -0500 (CDT) (envelope-from rsnow@lgc.com) Message-ID: <37C0868D.33EDC140@lgc.com> Date: Sun, 22 Aug 1999 18:23:57 -0500 From: Rob Snow X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.11 i686) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) References: <199908222250.PAA77319@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG linux> cp multipatch-1.diff test1 fbsd> cat test1 cat: test1: RPC struct is bad fbsd> cp test1 /tmp fbsd> cat test1 + (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@requested range. Note: we are assuming that Doesn't happen between two linux boxen. (Both 2.2.11-NFSv3) -Rob Matthew Dillon wrote: > > :When copying over (FreeBSD client) the multipatch from a Linux (2.2.11) > :box before the patch I got this garbage in the file, -current as of 4am > :this morning. gzip'ed version has bad crc's. Went the other way and it > :worked fine (Linux client), this is v2 via amd. > : > :... > :Update: after reboot with new kernel I get the same thing. It's > :reproducible. It doesn't happen between linux boxen and doesn't happen > :on loopback mounts. > : > :-Rob > > Same thing before and after the patch, so the patch itself is not the > problem? Then this is a preexisting bug of some sort. > > Hmm. The question is how to focus on the bug. The FreeBSD 'cp' command > uses mmap(). On the linux box 'cp' the file to a different name and then > try using 'cat' on the freebsd client to read it, redirected to a > localfile. Then see if the local file is corrupted. Copy the file to > a different name on the linux box again, and this time use 'cp' on the > freebsd box to see if you get the corruption. ( the act of copying the > file on the linux box to a different name removes any possibility of > it being already-cached on the freebsd client when we run our test ). > > linux> cp multipatch-1.diff test1 > fbsd> cat /test1 local1 > fbsd> (check for corruption in local1) > > linux> cp multipatch-1.diff test2 > fbsd> cp /test2 local2 > fbsd> (check for corruption in local2) > > If the corruption occurs with 'cp' but not 'cat' then we know it has > something to do with mmap. If it occurs with both commands then the > corruption may be a bug on the linux server. > > If you can repeat the corruption using the above test the next step is > to try to determine whether the bug is in the linux server or the freebsd > client. I kinda suspect the linux box because there are no cache > interaction issues w/ the freebsd box if the client is simply reading the > file. > > -Matt > Matthew Dillon > > > :+ if (vp->v_object && > :+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { > : > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@requested range. Note: we are assuming that > : > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 16:42:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.ihug.co.nz (tk1.ihug.co.nz [203.29.160.13]) by hub.freebsd.org (Postfix) with ESMTP id 7DC5914BDE for ; Sun, 22 Aug 1999 16:42:51 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p80-max9.dun.ihug.co.nz [216.132.34.116]) by smtp1.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA07111; Mon, 23 Aug 1999 11:41:59 +1200 Message-ID: <37C08AB9.CCA9B6DE@es.co.nz> Date: Mon, 23 Aug 1999 11:41:45 +1200 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Tattr Cc: freebsd-current@FreeBSD.ORG Subject: Re: help References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tattr wrote: > > Hi > i wonder if you can help me please? > my friend has just bought a cam for his pc > its a webstar and we are having a problem > we have loaded the cd and the cam wont work cos it keeps saying video > capture devise missing > i have the same cam as he and instakked it the same way > i went into my control panel to multiemedia and went to video and under it > was > ppc2 > his does not have anything under his > i think we need to download this driver (if thats what it is) > can you please tell me where i get it or what to do? > As you can tell neither of us know too much about computers. > Thanks for any help you can give. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message aye!? Is this someones idea of a joke... im laughing.. honest HANNNG ON... -current mailing list.. windows problem.. HMMMM - what kinda mental tard would do that? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 16:46:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E6F614BDE for ; Sun, 22 Aug 1999 16:46:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA00694; Sun, 22 Aug 1999 16:46:48 -0700 (PDT) (envelope-from dillon) Date: Sun, 22 Aug 1999 16:46:48 -0700 (PDT) From: Matthew Dillon Message-Id: <199908222346.QAA00694@apollo.backplane.com> To: Rob Snow Cc: Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) References: <199908222250.PAA77319@apollo.backplane.com> <37C0868D.33EDC140@lgc.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :linux> cp multipatch-1.diff test1 :fbsd> cat test1 :cat: test1: RPC struct is bad :fbsd> cp test1 /tmp :fbsd> cat test1 : :+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { : :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ :^@^@^@^@^@^@^@^@requested range. Note: we are assuming that : : :Doesn't happen between two linux boxen. (Both 2.2.11-NFSv3) : :-Rob Yah, but that doesn't mean much. What we have here is some sort of protocol confusion. Try an NFSv2 mount and see if that works. If the problem is protocol confusion there's a good 70% chance that the confusion is on the side of the linux server, since linux's NFSv3 implementation is *very* recent. It would take someone with a protocol analyzer to track it down. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 17:29:36 1999 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 A744214C23 for ; Sun, 22 Aug 1999 17:29:26 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA33566; Sun, 22 Aug 1999 17:27:10 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908230027.RAA33566@gndrsh.dnsmgr.net> Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: from Chuck Robey at "Aug 22, 1999 05:02:00 pm" To: chuckr@picnic.mat.net (Chuck Robey) Date: Sun, 22 Aug 1999 17:27:09 -0700 (PDT) Cc: roberto@keltia.freenix.fr (Ollivier Robert), 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 > On Sun, 22 Aug 1999, Ollivier Robert wrote: > > > According to Narvi: > > > "Falling letters like in the movie with red bills" > > > > Pill :) > > > > That very important... The screensaver triggered me to see the movie > > again. Ahhhh. I love it. > > Yeah, it's gotta be the perfect hacker's movie. > > Maybe we *should* go approach the producers? I have gone to that movie > several times, and I keep on enjoying it, so this is GOOD PR for them. Good idea, the approach for approval to distrubute this presented to the marketing department has a strong leverage on the legal department, in that they can't just take the easy road of saying ``no'' when the marketing department is going ``yes, yes.. this would be good for revenue''. -- Rod Grimes - KD7CAX - (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 Sun Aug 22 17:40:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from mw5.texas.net (mw5.texas.net [206.127.30.15]) by hub.freebsd.org (Postfix) with ESMTP id 6B47B14F08 for ; Sun, 22 Aug 1999 17:40:42 -0700 (PDT) (envelope-from rsnow@lgc.com) Received: from basil.dympna.COM (mnet07-78.sat.texas.net [209.99.53.78]) by mw5.texas.net (2.4/2.4) with ESMTP id TAA20233; Sun, 22 Aug 1999 19:39:09 -0500 (CDT) Received: from lgc.com (IDENT:rsnow@turbo [134.132.228.6]) by basil.dympna.COM (8.9.3/8.8.7) with ESMTP id TAA01262; Sun, 22 Aug 1999 19:39:00 -0500 (CDT) (envelope-from rsnow@lgc.com) Message-ID: <37C09823.D36A0D7C@lgc.com> Date: Sun, 22 Aug 1999 19:38:59 -0500 From: Rob Snow X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.11 i686) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Doug , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Patches available (was Re: NFS HEADS UP) References: <199908222250.PAA77319@apollo.backplane.com> <37C0868D.33EDC140@lgc.com> <199908222346.QAA00694@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyways, I have to agree with you on the protocol issue. I cannot even get mounts to work reliably between the Linux boxes, they seem to get confused. Basically, looks like recent Linux NFS Server is broken, therefore, I'm guessing that the error I saw was on that side of the house. FYI, my Bonnie numbers from Linux client look about the same as pre-patch, in my initial tests. -Rob Matthew Dillon wrote: > > :linux> cp multipatch-1.diff test1 > :fbsd> cat test1 > :cat: test1: RPC struct is bad > :fbsd> cp test1 /tmp > :fbsd> cat test1 > : > :+ (vp->v_object->flags & OBJ_MIGHTBEDIRTY)) { > : > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > :^@^@^@^@^@^@^@^@requested range. Note: we are assuming that > : > : > :Doesn't happen between two linux boxen. (Both 2.2.11-NFSv3) > : > :-Rob > > Yah, but that doesn't mean much. What we have here is some sort of > protocol confusion. Try an NFSv2 mount and see if that works. > > If the problem is protocol confusion there's a good 70% chance that the > confusion is on the side of the linux server, since linux's NFSv3 > implementation is *very* recent. It would take someone with a protocol > analyzer to track it down. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 17:48: 2 1999 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 9502C154BC; Sun, 22 Aug 1999 17:47:40 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id UAA23102; Sun, 22 Aug 1999 20:46:42 -0400 (EDT) Date: Sun, 22 Aug 1999 20:46:42 -0400 (EDT) From: Daniel Eischen Message-Id: <199908230046.UAA23102@pcnet1.pcnet.com> To: obrien@FreeBSD.ORG, tich@ma.ikos.com Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT Cc: current@FreeBSD.ORG, tich@par28.ma.ikos.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Cownie wrote: > On Sat, 21 Aug 1999, David O'Brien wrote: > > Are you saying 4.17 is better than 4.18 for debugging C++? Or are you > > saying you didn't know FreeBSD comes with gdb: > > gdb-4.18 is badly broken on all platforms (at least for C++). You can't > call methods from the gdb command line, and also it frequently freezes > to the point where you have to kill the window. gdb-4.17 is much better > for C++. There's a port for gdb-4.17 sitting on my ftp site at: ftp://ftp.pcnet.com/users/eischen/FreeBSD/gdb-4.17-port.tar.gz The port includes changes made to the gdb in our base system (then, Mar 1999, it was gdb-4.15 I believe). I haven't made any further updates to it since. You're welcome to play around with it. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 17:52:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DC5A514D8C for ; Sun, 22 Aug 1999 17:52:29 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA70305; Sun, 22 Aug 1999 20:45:07 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 22 Aug 1999 20:45:07 -0400 (EDT) From: Chuck Robey To: "Rodney W. Grimes" Cc: Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <199908230027.RAA33566@gndrsh.dnsmgr.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, 22 Aug 1999, Rodney W. Grimes wrote: > > On Sun, 22 Aug 1999, Ollivier Robert wrote: > > > > > According to Narvi: > > > > "Falling letters like in the movie with red bills" > > > > > > Pill :) > > > > > > That very important... The screensaver triggered me to see the movie > > > again. Ahhhh. I love it. > > > > Yeah, it's gotta be the perfect hacker's movie. > > > > Maybe we *should* go approach the producers? I have gone to that movie > > several times, and I keep on enjoying it, so this is GOOD PR for them. > > Good idea, the approach for approval to distrubute this presented to > the marketing department has a strong leverage on the legal department, > in that they can't just take the easy road of saying ``no'' when > the marketing department is going ``yes, yes.. this would be > good for revenue''. OK, then, I'll do it "with unofficial but general approval of many FreeBSDers" (which is what I'll tell the folks). Too bad I don't live in LA anymore, I used to know the right folks to go to. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 19:33:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail4.lig.bellsouth.net (mail4.lig.bellsouth.net [205.152.0.32]) by hub.freebsd.org (Postfix) with ESMTP id 3875B14EEA for ; Sun, 22 Aug 1999 19:33:34 -0700 (PDT) (envelope-from gljohns@bellsouth.net) Received: from gforce.johnson.home (host-216-76-174-185.msy.bellsouth.net [216.76.174.185]) by mail4.lig.bellsouth.net (3.3.2/8.9.3) with ESMTP id WAA10459 for ; Sun, 22 Aug 1999 22:32:51 -0400 (EDT) Received: (from glenn@localhost) by gforce.johnson.home (8.9.3/8.9.3) id VAA65448; Sun, 22 Aug 1999 21:28:48 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Sun, 22 Aug 1999 21:28:47 -0500 To: william woods Cc: freebsd-current@FreeBSD.ORG Subject: Re: Downgrade ???? Message-ID: <19990822212847.A48327@gforce.johnson.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from william woods on Sun, Aug 22, 1999 at 02:49:49PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 22, 1999 at 02:49:49PM -0700, william woods wrote: > OK, this is kinda a crazy questions, but..what the hell.... > ...snip... > How possible is it to cvsup stable ( I would blow away /uusr/src > first) and then do a make world and have a 3.2-stable system or should > I just re-install 3.2-stable? I think it would be better if you did a binary upgrade. That way you don't have to worry about build tools from CURRENT doing something funny to your 'make world'. In either case you will want to remove libraries from CURRENT not present in STABLE and any that may have had a version bump for CURRENT, ie. libfoo.so.1 in STABLE was libfoo.so.2 in CURRENT. Any ports that you compiled with c++ in CURRENT will have to be recompiled after you downgrade. Those are the types of issues I think you will run into. Doing the binary upgrade should preserve your /etc so your password database should be OK. It would of course be prudent to back up /etc anyway. Good luck. -- Glenn Johnson gljohns@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 22:24:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B6943156CC; Sun, 22 Aug 1999 22:24:46 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11ImaG-000BE2-00; Mon, 23 Aug 1999 07:23:52 +0200 From: Sheldon Hearn To: Doug Cc: obrien@freebsd.org, current@freebsd.org Subject: Re: REQ: Test /etc/rc clean-up In-reply-to: Your message of "Fri, 20 Aug 1999 11:59:05 MST." Date: Mon, 23 Aug 1999 07:23:52 +0200 Message-ID: <43153.935385832@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Aug 1999 11:59:05 MST, Doug wrote: > However I'd REALLY like to emphasize again that if we're going to do > this the proper fix is to use case wherever possible. > > I have offered several times to do the work if it has a chance of > being committed, that offer is still good. Hi Doug, The several times before, did folks come up with objections, or was it just a case of mass apathy? :-) I don't want to piss into the wind of wisdom from ages past, but I like the sound of what you're suggesting. I guess if there _are_ sensible objections, they'll crop up when you send a diff? Oh, and thanks for the offer. You no doubt understand that this is probably not something that'll get pumped straight into CURRENT without a goodly number of "works for me" messages in prviate mail from folks using lotsa weird setups. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 22 23:27:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E043314DD1; Sun, 22 Aug 1999 23:27:17 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA49585; Mon, 23 Aug 1999 08:27:15 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908230627.IAA49585@freebsd.dk> Subject: Re: problem with the ata driver In-Reply-To: <19990822222102.32308@breizh.teaser.fr> from Nicolas Souchu at "Aug 22, 1999 10:21: 2 pm" To: nsouch@teaser.fr (Nicolas Souchu) Date: Mon, 23 Aug 1999 08:27:15 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, soren@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nicolas Souchu wrote: > acd0: CDROM drive at ata0 as master > acd0: drive speed 0KB/sec > acd0: supported read types: > acd0: Mechanism: caddy > acd0: Medium: CD-ROM unknown medium > > Any clue? > > The drive was running flawlessly with the old wdc driver and with various > primary releases of the new ata driver (some, not all). Hmm, looks like the timeout I've chosen for timing out on the probes *might* be too short for some devices.. -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 Aug 23 0: 1:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id AFAB4155F1 for ; Mon, 23 Aug 1999 00:01:03 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id RAA03444; Mon, 23 Aug 1999 17:00:01 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma003425; Mon, 23 Aug 99 16:59:55 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id QAA03897 for ; Mon, 23 Aug 1999 16:59:55 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id QAA20940 for ; Mon, 23 Aug 1999 16:59:56 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id QAA08609; Mon, 23 Aug 1999 16:59:53 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908230659.QAA08609@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Softupdates reliability? Date: Mon, 23 Aug 1999 16:59:53 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a recent crash on my home box that makes me question the reliablity of softupdates. My home box runs 3.2-R, but as far as I can determine, there have been no reliablity fixes to softupdates since then. So a failure here should be relevant to -current. Hardware: K6-2/300, 64MB ECC SDRAM, Fireport40 (ncr 875j) U/W SCSI, 2xDCAS-34330 + 1xDDRS-39130 disks (all U/W from IBM), Toshiba CD, Exabyte 8200. This hardware has run happily for a long time, and often experiences high load. I was extracting from the Exabyte to the DDRS disk while applying a CTM update from that disk against one of the DCAS disks when it crashed. The Exabyte went wonky (took about 6 goes to get the tape ejected) and the rest of the disk system locked up. The SCSI adapter was so confused I had to power down. When it recovered, there was an "UNEXPECTED SOFT UPDATE INCONSISTENCY" which turned out to be a referenced but unallocated inode, and two zero size directories. In all, a couple dozen files ended up in lost+found. So, what do people think is the most likely: 1) the SCSI adapter told the disk to write crap to a couple places on the disk (breaking an inode and some directories) 2) softupdates can't handle a sudden interruption (leaving many unwritten blocks) If many other people have survived sudden power loss or similar no-sync type crashes, I'll be happy to believe option 1 caused my problem. If not, then perhaps softupdates still has incomplete handling of dependencies. Of course, if it is option 1, I'm keen to know what's wrong with the current driver! Stephen. By the way, I have a 3.2-stable machine at work on which I installed revision 1.27 of softupdates, instead of the 1.20.2.2 == 1.24 normally included. It hasn't crashed ever :-) so I don't know if that will cause me problems. It works fine in normal operation. Perhaps it is time to MFC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 0:43:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4A78B14D30 for ; Mon, 23 Aug 1999 00:43:03 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11IojC-000C6k-00; Mon, 23 Aug 1999 09:41:14 +0200 From: Sheldon Hearn To: "Jordan K. Hubbard" Cc: Harlan Stenn , Doug , Warner Losh , current@FreeBSD.ORG Subject: Re: REQ: Test /etc/rc clean-up In-reply-to: Your message of "Sat, 21 Aug 1999 16:59:38 MST." <81513.935279978@localhost> Date: Mon, 23 Aug 1999 09:41:14 +0200 Message-ID: <46545.935394074@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999 16:59:38 MST, "Jordan K. Hubbard" wrote: > http://www.freebsd.org/~jkh/etc.diffs.fix-it-right > > Which I've sent to Sheldon for review but haven't heard anything > back from him yet. Universal Week-end Time. :-P 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 Aug 23 0:44:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 46ECC155D5 for ; Mon, 23 Aug 1999 00:44:53 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11IomR-000C7r-00; Mon, 23 Aug 1999 09:44:35 +0200 From: Sheldon Hearn To: Doug Cc: freebsd-current@FreeBSD.ORG, dbaker@distributed.net Subject: Re: Weird differences in rc5 behavior on -current vs. -stable In-reply-to: Your message of "Sat, 21 Aug 1999 19:11:33 MST." <37BF5C55.519542EF@gorean.org> Date: Mon, 23 Aug 1999 09:44:35 +0200 Message-ID: <46614.935394275@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 Aug 1999 19:11:33 MST, Doug wrote: > I have a 3.2-Stable and a 4.0-Current system at home, both > running rc5des. On both systems I set the priority in the rc5 options > menu to '0', indicating lowest possible priority. On the -Stable > system it's running at nice level '0', but it seems to be taking > advantage of the idprio stuff since in general my system seems much > "snappier," than when I was running 2.2.8 on the exact same machine. I think you'll find PR 12381 explains these results quite well. The fix bde applied to CURRENT and backported to STABLE were not backported to RELENG_2_2. If you look at the difference between RELENG_2_2 and RELENG_3, I think you'll see why. :-) 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 Aug 23 0:52:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id 84E4D1562E for ; Mon, 23 Aug 1999 00:52:19 -0700 (PDT) (envelope-from john.saunders@nlc.net.au) Received: (qmail 29964 invoked by uid 1000); 23 Aug 1999 17:49:58 +1000 From: "John Saunders" Date: Mon, 23 Aug 1999 17:49:58 +1000 (EST) To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: NTP daemon and Y2K issues 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 noticed that -stable is running xntpd 3.4e and possible -current is the same (although I can't check at the moment). The following was sent to a sysadmin mailing list (SAGE-AU). -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 04-1822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ Just when you thought it was safe ... For those of you feeling quite happy running XNTP version 3.x, you might want to upgrade to the latest NTP (currently 4.0.97) to be squeaky clean with your Y2K team. There have been changes made to the source after the AT&T Labs "Freeware Y2K Certification Project" had been at it. >From the file NOTES.y2kfixes in the top level source directory: 1) Errors were found in improper use of tm_year within struct tm, calculations that did not support year 2000 as a leap year (it truly is, despite any unchanged comments remaining in the NTP source), and some incorrect date calculations, while not traditional Y2K errors, would break in the year 2000. 2) include/ntpd.h Added some definitions and documentation about the right way of doing things. Definitions used by most, if not all, of the Y2K repairs. Not huge changes, but there probably will be a problem. For those that just want to check the relevant files, you can check the online CVS repository at http://maccarony.ntp.org/cgi-bin/cvsweb.cgi/ntp/ Please note that the SAGE-AU mirror only has XNTP 3.x, so you will need to go further afield until NTP 4 is being mirrored. John Warburton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 1: 9:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from enya.clari.net.au (enya.clari.net.au [203.8.14.116]) by hub.freebsd.org (Postfix) with ESMTP id 1F58814D49; Mon, 23 Aug 1999 01:09:31 -0700 (PDT) (envelope-from danny@freebsd.org) Received: from localhost (danny@localhost) by enya.clari.net.au (8.9.2/8.9.1) with ESMTP id SAA32068; Mon, 23 Aug 1999 18:08:56 +1000 (EST) (envelope-from danny@freebsd.org) X-Authentication-Warning: enya.clari.net.au: danny owned process doing -bs Date: Mon, 23 Aug 1999 18:08:56 +1000 (EST) From: "Daniel O'Callaghan" X-Sender: danny@enya.clari.net.au To: John Saunders Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: NTP daemon and Y2K issues 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, 23 Aug 1999, John Saunders wrote: > I noticed that -stable is running xntpd 3.4e and possible -current is the I y2k-fixed xntpd in FreeBSD in January. Have a look at CVS log for src/usr.sbin/xntpd/parse/util/dcfd.c 1.6 Tue Jan 12 19:37:30 1999 UTC by danny CVS Tags: RELENG_3_2_PAO_BP, RELENG_3_2_0_RELEASE, RELENG_3_1_0_RELEASE, RELENG_3_BP, HEAD, RELENG_3, RELENG_3_2_PAO Diffs to 1.5 Fix leap year calculations, including 2000. The code was broken for all years! Reviewed by: , To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 5:19:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by hub.freebsd.org (Postfix) with ESMTP id DB90C156A0 for ; Mon, 23 Aug 1999 05:19:21 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix10.ix.netcom.com (8.8.4/8.8.4) id HAA21136 for ; Mon, 23 Aug 1999 07:19:18 -0500 (CDT) Received: from sji-ca5-176.ix.netcom.com(209.109.234.176) by dfw-ix10.ix.netcom.com via smap (V1.3) id rma021112; Mon Aug 23 07:19:12 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id FAA07566; Mon, 23 Aug 1999 05:19:08 -0700 (PDT) Date: Mon, 23 Aug 1999 05:19:08 -0700 (PDT) Message-Id: <199908231219.FAA07566@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 Subject: whither readline.h? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear currenters, /usr/include/readline/readline.h (and whatever else that's supposed to be in that directory) has been missing from 4-current and 3-stable snaps for awhile. Does anyone know why? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 6:25:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1158B15438; Mon, 23 Aug 1999 06:25:07 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA08079; Mon, 23 Aug 1999 22:24:41 +0900 (JST) Message-ID: <37C14B68.A9D10D1B@newsguy.com> Date: Mon, 23 Aug 1999 22:23:52 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kevin Day Cc: Andrzej Bialecki , Narvi , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 References: <4.2.0.58.19990822095052.00ad17c0@nfs.dragondata.com> <4.2.0.58.19990822114423.00ad3cc0@nfs.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > ... > If this is distributed as a fan based thing, the worst they'd likely do is > say "Take it down.". If this is on thousands of FreeBSD cd's, it could > become a financial problem if they want to take it far enough. > > This is just my opinion though, and not to be used as legal advice for > anyone. I just don't want FreeBSD to become a ball of intellectual property > infringements. :) Let me retract the Ghost in the Shell statement. I just checked, and my memory played tricks on me. It was a different letter effect. :-) Andrzej, can you somehow turn it into a parody? If you can make it into a parody, then it's legal. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org - Come on. - Where are we going? - To get what you came for. - What's that? - Me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 7:10:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 88A3B14CF7; Mon, 23 Aug 1999 07:10:06 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 2C51B1912; Mon, 23 Aug 1999 16:09:24 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 2B32949D3; Mon, 23 Aug 1999 16:09:24 +0200 (CEST) Date: Mon, 23 Aug 1999 16:09:24 +0200 (CEST) From: Andrzej Bialecki To: "Daniel C. Sobral" Cc: Kevin Day , Narvi , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <37C14B68.A9D10D1B@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, Daniel C. Sobral wrote: > Kevin Day wrote: > > > ... > > If this is distributed as a fan based thing, the worst they'd likely do is > > say "Take it down.". If this is on thousands of FreeBSD cd's, it could > > become a financial problem if they want to take it far enough. > > > > This is just my opinion though, and not to be used as legal advice for > > anyone. I just don't want FreeBSD to become a ball of intellectual property > > infringements. :) > > Let me retract the Ghost in the Shell statement. I just checked, and > my memory played tricks on me. It was a different letter effect. :-) > > Andrzej, can you somehow turn it into a parody? If you can make it > into a parody, then it's legal. I can't think of any... What could be funny in such primitive effect anyway? Besides, I'm not that sure I want to spend more time on that. Feel free to hack it, guys, if you like it - it's BSD license, you know... 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 Aug 23 7:18:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id AB16E14D12 for ; Mon, 23 Aug 1999 07:18:26 -0700 (PDT) (envelope-from npp@swamp.dk) Received: from nicolai (firewall.bfc.dk [194.192.110.10]) by distortion.dk (8.9.1/8.9.1) with SMTP id RAA26937 for ; Mon, 23 Aug 1999 17:58:40 +0200 (CEST) (envelope-from npp@swamp.dk) Message-ID: <002201beed72$569d5a00$5b861dac@wmdata.dk> From: "Nicolai Petri" To: Subject: Linux compat: Lotus Notes Server 5 for linux ? Date: Mon, 23 Aug 1999 16:17:44 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01BEED83.07CCE600" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0019_01BEED83.07CCE600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I tried subject but got only coredumps in return.. Anybody who was = luckier ?? -------- Nicolai Petri ------=_NextPart_000_0019_01BEED83.07CCE600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I tried subject but got only = coredumps in=20 return.. Anybody who was luckier ??
 
--------
Nicolai Petri
 
------=_NextPart_000_0019_01BEED83.07CCE600-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 7:18:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 0A43115738 for ; Mon, 23 Aug 1999 07:18:43 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 66367 invoked from network); 23 Aug 1999 14:18:33 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 23 Aug 1999 14:18:33 -0000 Date: Mon, 23 Aug 1999 09:18:33 -0500 (CDT) From: David Scheidt To: Stephen McKay Cc: freebsd-current@freebsd.org Subject: Re: Softupdates reliability? In-Reply-To: <199908230659.QAA08609@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, Stephen McKay wrote: > I was extracting from the Exabyte to the DDRS disk while applying a CTM > update from that disk against one of the DCAS disks when it crashed. The > Exabyte went wonky (took about 6 goes to get the tape ejected) and the > rest of the disk system locked up. The SCSI adapter was so confused I > had to power down. > > When it recovered, there was an "UNEXPECTED SOFT UPDATE INCONSISTENCY" > which turned out to be a referenced but unallocated inode, and two zero size > directories. In all, a couple dozen files ended up in lost+found. I had this happen a couple times in 3.-2 stable. I tried to load a buggy kernel module, and hosed a cylinder group. As near as I could tell, the kernel module was writing to memory at random, and corrupted the buffer chain. I couldn't quite reproduce this enough to get a good handle on exactly what was going on, though. > If many other people have survived sudden power loss or similar no-sync type > crashes, I'll be happy to believe option 1 caused my problem. If not, then > perhaps softupdates still has incomplete handling of dependencies. Of course, > if it is option 1, I'm keen to know what's wrong with the current driver! I have survived a number of power loss crashes, with no problems. I tend to suspect the SCSI driver did something bad. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 7:31:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.datasys.net (kiwi.datasys.net [209.119.145.2]) by hub.freebsd.org (Postfix) with ESMTP id A3C5B14C9E for ; Mon, 23 Aug 1999 07:31:10 -0700 (PDT) (envelope-from ayan@kiwi.datasys.net) Received: (from ayan@localhost) by kiwi.datasys.net (8.9.3/8.9.3) id KAA94337; Mon, 23 Aug 1999 10:29:58 -0400 (EDT) (envelope-from ayan) Date: Mon, 23 Aug 1999 10:29:58 -0400 (EDT) From: Ayan George Message-Id: <199908231429.KAA94337@kiwi.datasys.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: asami@cs.berkeley.edu (Satoshi Asami), current@FreeBSD.ORG Subject: Re: whither readline.h? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check under: /usr/src/gnu/lib/libreadline/readline -Ayan George [ Quoted message from Satoshi Asami, received Aug 23, 5:19am.] > Dear currenters, > > /usr/include/readline/readline.h (and whatever else that's supposed to > be in that directory) has been missing from 4-current and 3-stable > snaps for awhile. Does anyone know why? > > Satoshi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message [ End message from Satoshi Asami. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 7:32:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from distortion.dk (distortion.dk [195.249.147.156]) by hub.freebsd.org (Postfix) with ESMTP id 7671A14BCE for ; Mon, 23 Aug 1999 07:32:42 -0700 (PDT) (envelope-from npp@swamp.dk) Received: from nicolai (firewall.bfc.dk [194.192.110.10]) by distortion.dk (8.9.1/8.9.1) with SMTP id SAA27052 for ; Mon, 23 Aug 1999 18:14:02 +0200 (CEST) (envelope-from npp@swamp.dk) Message-ID: <001301beed74$7be77c30$5b861dac@wmdata.dk> From: "Nicolai Petri" To: Subject: re: Linux compat: Lotus Notes Server 5 for linux ? Date: Mon, 23 Aug 1999 16:33:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I tried subject but got only coredumps in return.. Anybody who was > luckier ?? > > I've gotten notes for solaris worling. Version 4.6 Nice... How well does it run ?? And did you install it on FreeBSD or Solaris ?? (I don't have a solaris so I prefer not to do it that way :) ------- Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 8:21: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 4D11714D21; Mon, 23 Aug 1999 08:20:50 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Mon, 23 Aug 1999 11:19:17 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 23 Aug 1999 08:19:14 -0700 (PDT) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 23 Aug 1999 11:19:14 -0400 (EDT) To: "Daniel O'Callaghan" Cc: John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: NTP daemon and Y2K issues In-Reply-To: "Daniel O'Callaghan"'s (danny@FreeBSD.ORG) message dated Mon, 23 Aug 1999 18:08:56. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Mon, 23 Aug 1999 11:19:14 -0400 Message-ID: <14766.935421554@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dcfd is only used for some parse clock applications. There were a number of other Y2K-type changes made by the AT&T patch. Also, a *huge* number of bugfixes and improvements have been made to the NTP code since xntp3.4anything. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 8:41:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (oreilly131.oreilly.mbaynet.com [206.55.242.131]) by hub.freebsd.org (Postfix) with ESMTP id 0E08A1586D for ; Mon, 23 Aug 1999 08:41:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA00802; Mon, 23 Aug 1999 08:35:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908231535.IAA00802@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Mon, 23 Aug 1999 22:23:52 +0900." <37C14B68.A9D10D1B@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Aug 1999 08:35:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kevin Day wrote: > > > ... > > If this is distributed as a fan based thing, the worst they'd likely do is > > say "Take it down.". If this is on thousands of FreeBSD cd's, it could > > become a financial problem if they want to take it far enough. > > > > This is just my opinion though, and not to be used as legal advice for > > anyone. I just don't want FreeBSD to become a ball of intellectual property > > infringements. :) > > Let me retract the Ghost in the Shell statement. I just checked, and > my memory played tricks on me. It was a different letter effect. :-) > > Andrzej, can you somehow turn it into a parody? If you can make it > into a parody, then it's legal. Just make it a port, for crap's sake, and distribute it from Poland. By the time WB's American lawyers work out where you are on the map, the statute of limitations will have expired and you'll be fine. But it's not going into the tree, no. I think Kevin's point and the experiences we had with Hasbro should already have convinced people of that much. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 9:56:58 1999 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 CD1401568C for ; Mon, 23 Aug 1999 09:56:55 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-3-69.ucdavis.edu [169.237.17.69]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA16607 for ; Mon, 23 Aug 1999 09:55:26 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA53206 for current@freebsd.org; Mon, 23 Aug 1999 09:55:24 -0700 (PDT) (envelope-from obrien) Date: Mon, 23 Aug 1999 09:54:51 -0700 From: "David O'Brien" To: Satoshi Asami Subject: Re: whither readline.h? Message-ID: <19990823095451.A52275@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199908231219.FAA07566@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199908231219.FAA07566@silvia.hip.berkeley.edu>; from Satoshi Asami on Mon, Aug 23, 1999 at 05:19:08AM -0700 X-Operating-System: FreeBSD 4.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 > /usr/include/readline/readline.h (and whatever else that's supposed to > be in that directory) has been missing from 4-current and 3-stable > snaps for awhile. Does anyone know why? I just checked that cd /usr/src/gnu/lib/libreadline ; make obj all install does the right thing. Ideas where to look next? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 10:27:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 6B3AC14D82 for ; Mon, 23 Aug 1999 10:26:58 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA06165 for current@freebsd.org; Mon, 23 Aug 1999 13:28:15 -0400 From: Bill Paul Message-Id: <199908231728.NAA06165@skynet.ctr.columbia.edu> Subject: Monday strikes again To: current@freebsd.org Date: Mon, 23 Aug 1999 13:28:14 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2406 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Must... control... fist of death... I just tried to boot the latest -current snapshot (Aug 23) on my little 486/66 machine. The kern.flp kernel panics right after saying "Probing for PnP devices:". Now, this machine has a PCI bus but it doesn't support ISA plug and play, so before any of you lot start theorizing about possible PnP BIOS problems, don't. The panic message says the kernel dies because of a page fault trying to reference memory location 0x4 (which is in page 0, which isn't mapped, which means this is a NULL pointer dereference) at PC 0xc0175b20. Running "nm kernel | grep c0175b" on the install kernel yields: c0175b68 t cnuninit c0175bc8 t sysctl_kern_consmute Running "nm kernel | grep c0175a" on the install kernel yields: c0175a50 T cninit c0175afc T cninit_finish c0175a50 t gcc2_compiled. c0175a08 t l_noclose c0175a14 T l_noread c0175a2c t l_norint c0175a38 t l_nostart c0175a20 T l_nowrite c0175a44 t l_nullioctl My money says the problem is cninit_finish(). The hardware config of this machine is as follows: 486DX2-S 66Mhz CPU 16MB RAM Diamond Speedstar ISA SVGA adapter (ET4000 chipset, 1MB RAM) IDE disk controller Maxtor LTX-200A IDE disk 3.5" floppy drive 2 serial ports, one parallel port Integrated Micro Systems PCI bridge Compaq NetFlex 3/P PCI ethernet adapter D-Link DFE-550TX PCI ethernet adapter The machine is running a -current snapshot from August 9th which works fine (or at least, it did after I fixed the PCI bridge detection breakage that screwed it up last time). It looks like the major difference is that /sys/i386/i386/cons.c was taken away and replaced with some MI console routines in /sys/kern. My gut tells me that console initialization is failing because it can't find the ISA graphics adapter for some reason. Anybody have any bright ideas where I can start looking for the problem? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 10:35:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 96AD914F23; Mon, 23 Aug 1999 10:35:04 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id UAA14210; Mon, 23 Aug 1999 20:32:50 +0300 (EEST) Date: Mon, 23 Aug 1999 20:32:50 +0300 (EEST) From: Narvi To: Andrzej Bialecki Cc: "Daniel C. Sobral" , Kevin Day , Nik Clayton , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 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, 23 Aug 1999, Andrzej Bialecki wrote: > On Mon, 23 Aug 1999, Daniel C. Sobral wrote: > > > > > Let me retract the Ghost in the Shell statement. I just checked, and > > my memory played tricks on me. It was a different letter effect. :-) > > > > Andrzej, can you somehow turn it into a parody? If you can make it > > into a parody, then it's legal. > > I can't think of any... What could be funny in such primitive effect > anyway? Besides, I'm not that sure I want to spend more time on that. Feel Parody doesn't hve to be funny. > free to hack it, guys, if you like it - it's BSD license, you know... > Make the falling letters black (on black background) and we will put up a patch in numerous free web directories that makes the letters visible again. 8-) > 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/ ---- > Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 10:35:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2B36714F0E for ; Mon, 23 Aug 1999 10:35:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA14513; Mon, 23 Aug 1999 19:26:20 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA50699; Mon, 23 Aug 1999 19:16:46 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908231716.TAA50699@yedi.iaf.nl> Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <199908231535.IAA00802@dingo.cdrom.com> from Mike Smith at "Aug 23, 1999 8:35:16 am" To: mike@smith.net.au (Mike Smith) Date: Mon, 23 Aug 1999 19:16:46 +0200 (CEST) Cc: dcs@newsguy.com, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Mike Smith wrote ... > > Kevin Day wrote: > > > This is just my opinion though, and not to be used as legal advice for > > > anyone. I just don't want FreeBSD to become a ball of intellectual property > > > infringements. :) > > > > Let me retract the Ghost in the Shell statement. I just checked, and > > my memory played tricks on me. It was a different letter effect. :-) > > > > Andrzej, can you somehow turn it into a parody? If you can make it > > into a parody, then it's legal. > > Just make it a port, for crap's sake, and distribute it from Poland. > By the time WB's American lawyers work out where you are on the map, > the statute of limitations will have expired and you'll be fine. > > But it's not going into the tree, no. I think Kevin's point and the > experiences we had with Hasbro should already have convinced people of > that much. Hear hear! I sat astounded, 'nailed' to my chair over all the excitement a mere screen saver can generate. Yes, I've seen The Matrix, no, I have not tried the screensaver. But it escapes me why one would like to import something into the mainline source tree that might attract undesirable legal attention (isn't all legal att. undesirable? ;-) to the project. Especially when everybody who really can't live without it has grabbed it from some ftp-server already. Amen, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Aug 23 10:36:10 1999 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 36EC215044 for ; Mon, 23 Aug 1999 10:36:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA10198; Mon, 23 Aug 1999 19:35:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Monday strikes again In-reply-to: Your message of "Mon, 23 Aug 1999 13:28:14 EDT." <199908231728.NAA06165@skynet.ctr.columbia.edu> Date: Mon, 23 Aug 1999 19:35:16 +0200 Message-ID: <10196.935429716@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908231728.NAA06165@skynet.ctr.columbia.edu>, Bill Paul writes: >Anybody have any bright ideas where I can start looking for the problem? Sprinkle liberally with printf() and bake until done... -- 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 Aug 23 10:37:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 2D5C414EC7 for ; Mon, 23 Aug 1999 10:37:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA09523; Mon, 23 Aug 1999 10:37:34 -0700 (PDT) (envelope-from dillon) Date: Mon, 23 Aug 1999 10:37:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199908231737.KAA09523@apollo.backplane.com> To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Monday strikes again References: <199908231728.NAA06165@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :some MI console routines in /sys/kern. My gut tells me that console :initialization is failing because it can't find the ISA graphics :adapter for some reason. : :Anybody have any bright ideas where I can start looking for the problem? : :-Bill : :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu No ideas, but if you compile the kernel up with the DDB option it should break into the debugger on the console when it panics, allowing you to do a 'trace'. The results of the trace should be of great benefit. -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 Aug 23 10:48: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id EE70B14CEC for ; Mon, 23 Aug 1999 10:48:05 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id KAA09294; Mon, 23 Aug 1999 10:47:05 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37C18919.CE2F3130@gorean.org> Date: Mon, 23 Aug 1999 10:47:05 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0821 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG, dbaker@distributed.net Subject: Re: Weird differences in rc5 behavior on -current vs. -stable References: <46614.935394275@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > On Sat, 21 Aug 1999 19:11:33 MST, Doug wrote: > > > I have a 3.2-Stable and a 4.0-Current system at home, both > > running rc5des. On both systems I set the priority in the rc5 options > > menu to '0', indicating lowest possible priority. On the -Stable > > system it's running at nice level '0', but it seems to be taking > > advantage of the idprio stuff since in general my system seems much > > "snappier," than when I was running 2.2.8 on the exact same machine. > > I think you'll find PR 12381 explains these results quite well. How does that PR explain why rc5des with the same ini file is running at nice 20 on -current, seemingly without idprio and running at nice 0 on -stable, seemingly with it? I'm aware of the discussion related to that PR, an both systems were built after Bruce committed that fix. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 11:12:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D1B1714F42 for ; Mon, 23 Aug 1999 11:12:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA09775; Mon, 23 Aug 1999 11:11:53 -0700 (PDT) (envelope-from dillon) Date: Mon, 23 Aug 1999 11:11:53 -0700 (PDT) From: Matthew Dillon Message-Id: <199908231811.LAA09775@apollo.backplane.com> To: Doug Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG, dbaker@distributed.net Subject: Re: Weird differences in rc5 behavior on -current vs. -stable References: <46614.935394275@axl.noc.iafrica.com> <37C18919.CE2F3130@gorean.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : How does that PR explain why rc5des with the same ini file is running at :nice 20 on -current, seemingly without idprio and running at nice 0 on :-stable, seemingly with it? I'm aware of the discussion related to that PR, :an both systems were built after Bruce committed that fix. : :Doug Why don't you ktrace the program to see what it does? On the face of it it sounds like the program may be doing it on purpose. -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 Aug 23 11:31:48 1999 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 8B9BA1585B; Mon, 23 Aug 1999 11:31:34 -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 OAA57510; Mon, 23 Aug 1999 14:29:59 -0400 (EDT) Message-Id: <199908231829.OAA57510@cs.rpi.edu> To: freebsd-current@freebsd.org Cc: new-bus@freebsd.org Subject: PCI interrupt routing in -Current/newbus Date: Mon, 23 Aug 1999 14:29:59 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How are PCI interrupts routed in CURRENT/NewBus? For example almost all of my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI world, but how does the interrupt dispatch routine decide which ints to route where? I recently put a panic() in a intr routine of mine just to see the call stack, but all it showed has Xintr11 (which upon grepping the source found no matches, but a nm /kernel did find it?!?. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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 Mon Aug 23 11:33:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id D807214F1D for ; Mon, 23 Aug 1999 11:33:42 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA06292 for current@freebsd.org; Mon, 23 Aug 1999 14:35:51 -0400 From: Bill Paul Message-Id: <199908231835.OAA06292@skynet.ctr.columbia.edu> Subject: Re: Monday strikes again To: current@freebsd.org Date: Mon, 23 Aug 1999 14:35:49 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1356 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, further investigation shows that configure() has the following code: #if NPNP > 0 /* Activate PNP. If no drivers are found, let ISA probe them.. */ pnp_configure(); #endif /* * Explicitly probe and attach ISA last. The isa bus saves * it's device node at attach time for us here. */ if (isa_bus_device) bus_generic_attach(isa_bus_device); However isa_bus_device is still NULL so we never get any ISA devices attached. No ISA devices means no console (the VGA card and serial ports are both ISA devices), so we explode. Since the ISA bus in this machine is on-board instead of being hung off a PCI to ISA bridge, I suspect that somebody broke the handling on on-board ISA buses. Thank you very much, may I have another. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 11:39:52 1999 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 7FE5815783; Mon, 23 Aug 1999 11:39:48 -0700 (PDT) (envelope-from ab@astralblue.com) Received: from raista.pl.cp (raista.pl.cp [10.0.0.14]) by gw1.pl.cp (8.9.3/8.9.3) with ESMTP id LAA27944; Mon, 23 Aug 1999 11:26:03 -0700 (PDT) (envelope-from ab@astralblue.com) Received: from localhost (ab@localhost) by raista.pl.cp (8.9.3/8.9.3) with ESMTP id CAA02843; Mon, 23 Aug 1999 02:04:40 -0700 (PDT) (envelope-from ab@astralblue.com) X-Authentication-Warning: raista.pl.cp: ab owned process doing -bs Date: Mon, 23 Aug 1999 02:04:39 -0700 (PDT) From: "Eugene M. Kim" X-Sender: ab@raista.pl.cp To: Soren Schmidt Cc: Nicolas Souchu , freebsd-current@FreeBSD.ORG, soren@FreeBSD.ORG Subject: Re: problem with the ata driver In-Reply-To: <199908230627.IAA49585@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=euc-kr Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh well. First of all I now feel a little more comfortable to see that I'm not alone. :-) I had same problem, and have tracked the problem down to some weird behavior of the CD-ROM drive that I have (which is also a LG one). And FYI, I have an Intel 82371FB-based PIIX controller (which supports the DMA transfer but is not supported by the ata driver). My dmesg output with modified patch (which will be explained later) and all ATA/ATAPI debug flags goes here: WARNING: "bktr" is usurping "bktr"'s cdevsw[] isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: type=12308086 class=01 subclass=01 cmd=02800005 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=00 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=00 status0=ff status1=ff ahc0: irq 11 at device 17.0 on pci0 ... (snip) ... ep0 XXX: driver didn't set ifq_maxlen ata0: ata_command: addr=01f0, device=00, cmd=a1, c=0, h=0, s=0, count=0, flags=01 ata_start: entered ata_command: leaving atapi: piomode=3, dmamode=1, udmamode=-1 ata0: dmainit: ioaddr=0x1f0 altioaddr=0x3f6, bmaddr=0x1000 atapi: PIO transfer mode set ata_start: entered atapi: trying to start MODE_SENSE cmd ata0: ata_command: addr=01f0, device=00, cmd=a0, c=28, h=0, s=0, count=0, flags=00 ata_command: leaving ata_start: started atapi, leaving atapi_interrupt: enter atapi_interrupt: length=24 reason=0x0b atapi_interrupt: command completion interrupt with DRQ atapi_interrupt: read size problem, 4 bytes residue atapi_interrupt: error=0x00 ata_start: entered atapi: phew, got back from asleep with wakeup atapi: acd: mode sense 0-16-04-00-00-00-00-00-2a-0e-00-00-71-6d-2d-03-02-c2-01-00-00-80-02-c2-00-00-00-00 acd0: CDROM drive at ata0 as master acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked, lock protected Waiting 2 seconds for SCSI devices to settle As seen here, instead of a data-in interrupt and a command completion interrupt, the drive (or the controller, I am not sure) is returning a single command completion interrupt with DRQ bit set (reason=0x0b). Since I don't have the ATA/ATAPI spec at hand I can't verify if this is an allowed behavior or not, but in my case reading and returning 24 bytes of data (as `length' suggests) works fine.2 The patch of sys/dev/ata/atapi-all.c that I used is available at http://home.astralblue.com/~ab/ata-patch/ (it is a little too big to include here); it also has some other minor fixes one of which uses asleep instead of tsleep to prevent an interrupt from being lost in the short window between splx and tsleep. BTW, my patch does not solve *all* problems that my drive has; if the kernel tries to read some data off the disc, the drive returns an `aborted command' error after two 512-byte blocks as in the following dmesg output (I have used `dd if=/dev/acd0c of=/dev/null bs=2k count=1' to produce this): ata_start: entered atapi: trying to start READ_BIG cmd ata0: ata_command: addr=01f0, device=00, cmd=a0, c=2048, h=0, s=0, count=0, flags=00 ata_command: leaving ata_start: started atapi, leaving atapi_interrupt: enter atapi_interrupt: length=512 reason=0x0a atapi_interrupt: enter atapi_interrupt: length=512 reason=0x0b atapi_interrupt: command completion interrupt with DRQ atapi_interrupt: error=0xb4 ata_start: entered atapi: phew, got back from asleep with wakeup ata_start: entered atapi: trying to start REQUEST_SENSE cmd ata0: ata_command: addr=01f0, device=00, cmd=a0, c=18, h=0, s=0, count=0, flags=00 ata_command: leaving ata_start: started atapi, leaving atapi_interrupt: enter atapi_interrupt: length=14 reason=0x0b atapi_interrupt: command completion interrupt with DRQ atapi_interrupt: read size problem, 4 bytes residue atapi_interrupt: error=0x00 ata_start: entered atapi: phew, got back from asleep with wakeup atapi_error: READ_BIG - ABORTED COMMAND skey=b asc=00 ascq=00 error=04 I guess that perhaps these LG CD-ROM drives are using some nonstandard or obsolete convention that the new ata driver doesn't understand. Unfortunately, I couldn't test the drive with the old wdc driver because it even didn't detect my drive (being the only IDE/ATAPI device, master on the primary controller). Thank you, Eugene On Mon, 23 Aug 1999, Soren Schmidt wrote: | It seems Nicolas Souchu wrote: | > acd0: CDROM drive at ata0 as master | > acd0: drive speed 0KB/sec | > acd0: supported read types: | > acd0: Mechanism: caddy | > acd0: Medium: CD-ROM unknown medium | > | > Any clue? | > | > The drive was running flawlessly with the old wdc driver and with various | > primary releases of the new ata driver (some, not all). | | Hmm, looks like the timeout I've chosen for timing out on the probes | *might* be too short for some devices.. | | -Søren | | | 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 Aug 23 11:42:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 6BCB115021; Mon, 23 Aug 1999 11:42:03 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id UAA00587; Mon, 23 Aug 1999 20:41:39 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A806C870A; Mon, 23 Aug 1999 19:37:38 +0200 (CEST) Date: Mon, 23 Aug 1999 19:37:38 +0200 From: Ollivier Robert To: Harlan Stenn Cc: "Daniel O'Callaghan" , John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: NTP daemon and Y2K issues Message-ID: <19990823193738.A19091@keltia.freenix.fr> Mail-Followup-To: Harlan Stenn , Daniel O'Callaghan , John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG References: <14766.935421554@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <14766.935421554@brown.pfcs.com>; from Harlan Stenn on Mon, Aug 23, 1999 at 11:19:14AM -0400 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Harlan Stenn: > Also, a *huge* number of bugfixes and improvements have been made to the NTP > code since xntp3.4anything. I plan to upgrade CURRENT up to 4.0.97 soon. I don't run STABLE at all and we're too close to 3.3 to change anything in it. Maybe for 3.4. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 13:27:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id A933914CC0; Mon, 23 Aug 1999 13:27:33 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-148.skylink.it [194.185.55.148]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA13067; Mon, 23 Aug 1999 22:27:31 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id UAA00395; Mon, 23 Aug 1999 20:12:00 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 23 Aug 1999 20:12:00 GMT Date: Mon, 23 Aug 1999 22:12:00 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Ollivier Robert Cc: Harlan Stenn , "Daniel O'Callaghan" , John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: NTP daemon and Y2K issues In-Reply-To: <19990823193738.A19091@keltia.freenix.fr> 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 For your information: the patch supplied was not in xntpd-3.5f-3. So you might want to repatch after importing. Nick > According to Harlan Stenn: > > Also, a *huge* number of bugfixes and improvements have been made to the NTP > > code since xntp3.4anything. > > I plan to upgrade CURRENT up to 4.0.97 soon. I don't run STABLE at all and > we're too close to 3.3 to change anything in it. Maybe for 3.4. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 13:27:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 64F7D14CC0 for ; Mon, 23 Aug 1999 13:27:50 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id QAA03853 for ; Mon, 23 Aug 1999 16:27:48 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 23 Aug 1999 16:31:31 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: current@freebsd.org Subject: Floppy/diskless booting problem with -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm attempting to boot a -current system (from 4 days ago) off of a modified GENERIC kernel floppy disk, and it is failing in kern/vfs_conf.c's vfs_mountrootfs routine, with a message: rootdev=0xffffffff error=6, panic: cannot mount root(2) rootdev is NODEV, and err is ENXIO. The isc-dhcp server does serve the bootp request successfully (I get messages from the -current kernel that indicate an IP address, rootfs, et.al), and the NFS server reports the success of the client mounting the NFS-exported filesystem (the server is a 3.1-RELEASE machine). I am not specifying any swap (yet). I'm using a straight GENERIC kernel, kgzipped, with options added at the end: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT options NULLFS options UNION (the NFS_ROOT option is already in GENERIC.) Am I missing something? (I tried "BOOTP_NFSV3" option also)... Any success stories using this method? (as documented in /usr/share/examples/diskless) -Mark Taylor NetMAX Developer mtaylor@cybernet.com http://www.netmax.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 13:32:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 422F71527D; Mon, 23 Aug 1999 13:32:42 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Mon, 23 Aug 1999 16:32:19 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 23 Aug 1999 13:32:17 -0700 (PDT) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 23 Aug 1999 16:32:16 -0400 (EDT) To: Nick Hibma Cc: Ollivier Robert , Harlan Stenn , "Daniel O'Callaghan" , John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: NTP daemon and Y2K issues In-Reply-To: Nick Hibma's (n_hibma@skylink.it) message dated Mon, 23 Aug 1999 22:12:00. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Mon, 23 Aug 1999 16:32:16 -0400 Message-ID: <15120.935440336@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are saying that FreeBSD has patches to ntp that are missing from ntp4, please submit them to UDel. Don't bother sending patches that only fix problems with ntp3; ntp3 is no longer supported. ntp-4.1.0 should be available in a few weeks. I'm waiting for some portability patches to settle down, some minor NT cleanup, and perhaps some parse code cleanup before making the release. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 13:34:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5A9181565A for ; Mon, 23 Aug 1999 13:34:19 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 VAA59823; Mon, 23 Aug 1999 21:44:10 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 23 Aug 1999 21:44:10 +0100 (BST) From: Doug Rabson To: Bill Paul Cc: current@freebsd.org Subject: Re: Monday strikes again In-Reply-To: <199908231835.OAA06292@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, Bill Paul wrote: > Okay, further investigation shows that configure() has the following > code: > > #if NPNP > 0 > /* Activate PNP. If no drivers are found, let ISA probe them.. */ > pnp_configure(); > #endif > > /* > * Explicitly probe and attach ISA last. The isa bus saves > * it's device node at attach time for us here. > */ > if (isa_bus_device) > bus_generic_attach(isa_bus_device); > > However isa_bus_device is still NULL so we never get any ISA devices > attached. No ISA devices means no console (the VGA card and serial ports > are both ISA devices), so we explode. > > Since the ISA bus in this machine is on-board instead of being hung > off a PCI to ISA bridge, I suspect that somebody broke the handling > on on-board ISA buses. > > Thank you very much, may I have another. It seems like isa bus is never being attached for some reason. Have a look at nexus_attach() and see if anything suspicious is happening (like an error return from device_probe_and_attach()). -- 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 Mon Aug 23 13:36:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FEF31501B; Mon, 23 Aug 1999 13:36:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 VAA59830; Mon, 23 Aug 1999 21:45:24 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 23 Aug 1999 21:45:24 +0100 (BST) From: Doug Rabson To: "David E. Cross" Cc: freebsd-current@freebsd.org, new-bus@freebsd.org Subject: Re: PCI interrupt routing in -Current/newbus In-Reply-To: <199908231829.OAA57510@cs.rpi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, David E. Cross wrote: > How are PCI interrupts routed in CURRENT/NewBus? For example almost all of > my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI > world, but how does the interrupt dispatch routine decide which ints to > route where? I recently put a panic() in a intr routine of mine just to > see the call stack, but all it showed has Xintr11 (which upon grepping the > source found no matches, but a nm /kernel did find it?!?. The bios informs the kernel what irq each device is mapped to and we build a chain of interrupt handlers for each one. All the handlers registered for a given irq are called when it fires. -- 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 Mon Aug 23 13:39:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 4FE951514B for ; Mon, 23 Aug 1999 13:39:20 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id WAA51039 for ; Mon, 23 Aug 1999 22:37:42 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id WAA06796 for freebsd-current@freebsd.org; Mon, 23 Aug 1999 22:37:42 +0200 (CEST) Date: Mon, 23 Aug 1999 22:37:42 +0200 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: Any chances to solve bin/7973? Message-ID: <19990823223742.A6198@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody capable to solve or fix bin/7973 in lpd? I have found the problem is still there (FreeBSD-3.2). Or am I anything missing/doing wrong? bin/7973: Bad control file owner in case of remote printing. The problem is that print filters ("if" in printcap) cannot read control files cf* in case of remote printing (in case of local printing everything is ok). -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 13:47:44 1999 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 1A0EA14DEF; Mon, 23 Aug 1999 13:47:40 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA60761; Mon, 23 Aug 1999 16:47:35 -0400 (EDT) Message-Id: <199908232047.QAA60761@cs.rpi.edu> To: Doug Rabson Cc: "David E. Cross" , freebsd-current@freebsd.org, new-bus@freebsd.org, crossd@cs.rpi.edu Subject: Re: PCI interrupt routing in -Current/newbus In-Reply-To: Message from Doug Rabson of "Mon, 23 Aug 1999 21:45:24 BST." Date: Mon, 23 Aug 1999 16:47:35 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How are PCI interrupts routed in CURRENT/NewBus? For example almost all of > > my PCI devices are mapped to IRQ11. I understand this is "normal" in the PCI > > world, but how does the interrupt dispatch routine decide which ints to > > route where? I recently put a panic() in a intr routine of mine just to > > see the call stack, but all it showed has Xintr11 (which upon grepping the > > source found no matches, but a nm /kernel did find it?!?. > > The bios informs the kernel what irq each device is mapped to and we build > a chain of interrupt handlers for each one. All the handlers registered > for a given irq are called when it fires. That is what I initially thought, but my PCI handler is only called when that PCI device gets and interrupt. I would expect with IRQ 11 being so frequently used in my system that my handler would be called much more often than that. It is also called with the appropriate softc structure (this being a dual function controller). If it was firing all the handlers I would expect function 0 to trigger first, it does not trigger at all when function 1 signals the int. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 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 Mon Aug 23 13:56:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 8D58C156FD for ; Mon, 23 Aug 1999 13:56:38 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA41544; Mon, 23 Aug 1999 16:55:59 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <19990823223742.A6198@dcse.fee.vutbr.cz> References: <19990823223742.A6198@dcse.fee.vutbr.cz> Date: Mon, 23 Aug 1999 16:56:27 -0400 To: Cejka Rudolf , freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Any chances to solve bin/7973? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:37 PM +0200 8/23/99, Cejka Rudolf wrote: >Is anybody capable to solve or fix bin/7973 in lpd? I have found the >problem is still there (FreeBSD-3.2). Or am I anything missing/doing wrong? > >bin/7973: Bad control file owner in case of remote printing. The problem >is that print filters ("if" in printcap) cannot read control files cf* in >case of remote printing (in case of local printing everything is ok). (I haven't looked at the PR, but...) Why would the filter be reading the control file? It is just a filter, supposedly reading from stdin and writing to stdout... --- 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 Mon Aug 23 13:58:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 2371B14CD3; Mon, 23 Aug 1999 13:58:07 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-148.skylink.it [194.185.55.148]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA13641; Mon, 23 Aug 1999 22:57:24 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id UAA00541; Mon, 23 Aug 1999 20:49:11 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 23 Aug 1999 20:49:11 GMT Date: Mon, 23 Aug 1999 22:49:11 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Harlan Stenn Cc: Ollivier Robert , "Daniel O'Callaghan" , John Saunders , freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: NTP daemon and Y2K issues In-Reply-To: <15120.935440336@brown.pfcs.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've submitted patches for 3, but the patch applies to the GPS input filters, so I assume they can be ported. If not, pitty. Nick On Mon, 23 Aug 1999, Harlan Stenn wrote: > If you are saying that FreeBSD has patches to ntp that are missing from > ntp4, please submit them to UDel. > > Don't bother sending patches that only fix problems with ntp3; ntp3 is no > longer supported. > > ntp-4.1.0 should be available in a few weeks. I'm waiting for some > portability patches to settle down, some minor NT cleanup, and perhaps some > parse code cleanup before making the release. > > H > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 14: 7:12 1999 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 8CCF715792 for ; Mon, 23 Aug 1999 14:07:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-63.ucdavis.edu [169.237.16.191]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA18145; Mon, 23 Aug 1999 14:06:12 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA70305; Mon, 23 Aug 1999 14:06:09 -0700 (PDT) (envelope-from obrien) Date: Mon, 23 Aug 1999 14:06:08 -0700 From: "David O'Brien" To: current@freebsd.org Cc: vladimir@math.uic.edu Subject: NFSv3 on freebsd<-->solaris Message-ID: <19990823140608.A70275@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 4.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 I'm forwarding this to current@freebsd.org as I know many people are on the list that live in multi-platform worlds. ----- Forwarded message from vladimir@math.uic.edu ----- Solaris 7 machines cannot use NFSv3 mounts from a FreeBSD NFS server. When using NFSv2 the decrease in performance was very noticeable. I was wondering if anyone among FreeBSD developers is aware of this problem (I am not implying that the problem might be on the FreeBSD side, it might as well be a bug in solaris NFS implementation). I would greatly appreciate any help with the following problem. I have a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 client. I run into problems when trying to use NFSv3 mounts on the client. Trying to remove files from the mounted partition (on the nfs client) results in multiple errors, for example: # rm -r /home/2/vladimir rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists I have tried using tcp and udp mount options with the same result. NFSv2 works fine. Solaris client has the latest patches applied. I would very much appreciate any comments on that. ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 14: 7:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 8F1851514B; Mon, 23 Aug 1999 14:07:53 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id XAA17658; Mon, 23 Aug 1999 23:07:35 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id XAA03633; Mon, 23 Aug 1999 23:06:25 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990823230625.37897@breizh.teaser.fr> Date: Mon, 23 Aug 1999 23:06:25 +0200 From: Nicolas Souchu To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG, soren@FreeBSD.ORG Subject: Re: problem with the ata driver References: <19990822222102.32308@breizh.teaser.fr> <199908230627.IAA49585@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: <199908230627.IAA49585@freebsd.dk>; from Soren Schmidt on Mon, Aug 23, 1999 at 08:27:15AM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 23, 1999 at 08:27:15AM +0200, Soren Schmidt wrote: > >It seems Nicolas Souchu wrote: >> acd0: CDROM drive at ata0 as master >> acd0: drive speed 0KB/sec >> acd0: supported read types: >> acd0: Mechanism: caddy >> acd0: Medium: CD-ROM unknown medium >> >> Any clue? >> >> The drive was running flawlessly with the old wdc driver and with various >> primary releases of the new ata driver (some, not all). > >Hmm, looks like the timeout I've chosen for timing out on the probes >*might* be too short for some devices.. Which ones, I found nothing in the LINT file related to ATA. > >-Søren > Thanks. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 14:53:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id E628A157A8 for ; Mon, 23 Aug 1999 14:53:42 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40322>; Tue, 24 Aug 1999 07:51:48 +1000 Date: Tue, 24 Aug 1999 07:52:41 +1000 From: Peter Jeremy Subject: Re: Softupdates reliability? In-reply-to: <199908230659.QAA08609@nymph.detir.qld.gov.au> To: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Message-Id: <99Aug24.075148est.40322@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay wrote: >I was extracting from the Exabyte to the DDRS disk while applying a CTM >update from that disk against one of the DCAS disks when it crashed. The >Exabyte went wonky (took about 6 goes to get the tape ejected) and the >rest of the disk system locked up. The SCSI adapter was so confused I >had to power down. The exact order of events is not clear from this. In general, I'd say that if something managed to upset the SCSI bus sufficiently to confuse every target on it, then there's a reasonably likelihood that data transfers were also corrupted. A serious bus corruption during a disk write (either command or data phase) would have a reasonable chance of resulting in corrupt data on the disk (either the wrong data in the right place or the right data in the wrong place). >So, what do people think is the most likely: > > 1) the SCSI adapter told the disk to write crap to a couple places > on the disk (breaking an inode and some directories) Personally, I'd go for this one - though it's not clear that the Fireport40 (or its driver) is to blame. Any of the SCSI targets could have caused the problem by deciding to take over the bus at an inopportune time. I'm not sure how to go about isolating the problem. I don't suppose you happened to bump one of the cables, or suffer a power glitch? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 14:58:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 9EB4114FA6 for ; Mon, 23 Aug 1999 14:58:06 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id AB03C1912; Mon, 23 Aug 1999 23:57:23 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id A810749D3; Mon, 23 Aug 1999 23:57:23 +0200 (CEST) Date: Mon, 23 Aug 1999 23:57:23 +0200 (CEST) From: Andrzej Bialecki To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <199908231535.IAA00802@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999, Mike Smith wrote: > Just make it a port, for crap's sake, and distribute it from Poland. > By the time WB's American lawyers work out where you are on the map, > the statute of limitations will have expired and you'll be fine. > > But it's not going into the tree, no. I think Kevin's point and the > experiences we had with Hasbro should already have convinced people of > that much. I'm tired of this. It has priority number -infinity on my list. Do with it what you want - the code is there. I won"t put it in the tree. 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 Aug 23 15:31:53 1999 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 48B30157E3; Mon, 23 Aug 1999 15:31:48 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA09365; Mon, 23 Aug 1999 15:30:04 -0700 (PDT) (envelope-from green@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: green owned process doing -bs Date: Mon, 23 Aug 1999 15:30:03 -0700 (PDT) From: "Brian F. Feldman" To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-Reply-To: <199908230659.QAA08609@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What revision of the K6-2 did this happen on? -- Brian Fundakowski Feldman / "Any sufficiently advanced bug is \ green@FreeBSD.org | indistinguishable from a feature." | FreeBSD: The Power to Serve! \ -- Rich Kulawiec / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 15:41:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 42BFC15189 for ; Mon, 23 Aug 1999 15:41:41 -0700 (PDT) (envelope-from n_hibma@skylink.it) Received: from heidi.plazza.it (va-148.skylink.it [194.185.55.148]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA15409; Tue, 24 Aug 1999 00:41:40 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id WAA01692; Mon, 23 Aug 1999 22:42:23 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Mon, 23 Aug 1999 22:42:23 GMT Date: Tue, 24 Aug 1999 00:42:23 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Doug Rabson Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: Monday strikes again 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 Anything the change to nexus.c that Peter Wemm made would change? 1.15 Mon Aug 23 19:23:33 1999 UTC by peter CVS Tags: HEAD Diffs to 1.14 The nexus_attach() code works a lot better if it's actually connected to the device methods... Also, don't fail to add eisa/isa because a previous device failed to attach. 1.14 Sun Aug 22 19:56:55 1999 UTC by peter Diffs to 1.13 Take advantage of the apm/npx code and let them identify themselves rather than having explicit hooks here. Treat the eisa/isa attach a little differently so that we defer the decision about to attach eisa/isa to the motherboard directly only if the PCI probe (if it exists) fails to turn up a PCI->EISA/ISA bridge. This restores the original device geometry where ISA and/or EISA attach to their bridge rather than bypassing and going to the root. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/nexus.c > > Okay, further investigation shows that configure() has the following > > code: > > > > #if NPNP > 0 > > /* Activate PNP. If no drivers are found, let ISA probe them.. */ > > pnp_configure(); > > #endif > > > > /* > > * Explicitly probe and attach ISA last. The isa bus saves > > * it's device node at attach time for us here. > > */ > > if (isa_bus_device) > > bus_generic_attach(isa_bus_device); > > > > However isa_bus_device is still NULL so we never get any ISA devices > > attached. No ISA devices means no console (the VGA card and serial ports > > are both ISA devices), so we explode. > > > > Since the ISA bus in this machine is on-board instead of being hung > > off a PCI to ISA bridge, I suspect that somebody broke the handling > > on on-board ISA buses. > > > > Thank you very much, may I have another. > > It seems like isa bus is never being attached for some reason. Have a > look at nexus_attach() and see if anything suspicious is happening (like > an error return from device_probe_and_attach()). > > -- > 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 > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 15:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 6DEF114D98; Mon, 23 Aug 1999 15:47:57 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id SAA09769; Mon, 23 Aug 1999 18:45:54 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 23 Aug 1999 18:49:36 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: current@FreeBSD.ORG Subject: RE: Floppy/diskless booting problem with -current: FIX Cc: jb@FreeBSD.ORG, phk@FreeBSD.ORG, peter@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that the problem is in kern/vfs_conf.c: When performing BOOTP configuration, nfs/bootp_subr:bootpc_init() is called before the root-mount attempts. This routine finds the first non-loopback and non-point- to-point interface, and does the bootp request. If it gets all of its needed data, then it mounts the specified rootfs, sets nfs_diskless_valid to 3, and returns. Then vfs_rootmountalloc() is called, and the loop to mount rootdevs is started. Unfortunately (?), rootdev is not set by bootpc_init(), so the loop is rather short. :) I'm not sure what the fix should be, but here's what I did to get the root mounted: Index: vfs_conf.c =================================================================== RCS file: /FreeBSD/CVS/src/sys/kern/vfs_conf.c,v retrieving revision 1.31 diff -c -9 -r1.31 vfs_conf.c *** vfs_conf.c 1999/07/03 17:40:31 1.31 --- vfs_conf.c 1999/08/23 22:38:58 *************** *** 70,87 **** --- 70,88 ---- /* * These define the root filesystem, device, and root filesystem type. */ dev_t rootdevs[] = { NODEV, NODEV }; char *rootdevnames[2]; struct vnode *rootvnode; char *mountrootfsname; #ifdef BOOTP extern void bootpc_init __P((void)); + extern int nfs_diskless_valid; #endif /* * vfs_init() will set maxvfsconf * to the highest defined type number. */ int maxvfsconf; struct vfsconf *vfsconf; *************** *** 133,168 **** --- 134,174 ---- panic("cannot mount root\n"); return ; } mp->mnt_flag |= MNT_ROOTFS; /* * Attempt the mount */ err = ENXIO; + #ifdef BOOTP + if (nfs_diskless_valid == 3) err = VFS_MOUNT(mp, NULL, NULL, NULL, p); + #endif + if (err) { orootdev = rootdev; if (rootdevs[0] == NODEV) rootdevs[0] = rootdev; for (i = 0; i < sizeof(rootdevs) / sizeof(rootdevs[0]); i++) { if (rootdevs[i] == NODEV) break; rootdev = rootdevs[i]; if (rootdev != orootdev) { s = splbio(); /* Overkill, but harmless.. */ printf("changing root device to %s\n", rootdevnames[i]); splx(s); orootdev = rootdev; } strncpy(mp->mnt_stat.f_mntfromname, rootdevnames[i] ? rootdevnames[i] : ROOTNAME, MNAMELEN - 1); err = VFS_MOUNT(mp, NULL, NULL, NULL, p); if (err != ENXIO) break; + } } if (err) { /* * XXX should ask the user for the name in some cases. * Why do we call vfs_unbusy() here and not after ENXIO * is returned above? */ vfs_unbusy(mp, p); /* I'd really appreciate it if someone could take a look at this and commit a fix (possibly this one). John? Poul? Peter? Without a similar fix, I don't think that BOOTP kernels will not work (as specified in the file /usr/share/examples/diskless/README.BOOTP). -Mark Taylor NetMAX Developer mtaylor@cybernet.com http://www.netmax.com/ On 23-Aug-99 Mark J. Taylor wrote: > > > I'm attempting to boot a -current system (from 4 days ago) off of a modified > GENERIC kernel floppy disk, and it is failing in kern/vfs_conf.c's vfs_mountrootfs > routine, with a message: > rootdev=0xffffffff error=6, panic: cannot mount root(2) > > > rootdev is NODEV, and err is ENXIO. > > > The isc-dhcp server does serve the bootp request successfully (I get messages from > the -current kernel that indicate an IP address, rootfs, et.al), and the NFS server > reports the success of the client mounting the NFS-exported filesystem (the server > is a 3.1-RELEASE machine). I am not specifying any swap (yet). > > > > I'm using a straight GENERIC kernel, kgzipped, with options added at the end: > options BOOTP > options BOOTP_NFSROOT > options BOOTP_COMPAT > options NULLFS > options UNION > > (the NFS_ROOT option is already in GENERIC.) > > > > Am I missing something? (I tried "BOOTP_NFSV3" option also)... Any success stories > using this method? (as documented in /usr/share/examples/diskless) > > > > > > -Mark Taylor > NetMAX Developer > mtaylor@cybernet.com > http://www.netmax.com/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 17:34:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0142D14EC7 for ; Mon, 23 Aug 1999 17:34:28 -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 ED80A1C1F; Tue, 24 Aug 1999 08:33:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: Doug Rabson , Bill Paul , current@FreeBSD.ORG Subject: Re: Monday strikes again In-reply-to: Your message of "Tue, 24 Aug 1999 00:42:23 +0200." Date: Tue, 24 Aug 1999 08:33:07 +0800 From: Peter Wemm Message-Id: <19990824003307.ED80A1C1F@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > Anything the change to nexus.c that Peter Wemm made would change? Yes, 1.14 broke non-PCI systems, and 1.15 fixed it. I forgot to change: DEVICE_METHOD(device_attach, bus_generic_attach); to: DEVICE_METHOD(device_attach, nexus_attach); .. which would explain why nexus_attach() wasn't being called. There were a few other problems, including the eisa probe/attach that would have returned ENXIO and failing the attach before isa was attached. > 1.15 Mon Aug 23 19:23:33 1999 UTC by peter > CVS Tags: HEAD > Diffs to 1.14 > > The nexus_attach() code works a lot better if it's actually connected to > the device methods... Also, don't fail to add eisa/isa because a > previous device failed to attach. > > > 1.14 Sun Aug 22 19:56:55 1999 UTC by peter > Diffs to 1.13 > > Take advantage of the apm/npx code and let them identify themselves > rather than having explicit hooks here. Treat the eisa/isa attach a > little differently so that we defer the decision about to attach > eisa/isa to the motherboard directly only if the PCI probe (if it > exists) fails to turn up a PCI->EISA/ISA bridge. This restores the > original device geometry where ISA and/or EISA attach to their bridge > rather than bypassing and going to the root. > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/nexus.c > > > > Okay, further investigation shows that configure() has the following > > > code: > > > > > > #if NPNP > 0 > > > /* Activate PNP. If no drivers are found, let ISA probe them.. */ > > > pnp_configure(); > > > #endif > > > > > > /* > > > * Explicitly probe and attach ISA last. The isa bus saves > > > * it's device node at attach time for us here. > > > */ > > > if (isa_bus_device) > > > bus_generic_attach(isa_bus_device); > > > > > > However isa_bus_device is still NULL so we never get any ISA devices > > > attached. No ISA devices means no console (the VGA card and serial ports > > > are both ISA devices), so we explode. > > > > > > Since the ISA bus in this machine is on-board instead of being hung > > > off a PCI to ISA bridge, I suspect that somebody broke the handling > > > on on-board ISA buses. > > > > > > Thank you very much, may I have another. > > > > It seems like isa bus is never being attached for some reason. Have a > > look at nexus_attach() and see if anything suspicious is happening (like > > an error return from device_probe_and_attach()). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 17:41: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.ihug.co.nz (tk1.ihug.co.nz [203.29.160.13]) by hub.freebsd.org (Postfix) with ESMTP id 581EC14FF2 for ; Mon, 23 Aug 1999 17:40:38 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p31-max5.dun.ihug.co.nz [209.77.156.31]) by smtp1.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id MAA09652 for ; Tue, 24 Aug 1999 12:39:34 +1200 Message-ID: <37C1E9BD.F3584C38@es.co.nz> Date: Tue, 24 Aug 1999 12:39:25 +1200 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: followup to apm problems. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ive been following the apm problems and changes in apm threads in hope that I would fix the problems that I too am having. I am using the latest sources for apm, apmconf and apmd, as well as the kernel. (as of 23/8/99, NZST, which is yesterday evening) dmesg is: apm0: on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f0000, Data 0xc00fdfa0 apm: Code entry 0x00008010, Idling CPU enabled, Management enabled apm: CS_limit=0xffff, DS_limit=0xffff apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU enabled Add hook "default suspend" Add hook "default resume" ---and then later on psm0: irq 12 on atkbdc0 Add hook "PS/2 mouse" after going 'apmconf -e' apm shows: APM version: 1.2 APM Managment: Enabled AC Line status: on-line Resume timer: disabled Resume on ring indicator: enabled APM Capacities: global standby state global suspend state resume timer from standby resume timer from suspend ---- 'apm -Z' for standby jumps into standby mode for like.. an instant, then comes right back out (while playing mp3) dmesg: APM ioctl: cmd = 0x2000500c Received APM Event: PMEV_STANDBYRESUME Execute APM hook "default resume." resumed from suspended mode (slept 00:00:00) Execute APM hook "PS/2 mouse." 'zzz' or 'apm -z' for suspend jumps into suspend mode, and just the same way, comes right back out (while playing mp3s again) dmesg: APM ioctl: cmd = 0x20005001 Execute APM hook "default suspend." Received APM Event: PMEV_NORMRESUME Execute APM hook "default resume." resumed from suspended mode (slept 00:00:01) Execute APM hook "PS/2 mouse." it should be noted that the cpu fan does turn off momentarily for both of these events, and the mp3 that is playing stops, then starts up again where it left off. Even without playing anything through the sound device, it does the same thing. If i leave the thing on with no activity, while running apmd, it goes into suspend or standby (depending on the timers set in the bios) every now and again, but jumps back out as soon as it does. Also, all the PM timer interrupts are disabled. Motherboard is an Abit BH-6 cheers, mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 18:39: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 7485B14FAC for ; Mon, 23 Aug 1999 18:38:49 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id LAA00642 for ; Tue, 24 Aug 1999 11:35:29 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id LAA15228 for freebsd-current@freebsd.org; Tue, 24 Aug 1999 11:35:26 +1000 (EST) Date: Tue, 24 Aug 1999 11:35:26 +1000 (EST) From: George Michaelson Message-Id: <199908240135.LAA15228@azure.dstc.edu.au> To: freebsd-current@freebsd.org Subject: SIO "lost interrupt" status in current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've done a quick scan of the lists and GNATS db, and see some evidence that in the last 1-2 years there has been a thread of people who see bad sio performance, coupled to any of X, Audio and APM (including bios APM setting). The PRs most relevant (but only marginally IMHO) are: http://www.freebsd.org/cgi/query-pr.cgi?pr=8940 http://www.freebsd.org/cgi/query-pr.cgi?pr=8981 Comments in the searchable mail indexes which are relevant are: http://www.freebsd.org/cgi/getmsg.cgi? \ fetch=4574708+4578214+ \ /usr/local/www/db/text/1999/freebsd-current/19990509.freebsd-current http://www.freebsd.org/cgi/getmsg.cgi? \ fetch=4631267+4632671+ \ /usr/local/www/db/text/1999/freebsd-current/19990509.freebsd-current http://www.freebsd.org/cgi/getmsg.cgi? \ fetch=393430+395069+ \ /usr/local/www/db/text/1999/freebsd-current/19990614.freebsd-current I'm on a P200, 16550, may do PnP for devices, PPP over 28.8kbps modem to a Cisco 3640 ISDN digital modem box and see hundreds of lost interrupts per hour. They cause extreme lossage of download speed to FTP/SSH/HTTP but have not creamed the IP layer across the board since immediately after one I can use a non-live telnet/ssh window fine. The hung session typically takes 30sec to come live again at a reduced window size of course. I've tried the LINT listed sio flags to enable extended FIFO (which didn't work for me, presumably because I'm not on a 16550A) and fast recovery to no avail. I have yet to confirm if I have APM disabled in BIOS, or check if removing PnP or soundcard drivers make any difference. X is the prime reason I use this box (@home access) so "don't do that" may not be an option for X11. The other stuff while annoying, might be viable fixes and I will explore them if somebody can give me clear advice here. I'm actually pretty sure it happens even without X11 live. This worries me! changing the modem serial speed down from 57600 through 33600 to 19200 made no difference. This also worries me. New-Bus is not new any more. If this is a lingering problem with new-bus then it should be documented and stomped on! Can I get some kind of semi-canonical reply from the knowledgable why this problem exists? I appreciate it may be low prio, I'm just concerned its dropped off the table of known problems/issues and that folk memory of possible fixes is also scattered. Having FreeBSD non-functional for dialup from home seems pretty unlikely: I must be doing something wrong locally. I can feel it in my bones... cheers! -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 20:29: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 36DCE14CB9 for ; Mon, 23 Aug 1999 20:29:04 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA06661; Mon, 23 Aug 1999 21:26:03 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA04652; Mon, 23 Aug 1999 21:26:02 -0600 Date: Mon, 23 Aug 1999 21:26:02 -0600 Message-Id: <199908240326.VAA04652@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: George Michaelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: SIO "lost interrupt" status in current? In-Reply-To: <199908240135.LAA15228@azure.dstc.edu.au> References: <199908240135.LAA15228@azure.dstc.edu.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm actually pretty sure it happens even without X11 live. This worries me! > changing the modem serial speed down from 57600 through 33600 to 19200 made > no difference. This also worries me. If the speed isn't being set down, then somehow interrupts are being turned off for a very long time, possibly by another device driver, or possibly you have bad hardware. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 20:46:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 662A715079 for ; Mon, 23 Aug 1999 20:46:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA12309; Mon, 23 Aug 1999 20:44:39 -0700 (PDT) (envelope-from dillon) Date: Mon, 23 Aug 1999 20:44:39 -0700 (PDT) From: Matthew Dillon Message-Id: <199908240344.UAA12309@apollo.backplane.com> To: "David O'Brien" Cc: current@FreeBSD.ORG, vladimir@math.uic.edu Subject: Re: NFSv3 on freebsd<-->solaris References: <19990823140608.A70275@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :am not implying that the problem might be on the FreeBSD side, it might :as well be a bug in solaris NFS implementation). : :I would greatly appreciate any help with the following problem. I have :a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 :client. I run into problems when trying to use NFSv3 mounts on the :client. Trying to remove files from the mounted partition (on the nfs :client) results in multiple errors, for example: : : # rm -r /home/2/vladimir : rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists : rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists : rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists : :I have tried using tcp and udp mount options with the same result. NFSv2 :works fine. : :Solaris client has the latest patches applied. I would very much appreciate :any comments on that. When you look at those directories on the server from the server are there any files left over? If so then the rm -r is somehow missing some files and then is unable to rmdir the directory because it isn't yet empty. -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 Aug 23 21:58:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from newton.math.uic.edu (dns.math.uic.edu [131.193.178.229]) by hub.freebsd.org (Postfix) with SMTP id 01DD614FE0 for ; Mon, 23 Aug 1999 21:58:36 -0700 (PDT) (envelope-from vladimir@math.uic.edu) Received: (qmail 17734 invoked from network); 24 Aug 1999 04:57:23 -0000 Received: from galois.math.uic.edu (HELO math.uic.edu) (131.193.178.114) by newton.math.uic.edu with SMTP; 24 Aug 1999 04:57:23 -0000 Received: (qmail 2402 invoked by uid 31415); 24 Aug 1999 04:57:22 -0000 Date: 24 Aug 1999 04:57:22 -0000 Message-ID: <19990824045722.2401.qmail@math.uic.edu> From: vladimir@math.uic.edu To: current@FreeBSD.ORG, dillon@apollo.backplane.com, obrien@NUXI.com Subject: Re: NFSv3 on freebsd<-->solaris Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From dillon@apollo.backplane.com Tue Aug 24 03:44:09 1999 >Delivered-To: vladimir@mailhost2.math.uic.edu >Delivered-To: vladimir@math.uic.edu >Date: Mon, 23 Aug 1999 20:44:39 -0700 (PDT) >From: Matthew Dillon >To: "David O'Brien" >Cc: current@FreeBSD.ORG, vladimir@math.uic.edu >Subject: Re: NFSv3 on freebsd<-->solaris > >:... >:am not implying that the problem might be on the FreeBSD side, it might >:as well be a bug in solaris NFS implementation). >: >:I would greatly appreciate any help with the following problem. I have >:a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 >:client. I run into problems when trying to use NFSv3 mounts on the >:client. Trying to remove files from the mounted partition (on the nfs >:client) results in multiple errors, for example: >: >: # rm -r /home/2/vladimir >: rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists >: rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists >: rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists >: >:I have tried using tcp and udp mount options with the same result. NFSv2 >:works fine. >: >:Solaris client has the latest patches applied. I would very much appreciate >:any comments on that. > > When you look at those directories on the server from the server are there any > files left over? There are files left over. > > If so then the rm -r is somehow missing some files and then is unable to > rmdir the directory because it isn't yet empty. I've run snoop on the client. Client's hostname is smb2 (Solaris 7), server is galileo (FBSD 3.2-STABLE, built on Aug 3). Output is below: smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=2C5A vladimir galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=9714 smb2.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=2C5A galileo.math.uic.edu -> smb2.math.uic.edu NFS R GETATTR3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=9714 galileo.math.uic.edu -> smb2.math.uic.edu NFS R GETATTR3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C READDIR3 FH=9714 Cookie=0 for 1048 galileo.math.uic.edu -> smb2.math.uic.edu NFS R READDIR3 OK 3 entries (No more) smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=9714 CVS galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=6447 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=6447read (read) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (read) smb2.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=6447 galileo.math.uic.edu -> smb2.math.uic.edu NFS R GETATTR3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=6447lookup (lookup) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (lookup) smb2.math.uic.edu -> galileo.math.uic.edu NFS C READDIR3 FH=6447 Cookie=0 for 1048 galileo.math.uic.edu -> smb2.math.uic.edu NFS R READDIR3 OK 3 entries (No more) smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=6447 blowup galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=8AB2 smb2.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=8AB2 galileo.math.uic.edu -> smb2.math.uic.edu NFS R GETATTR3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=8AB2 c galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=1C3C smb2.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=1C3C galileo.math.uic.edu -> smb2.math.uic.edu NFS R GETATTR3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C READDIR3 FH=1C3C Cookie=0 for 1048 galileo.math.uic.edu -> smb2.math.uic.edu NFS R READDIR3 OK 9 entries (More) smb2.math.uic.edu -> galileo.math.uic.edu NFS C READDIR3 FH=1C3C Cookie=1536 for 1048 galileo.math.uic.edu -> smb2.math.uic.edu NFS R READDIR3 OK 17 entries (No more) smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C print_ineq.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=4B03 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=4B03modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C print_ineq.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C print_mult_list.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=A985 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=A985modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C print_mult_list.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C print_times.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=0766 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=0766modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C print_times.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C proto.h,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=8861 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=8861modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C proto.h,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C readbranch.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=EED7 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=EED7modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C readbranch.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C resolve.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=C565 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=C565modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C resolve.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C reverse_mult_sequence.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=4F26 smb2.math.uic.edu -> galileo.math.uic.edu NFS C ACCESS3 FH=4F26modify,extend (modify,extend) galileo.math.uic.edu -> smb2.math.uic.edu NFS R ACCESS3 OK (modify,extend) smb2.math.uic.edu -> galileo.math.uic.edu NFS C REMOVE3 FH=1C3C reverse_mult_sequence.c,v galileo.math.uic.edu -> smb2.math.uic.edu NFS R REMOVE3 OK smb2.math.uic.edu -> galileo.math.uic.edu NFS C READDIR3 FH=1C3C Cookie=1536 for 1048 galileo.math.uic.edu -> smb2.math.uic.edu NFS R READDIR3 Readdir cookie is stale smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=1C3C .. galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=8AB2 smb2.math.uic.edu -> galileo.math.uic.edu NFS C RMDIR3 FH=8AB2 c galileo.math.uic.edu -> smb2.math.uic.edu NFS R RMDIR3 Directory not empty smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=8AB2 .. galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=6447 smb2.math.uic.edu -> galileo.math.uic.edu NFS C RMDIR3 FH=6447 blowup galileo.math.uic.edu -> smb2.math.uic.edu NFS R RMDIR3 Directory not empty smb2.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=6447 .. galileo.math.uic.edu -> smb2.math.uic.edu NFS R LOOKUP3 OK FH=9714 smb2.math.uic.edu -> galileo.math.uic.edu NFS C RMDIR3 FH=9714 CVS galileo.math.uic.edu -> smb2.math.uic.edu NFS R RMDIR3 Directory not empty smb2.math.uic.edu -> galileo.math.uic.edu NFS C RMDIR3 FH=2C5A vladimir galileo.math.uic.edu -> smb2.math.uic.edu NFS R RMDIR3 Directory not empty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 22: 3:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id B077714C0E for ; Mon, 23 Aug 1999 22:03:04 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 89D9F7C32; Tue, 24 Aug 1999 00:01:00 -0500 (CDT) From: Bruce Albrecht To: freebsd-current@freebsd.org Subject: panics in m_copym in kern/uipc_mbuf.c Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Message-Id: <19990824050100.89D9F7C32@mail.zuhause.org> Date: Tue, 24 Aug 1999 00:01:00 -0500 (CDT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started noticed this a couple of days ago, especially when when I'm doing a cvsup. I was originally running with -current from the end of July, but updated my -current box to late 8/22. What else should I be looking at? There are no error messages in /var/log/messages before the panic. #0 boot (howto=260) at ../../kern/kern_shutdown.c:281 #1 0xc0154f49 in panic (fmt=0xc0276844 "m_copym") at ../../kern/kern_shutdown.c:529 #2 0xc016d16a in m_copym (m=0xc0abcf80, off0=5736, len=342, wait=1) at ../../kern/uipc_mbuf.c:446 #3 0xc01a6a6b in tcp_output (tp=0xcbe2cba0) at ../../netinet/tcp_output.c:511 #4 0xc01a7ba9 in tcp_fasttimo () at ../../netinet/tcp_timer.c:106 #5 0xc016c94f in pffasttimo (arg=0x0) at ../../kern/uipc_domain.c:230 #6 0xc015966a in softclock () at ../../kern/kern_timeout.c:132 #7 0xc022e15e in doreti_swi () #8 0xc01fb409 in drain_output (vp=0xcbef19c0, islocked=1) at ../../ufs/ffs/ffs_softdep.c:4451 #9 0xc01fa3da in softdep_fsync_mountdev (vp=0xcbef19c0) at ../../ufs/ffs/ffs_softdep.c:3725 #10 0xc01fe7f6 in ffs_fsync (ap=0xcd3dbd1c) at ../../ufs/ffs/ffs_vnops.c:135 #11 0xc01fd05e in ffs_sync (mp=0xc0ec9000, waitfor=2, cred=0xc0a64880, p=0xc02e0ea0) at vnode_if.h:499 #12 0xc017e43f in sync (p=0xc02e0ea0, uap=0x0) at ../../kern/vfs_syscalls.c:545 #13 0xc015494b in boot (howto=256) at ../../kern/kern_shutdown.c:198 #14 0xc0154f49 in panic (fmt=0xc0276844 "m_copym") at ../../kern/kern_shutdown.c:529 #15 0xc016d16a in m_copym (m=0xc0abcf80, off0=5736, len=342, wait=1) at ../../kern/uipc_mbuf.c:446 #16 0xc01a6a6b in tcp_output (tp=0xcbe2cba0) at ../../netinet/tcp_output.c:511 #17 0xc01a5cb2 in tcp_input (m=0xc0abcd80, iphlen=20) at ../../netinet/tcp_input.c:1792 #18 0xc01a1538 in ip_input (m=0xc0abcd80) at ../../netinet/ip_input.c:679 #19 0xc01a1597 in ipintr () at ../../netinet/ip_input.c:706 #20 0xc022e1a5 in swi_net_next () #21 0xc024ecc1 in intr_mux (arg=0xc0a5d560) at ../../i386/isa/intr_machdep.c:549 #22 0x807b5d5 in ?? () Cannot access memory at address 0xf9c9e293. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 22: 8:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from mtiwmhc03.worldnet.att.net (mtiwmhc03.worldnet.att.net [204.127.131.38]) by hub.freebsd.org (Postfix) with ESMTP id CB839153A6 for ; Mon, 23 Aug 1999 22:08:48 -0700 (PDT) (envelope-from bsmith@mbnworld.com) Received: from default ([12.72.13.9]) by mtiwmhc03.worldnet.att.net (InterMail v03.02.07.07 118-134) with SMTP id <19990824021420.QOCO18791@default> for ; Tue, 24 Aug 1999 02:14:20 +0000 From: The Digital Brochure To: Subject: Introducing the Digital Brochure Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <19990824021420.QOCO18791@default> Date: Tue, 24 Aug 1999 02:14:20 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG HAVE YOU HEARD about Digital Brochure, the powerful new media tool which is helping Real Estate Agents throughout Europe sell properties more efficiently and more quickly? Digital Brochure is a highly compressed, e-mailable, electronic product which utilizes pictures, text, and sound. It is similar to a CD ROM, but due to its small size, can be e-mailed by you to potential buyers, providing full previews of likely properties, and increasing productivity, efficiency, and sales potential. Ø Each Digital Brochure includes exterior views (as desired) and interior views (two per room). Ø Using Digital Brochure, potential buyers will preview properties you select at their computers and at their convenience. Ø If a client does not have e-mail, you may send Digital Brochure on diskette by mail. Ø If you have your own Web Site, you may post Digital Brochures, making them available for all visitors to download and view. Ø If you do not have a Web Site, or if you have one but prefer not to post your Digital Brochures on it, we can post them for you free of charge on our Web Site. Visitors to your site would simply fill out a provided form, and the Digital Brochure you wish them to view would immediately download and arrive on their e-mail. Our Service Offers: 1) Professional photographers who will shoot listed properties by appointment at your convenience. 2) Digital Brochures created according to your instructions and delivered to you by e-mail. 3) Your Digital Brochures hosted on our Inflyer Web Site free of charge. Our Fees: One Digital Brochure, $125.00 Over ten Digital Brochures per month, $75.00 each (per house/property) OR: 0.1 percent of selling price (minimum $200.00) Fees include location shoot and Digital Brochure production. Contact us now to receive a sample by E-mail and we will produce your first Digital Brochure for FREE! INFLYER MBN ENTERTAINMENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 22:28:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5C6E915056 for ; Mon, 23 Aug 1999 22:28:24 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 11J96d-000Gn3-00; Tue, 24 Aug 1999 07:26:47 +0200 From: Sheldon Hearn To: Doug Cc: freebsd-current@FreeBSD.ORG, dbaker@distributed.net Subject: Re: Weird differences in rc5 behavior on -current vs. -stable In-reply-to: Your message of "Mon, 23 Aug 1999 10:47:05 MST." <37C18919.CE2F3130@gorean.org> Date: Tue, 24 Aug 1999 07:26:47 +0200 Message-ID: <64544.935472407@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Aug 1999 10:47:05 MST, Doug wrote: > How does that PR explain why rc5des with the same ini file is > running at nice 20 on -current, seemingly without idprio and running > at nice 0 on -stable, seemingly with it? Um, different nice levels. I didn't see that. Trigger happy. :-( Sorry, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:28:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 7474E15868 for ; Mon, 23 Aug 1999 23:28:46 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04661; Mon, 23 Aug 1999 23:28:13 -0700 (PDT) Date: Wed, 18 Aug 1999 11:39:22 -0700 (PDT) Message-Id: <199908240628.XAA04661@gilliam.users.flyingcroc.net> To: "Matt Crawford" Cc: "Pleschutznig, Andreas" , "'Leif Neland'" , current@FreeBSD.ORG Subject: Teergrubes [was Re: Dropping connections without RST] From: Joel Ray Holveck Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > process normally if the HELO and MAIL From/RCPT To look all right; > otherwise continue to read small gulps of the DATA at slow intervals, > then answer the final "." with a *temporary* failure code. I'd rather have spammers consume less of my CPU time and bandwidth, not have them keep coming back again and again. I suppose if you've got the computrons to waste, then it's okay. joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:29:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id D5EED157F0 for ; Mon, 23 Aug 1999 23:28:42 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04611; Mon, 23 Aug 1999 23:28:10 -0700 (PDT) Date: Wed, 18 Aug 1999 11:29:17 -0700 (PDT) Message-Id: <199908240628.XAA04611@gilliam.users.flyingcroc.net> To: Hidetoshi Shimokawa Cc: dillon@apollo.backplane.com, hasty@rah.star-gate.com, rb@gid.co.uk, current@FreeBSD.ORG Subject: Re: cd writer recommendation? From: Joel Ray Holveck Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For backup, I bought DVD-RAM drive for $400. > 5.2GB(double side) media is around $35, you can use them as 2.3GB x 2 > disks. No reason to buy double-sided media; just buy single-sided and punch a hole along the edge. :-) joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:29:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id EC358159A7 for ; Mon, 23 Aug 1999 23:29:29 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04623; Mon, 23 Aug 1999 23:28:11 -0700 (PDT) Date: Wed, 18 Aug 1999 11:35:02 -0700 (PDT) Message-Id: <199908240628.XAA04623@gilliam.users.flyingcroc.net> To: Amancio Hasty Cc: Richard Cownie , Alex Zepeda , freebsd-current@FreeBSD.ORG, tich@par28.ma.ikos.com Subject: SIGBUS [was Re: gdb] From: Joel Ray Holveck Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (gdb) run > Starting program: /tmp/./sieve > Program received signal SIGBUS, Bus error. That reminds me. I thought that SIGBUS meant byte-alignment errors. What does it mean on FreeBSD/x86? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:30: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 1F4141588C for ; Mon, 23 Aug 1999 23:28:56 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04729; Mon, 23 Aug 1999 23:28:20 -0700 (PDT) Date: Wed, 18 Aug 1999 12:03:33 -0700 (PDT) Message-Id: <199908240628.XAA04729@gilliam.users.flyingcroc.net> From: Chuck Gagnon To: "FreeBSD-current" Subject: bootparamd changed for use with inetd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've dug through the archives and found no mention of this subject. Are there any political/technical reasons why bootparamd was not set up to work with inetd? If the answer is no, I've included a patch for /usr/src/usr.sbin/bootparamd/bootparamd/main.c that allows it to work this way. I was also wondering if it would be more correct to put it in libexec under the name rpc.bootparamd if this patch were accepted? This does not break the ability to run it standalone. here is an example inetd.conf line I use: bootparamd/1 dgram rpc/udp wait root /usr/libexec/rpc.bootparamd rpc.bootparamd and under current naming sceme it would be: bootparamd/1 dgram rpc/udp wait root /usr/sbin/bootparamd bootparamd It accually boots my sparc10 just fine. In fact I can boot the sparc over 10T from my FBSD box faster than it boots from local disk :-) -- any theories on why? --- Chuck Gagnon (gagnocg@ev1.net) --- cut here ------ cut here ------ cut here --- begin 644 patch-aa M+2TM(&UA:6XN8RYOPHM"5-60UA04E0@*G1R86YS<#L*+0EI;G0@:3L*+0ES=')U8W0@ M:&]S=&5N="`J:&4["BT)PHM"0ER;W5T95]A9&1R(#T@:6YE=%]A M9&1R*&]P=&%R9RD["BT)"6)R96%K.PHM"2`@("`@('T@96QS92!["BT)"6AE M(#T@9V5T:&]S=&)Y;F%M92AO<'1APHK("`@(&-A2AH92T^:%]A9&1R+"`H8VAAPHK("`)("`@97)R>"@Q+"`B;F\@F5O9BAFPHK("`@(&9R;VU?:6YE=&0@/2`P.PHK("`@('-O8VL@/2!24$-?04Y94T]# M2SL**R`@("!PF5R M;R@H8VAAF5O M9B!FF5O M9B`H"@Q+"`B=6YA8FQE('1O(')E9VES M=&5R("A"3T]44$%204U04D]'+"!"3T]44$%204U615)3+"!U9'`I(BD["BL@ M('T**PHK("!I9B`HPHK("`@(&=E=%]M>6%D M9')E5]A9&1R+G-I;E]A9&1R M+G-?861DF5O9B`H"@Q+"`B=6YA8FQE('1O(')E9VES M=&5R("A"3T]44$%204U04D]'+"!"3T]44$%204U615)3+"!U9'`I(BD["B`* M+0ES=F-?"@Q+"`B&ET*#$I.PHK("!F<')I;G1F*'-T9&5R&ET*#$I.PHK?0HK"BMV;VED"BMC;&5A;G5P M*"D**WL**R`@*'9O:60I<&UA<%]U;G-E="A"3T]44$%204U04D]'+"!"3T]4 M4$%204U615)3*3L**R`@97AI="@P*3L**WT**PHK=F]I9`HK=7!D871EPHK("!U<&1A=&5S=&%T*"D["BL@(&EF("@A('-T871?:7-?:6YI="D* M*R`@("!S=&%T7VEN:70H*3L**R`@; Mon, 23 Aug 1999 23:28:58 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04745; Mon, 23 Aug 1999 23:28:20 -0700 (PDT) Date: Wed, 18 Aug 1999 12:09:12 -0700 (PDT) Message-Id: <199908240628.XAA04745@gilliam.users.flyingcroc.net> To: current@FreeBSD.ORG Subject: CD writer : Baby Hacker II From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1. Modify cdrecord so that if a device is not specified it will do a -scanbus . Present the user with a choice of cd recorders from which to chose from . Ideally there should be a generic device query interface to the system so other similar utilities can do the same thing . 2. Create an LDAP schema to store the configuration for cdrecord. the entry should have: host , InetOrgPerson, cd recorder brand/model, device name, scsibus address, CD-R speed, CD-RW speed... I can provide a servlet which can manage the configuration of the LDAP server. If you are interested on LDAP see: http://www.openldap.org and/or send me email. 3. A bit more dificult. Create a shared library module out of cdrecord with an interface similar to netscape's plug-in . Pick a graphical utility for instance gcombust and interface it to the plug-in. 4. Pie in the sky: Do step 2 and use xml as your protocol . For instance , if an app such gcombust sents a status query to the plug-in its response should be encapsulated in xml : detailing the device , current status : recording/pause/playing/stop. Enjoy -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:30:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F0C915134 for ; Mon, 23 Aug 1999 23:29:04 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04657; Mon, 23 Aug 1999 23:28:13 -0700 (PDT) Date: Wed, 18 Aug 1999 11:38:59 -0700 (PDT) Message-Id: <199908240628.XAA04657@gilliam.users.flyingcroc.net> From: brooks@one-eyed-alien.net To: Matthew Dillon Cc: Wilko Bulte , hasty@rah.star-gate.com, current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Aug 1999, Matthew Dillon wrote: > Remember that at least for the Yamaha you can set the speed to 6 if > you are burning CD-R's. 4 is the max for CD-RW's. When I last used cdrecord (on Solaris) I remember finding that if I tried to write with a speed that was too high for the media type (i.e. 2x on a 1x CD-RW writer) that the drive (an older Yamaha) did the right thing so you should be able to set the higher speed globaly. The only problem was that cdrecord didn't do the right thing so the time estimates were bogus. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:31: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 9916A158F9 for ; Mon, 23 Aug 1999 23:29:06 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04773; Mon, 23 Aug 1999 23:28:21 -0700 (PDT) Date: Wed, 18 Aug 1999 12:29:15 -0700 (PDT) Message-Id: <199908240628.XAA04773@gilliam.users.flyingcroc.net> Subject: Re: [re]writable cdrom drive To: hasty@rah.star-gate.com (Amancio Hasty) Cc: dillon@apollo.backplane.com (Matthew Dillon), wilko@yedi.iaf.nl (Wilko Bulte), current@FreeBSD.ORG From: "Kenneth D. Merry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote... > I have to agree with Matt on this plus the set of defaults is system wide . What are you agreeing with him on? Why not quote what you're talking about? > Is it possible to get a system bus enumeration from the system so > a program such a cdrecord can attempt to make an intelligent > decision as to which device is the cd recorder for instance we > know that the system can print the device's name and its > scsi address: If you want a bus number, there's a really easy way to get it: # camcontrol devlist at scbus0 target 3 lun 0 (pass0,ch0) at scbus0 target 4 lun 0 (pass1,sa0) at scbus1 target 0 lun 0 (pass2,da0) at scbus1 target 1 lun 0 (pass3,da1) at scbus1 target 3 lun 0 (pass4,cd0) at scbus1 target 6 lun 0 (pass5,cd1) at scbus2 target 0 lun 0 (pass6,da2) So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. cdrecord itself also has a slightly more obtuse way of doing the same thing: # cdrecord -scanbus Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling scsibus0: 0) * 1) * 2) * 3) 'EXABYTE ' 'EXB-10i ' '2.6 ' Removable Juke Box 4) 'EXABYTE ' 'EXB-8500-85Qanx0' '0415' Removable Tape 5) * 6) * 7) * scsibus1: 100) 'SEAGATE ' 'ST31230W ' '0510' Disk 101) 'SEAGATE ' 'ST32155N ' '0318' Disk 102) * 103) 'PLEXTOR ' 'CD-R PX-R412C ' '1.04' Removable CD-ROM 104) * 105) * 106) 'PLEXTOR ' 'CD-ROM PX-4XCS ' '1.04' Removable CD-ROM 107) * scsibus2: 200) 'SEAGATE ' 'ST34371N ' '0484' Disk 201) * 202) * 203) * 204) * 205) * 206) * 207) * The camcontrol output is easier to figure out, though. Ken -- Kenneth Merry ken@kdm.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 From owner-freebsd-current Mon Aug 23 23:31: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 116431590C for ; Mon, 23 Aug 1999 23:29:09 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04817; Mon, 23 Aug 1999 23:28:23 -0700 (PDT) Date: Wed, 18 Aug 1999 12:45:41 -0700 (PDT) Message-Id: <199908240628.XAA04817@gilliam.users.flyingcroc.net> Subject: Re: [re]writable cdrom drive To: hasty@rah.star-gate.com (Amancio Hasty) Cc: dillon@apollo.backplane.com, wilko@yedi.iaf.nl, current@FreeBSD.ORG From: "Kenneth D. Merry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote... > > Amancio Hasty wrote... > > > I have to agree with Matt on this plus the set of defaults is system wide . > > > > What are you agreeing with him on? Why not quote what you're talking > > about? > > > > > Is it possible to get a system bus enumeration from the system so > > > a program such a cdrecord can attempt to make an intelligent > > > decision as to which device is the cd recorder for instance we > > > know that the system can print the device's name and its > > > scsi address: > > > > If you want a bus number, there's a really easy way to get it: > > > > # camcontrol devlist > > at scbus0 target 3 lun 0 (pass0,ch0) > > at scbus0 target 4 lun 0 (pass1,sa0) > > at scbus1 target 0 lun 0 (pass2,da0) > > at scbus1 target 1 lun 0 (pass3,da1) > > at scbus1 target 3 lun 0 (pass4,cd0) > > at scbus1 target 6 lun 0 (pass5,cd1) > > at scbus2 target 0 lun 0 (pass6,da2) > > > > So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. > > > > cdrecord itself also has a slightly more obtuse way of doing the same > > thing: > > > > # cdrecord -scanbus > > Cdrecord release 1.8a22 Copyright (C) 1995-1999 J_rg Schilling > > scsibus0: > > 0) * > > 1) * [ ... ] > > The camcontrol output is easier to figure out, though. > > > > Ken > > This is about ease of use . cdrecord in the absence of a device specification > should > query the bus and present the user with a choice of cd recorder devices ideally > if there is one cd recorder it should go ahead an use it if such behavior is > not desired then create an option "--confirm" to ask the user if its okay > to use the "guessed" cd recorder. If you think cdrecord should do something different, talk to Joerg Schilling about it. > camcontrol is a generic scsi command line interface and very nice . What I am > after > is a generic bus enumerator API so apps like cd recorder or fxtv can use > to locate the device in the absence of a specified device. There is a generic SCSI bus enumerator API, and one for PCI as well. There isn't a generic API to get trees of devices of any type in the system, though. With new-bus that might be possible, but having done two enumerator APIs already (I wrote the CAM and PCI enumerator code), I can predict that it might be very complicated to do properly. (Things get really hairy when you have to keep the device tree from changing while you're traversing it.) In any case, for the two applications you specified, cdrecord is only interested in SCSI devices, and there is already an API -- that cdrecord already supports -- to do bus/device enumeration. The cdrecord -scanbus code already uses that API. Similarly, there is already a PCI device listing interface, so fxtv should be able to easily pull out the devices it is interested in. All it has to do is search for all "meteor" or "bktr" devices to find what it wants. Ken -- Kenneth Merry ken@kdm.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 From owner-freebsd-current Mon Aug 23 23:31:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id A7D7E1591D for ; Mon, 23 Aug 1999 23:29:11 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04837; Mon, 23 Aug 1999 23:28:28 -0700 (PDT) Date: Wed, 18 Aug 1999 12:55:51 -0700 (PDT) Message-Id: <199908240628.XAA04837@gilliam.users.flyingcroc.net> From: Doug Ambrisko Subject: Re: cd writer recommendation? To: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin S. Brackett writes: | Oh, well then, :) I'm glad I said something before I actually bought one | (I saw the atapi RW drives were rather cheap now (~US$125)) I think that most IDE CD-R/CD-RW will just work using Soren's ata driver in current. I'm doing that on my laptop right now with a hacked pccard and hacked ata driver. Also I have an external IDE hard disk as well. I do have a problem with buffer underflows when do a mkisofs to a 4X write over PCMCIA. 2X works fine. BTW I'm using a Sony drive. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:31:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 0218C15908 for ; Mon, 23 Aug 1999 23:29:09 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04797; Mon, 23 Aug 1999 23:28:22 -0700 (PDT) Date: Wed, 18 Aug 1999 12:41:27 -0700 (PDT) Message-Id: <199908240628.XAA04797@gilliam.users.flyingcroc.net> To: "Kenneth D. Merry" Cc: dillon@apollo.backplane.com (Matthew Dillon), wilko@yedi.iaf.nl (Wilko Bulte), current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Amancio Hasty wrote... > > I have to agree with Matt on this plus the set of defaults is system wide . > > What are you agreeing with him on? Why not quote what you're talking > about? > > > Is it possible to get a system bus enumeration from the system so > > a program such a cdrecord can attempt to make an intelligent > > decision as to which device is the cd recorder for instance we > > know that the system can print the device's name and its > > scsi address: > > If you want a bus number, there's a really easy way to get it: > > # camcontrol devlist > at scbus0 target 3 lun 0 (pass0,ch0) > at scbus0 target 4 lun 0 (pass1,sa0) > at scbus1 target 0 lun 0 (pass2,da0) > at scbus1 target 1 lun 0 (pass3,da1) > at scbus1 target 3 lun 0 (pass4,cd0) > at scbus1 target 6 lun 0 (pass5,cd1) > at scbus2 target 0 lun 0 (pass6,da2) > > So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. > > cdrecord itself also has a slightly more obtuse way of doing the same > thing: > > # cdrecord -scanbus > Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling > scsibus0: > 0) * > 1) * > 2) * > 3) 'EXABYTE ' 'EXB-10i ' '2.6 ' Removable Juke Box > 4) 'EXABYTE ' 'EXB-8500-85Qanx0' '0415' Removable Tape > 5) * > 6) * > 7) * > scsibus1: > 100) 'SEAGATE ' 'ST31230W ' '0510' Disk > 101) 'SEAGATE ' 'ST32155N ' '0318' Disk > 102) * > 103) 'PLEXTOR ' 'CD-R PX-R412C ' '1.04' Removable CD-ROM > 104) * > 105) * > 106) 'PLEXTOR ' 'CD-ROM PX-4XCS ' '1.04' Removable CD-ROM > 107) * > scsibus2: > 200) 'SEAGATE ' 'ST34371N ' '0484' Disk > 201) * > 202) * > 203) * > 204) * > 205) * > 206) * > 207) * > > The camcontrol output is easier to figure out, though. > > Ken This is about ease of use . cdrecord in the absence of a device specification should query the bus and present the user with a choice of cd recorder devices ideally if there is one cd recorder it should go ahead an use it if such behavior is not desired then create an option "--confirm" to ask the user if its okay to use the "guessed" cd recorder. camcontrol is a generic scsi command line interface and very nice . What I am after is a generic bus enumerator API so apps like cd recorder or fxtv can use to locate the device in the absence of a specified device. Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:31:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 87B0A15947 for ; Mon, 23 Aug 1999 23:29:14 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04841; Mon, 23 Aug 1999 23:28:28 -0700 (PDT) Date: Wed, 18 Aug 1999 12:56:33 -0700 (PDT) Message-Id: <199908240628.XAA04841@gilliam.users.flyingcroc.net> To: "Kenneth D. Merry" Cc: dillon@apollo.backplane.com, wilko@yedi.iaf.nl, current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Amancio Hasty wrote... > > > Amancio Hasty wrote... > > > > I have to agree with Matt on this plus the set of defaults is system wide . > > > > > > What are you agreeing with him on? Why not quote what you're talking > > > about? > > > > > > > Is it possible to get a system bus enumeration from the system so > > > > a program such a cdrecord can attempt to make an intelligent > > > > decision as to which device is the cd recorder for instance we > > > > know that the system can print the device's name and its > > > > scsi address: > > > > > > If you want a bus number, there's a really easy way to get it: > > > > > > # camcontrol devlist > > > at scbus0 target 3 lun 0 (pass0,ch0) > > > at scbus0 target 4 lun 0 (pass1,sa0) > > > at scbus1 target 0 lun 0 (pass2,da0) > > > at scbus1 target 1 lun 0 (pass3,da1) > > > at scbus1 target 3 lun 0 (pass4,cd0) > > > at scbus1 target 6 lun 0 (pass5,cd1) > > > at scbus2 target 0 lun 0 (pass6,da2) > > > > > > So, in this case, the bus,target,lun combination for my CD-R is 1,3,0. > > > > > > cdrecord itself also has a slightly more obtuse way of doing the same > > > thing: > > > > > > # cdrecord -scanbus > > > Cdrecord release 1.8a22 Copyright (C) 1995-1999 J_rg Schilling > > > scsibus0: > > > 0) * > > > 1) * > > [ ... ] > > > > The camcontrol output is easier to figure out, though. > > > > > > Ken > > > > This is about ease of use . cdrecord in the absence of a device specification > > should > > query the bus and present the user with a choice of cd recorder devices ideally > > if there is one cd recorder it should go ahead an use it if such behavior is > > not desired then create an option "--confirm" to ask the user if its okay > > to use the "guessed" cd recorder. > > If you think cdrecord should do something different, talk to Joerg > Schilling about it. > > > camcontrol is a generic scsi command line interface and very nice . What I am > > after > > is a generic bus enumerator API so apps like cd recorder or fxtv can use > > to locate the device in the absence of a specified device. > > There is a generic SCSI bus enumerator API, and one for PCI as well. There > isn't a generic API to get trees of devices of any type in the system, > though. With new-bus that might be possible, but having done two > enumerator APIs already (I wrote the CAM and PCI enumerator code), I can > predict that it might be very complicated to do properly. (Things get > really hairy when you have to keep the device tree from changing while > you're traversing it.) > > In any case, for the two applications you specified, cdrecord is only > interested in SCSI devices, and there is already an API -- that cdrecord > already supports -- to do bus/device enumeration. The cdrecord -scanbus > code already uses that API. > > Similarly, there is already a PCI device listing interface, so fxtv should > be able to easily pull out the devices it is interested in. All it has to > do is search for all "meteor" or "bktr" devices to find what it wants. > > Ken Now how can I map a device name from this bus enumeration so that I can issue an "open" to the device: pciconf -l chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 hdr=0x00 isab0@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 hdr=0x00 ide_pci0@pci0:1:1: class=0x010180 card=0x00000000 chip=0x70108086 rev=0x00 hdr=0x00 chip1@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70208086 rev=0x01 hdr=0x00 de0@pci0:9:0: class=0x020000 card=0x11001385 chip=0x00091011 rev=0x22 hdr=0x00 bktr0@pci0:10:0: class=0x040000 card=0x13eb0070 chip=0x036e109e rev=0x02 hdr=0x00 none0@pci0:10:1: class=0x048000 card=0x13eb0070 chip=0x0878109e rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 hdr=0x00 ahc1@pci0:12:0: class=0x010000 card=0x00000000 chip=0x71789004 rev=0x03 hdr=0x00 vga-pci0@pci0:13:0: class=0x030000 card=0x00000000 chip=0x0519102b rev=0x01 hdr=0x00 -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:31:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 725EA15946 for ; Mon, 23 Aug 1999 23:29:14 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04853; Mon, 23 Aug 1999 23:28:29 -0700 (PDT) Date: Wed, 18 Aug 1999 12:58:34 -0700 (PDT) Message-Id: <199908240628.XAA04853@gilliam.users.flyingcroc.net> Subject: Re: [re]writable cdrom drive To: hasty@rah.star-gate.com (Amancio Hasty) Cc: dillon@apollo.backplane.com, wilko@yedi.iaf.nl, current@FreeBSD.ORG From: "Kenneth D. Merry" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote... > > There is a generic SCSI bus enumerator API, and one for PCI as well. There > > isn't a generic API to get trees of devices of any type in the system, > > though. With new-bus that might be possible, but having done two > > enumerator APIs already (I wrote the CAM and PCI enumerator code), I can > > predict that it might be very complicated to do properly. (Things get > > really hairy when you have to keep the device tree from changing while > > you're traversing it.) > > > > In any case, for the two applications you specified, cdrecord is only > > interested in SCSI devices, and there is already an API -- that cdrecord > > already supports -- to do bus/device enumeration. The cdrecord -scanbus > > code already uses that API. > > > > Similarly, there is already a PCI device listing interface, so fxtv should > > be able to easily pull out the devices it is interested in. All it has to > > do is search for all "meteor" or "bktr" devices to find what it wants. > > > > Ken > > Now how can I map a device name from this bus enumeration so that I can issue > an "open" to the device: > > pciconf -l > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 > hdr=0x00 > isab0@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 > hdr=0x00 > ide_pci0@pci0:1:1: class=0x010180 card=0x00000000 chip=0x70108086 > rev=0x00 hdr=0x00 > chip1@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70208086 rev=0x01 > hdr=0x00 > de0@pci0:9:0: class=0x020000 card=0x11001385 chip=0x00091011 rev=0x22 > hdr=0x00 > bktr0@pci0:10:0: class=0x040000 card=0x13eb0070 chip=0x036e109e > rev=0x02 hdr=0x00 > none0@pci0:10:1: class=0x048000 card=0x13eb0070 chip=0x0878109e > rev=0x02 hdr=0x00 > ahc0@pci0:11:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 > hdr=0x00 > ahc1@pci0:12:0: class=0x010000 card=0x00000000 chip=0x71789004 rev=0x03 > hdr=0x00 > vga-pci0@pci0:13:0: class=0x030000 card=0x00000000 chip=0x0519102b > rev=0x01 hdr=0x00 Only one of the above devices actually has a character device interface in /dev. All you have to do is something like this: sprintf(foo, "/dev/%s%d", p->pd_name, p->pd_unit); The only way it would become complicated is if the device name in the kernel were different than the device name in /dev. Ken -- Kenneth Merry ken@kdm.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 From owner-freebsd-current Mon Aug 23 23:32: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id B21BE15968 for ; Mon, 23 Aug 1999 23:29:17 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04885; Mon, 23 Aug 1999 23:28:30 -0700 (PDT) Date: Wed, 18 Aug 1999 13:19:16 -0700 (PDT) Message-Id: <199908240628.XAA04885@gilliam.users.flyingcroc.net> From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Doug Ambrisko Cc: current@FreeBSD.ORG Subject: Re: cd writer recommendation? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Aug 1999, Doug Ambrisko wrote: > I think that most IDE CD-R/CD-RW will just work using Soren's ata driver > in current. I'm doing that on my laptop right now with a hacked pccard and > hacked ata driver. Also I have an external IDE hard disk as well. I do have > a problem with buffer underflows when do a mkisofs to a 4X write over > PCMCIA. 2X works fine. Making your dd blocksize a multiple (say 10) of physical blocksize should cure this. I use something like: AUBLKSIZE=2352 AUWRSIZE=5 AURDSIZE=`expr $AUWRSIZE '*' 2` OBS=`expr $AUBLKSIZE '*' $AUWRSIZE` IBS=`expr $AUBLKSIZE '*' $AURDSIZE` rtprio 5 team -v 1m 5 <$1 | \ rtprio 4 dd ibs=$IBS of=$WORM obs=$OBS conv=osync || exit ymmv, Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:37:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id D0C8915929 for ; Mon, 23 Aug 1999 23:34:14 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id IAA24845; Tue, 24 Aug 1999 08:33:02 +0200 (MET DST) Date: Tue, 24 Aug 1999 08:32:47 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Mike Muir Cc: freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. In-Reply-To: <37C1E9BD.F3584C38@es.co.nz> 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 you running CURRENT? Could you check whether you have at least rev. 101 of src/sys/i386/apm/apm.c Nick 1.101 Sun Aug 22 14:48:00 1999 UTC by iwasaki Diffs to 1.100 Fix `key release event prevent suspend' problem. We don't need `sleep 1; zzz' trick now. - APM BIOS Call for suspend/standby now should be issued with delay. - Delay for suspend/standby can be adjusted by using sysctl(8) interface (eg. sysctl -w machdep.apm_suspend_delay=3). On Tue, 24 Aug 1999, Mike Muir wrote: > Ive been following the apm problems and changes in apm threads in hope > that I would fix the problems that I too am having. > > I am using the latest sources for apm, apmconf and apmd, as well as the > kernel. (as of 23/8/99, NZST, which is yesterday evening) > > dmesg is: > > apm0: on motherboard > apm: APM BIOS version 0102 > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > apm: CS_limit=0xffff, DS_limit=0xffff > apm: Engaged control enabled > apm: found APM BIOS v1.2, connected at v1.2 > apm: Slow Idling CPU enabled > Add hook "default suspend" > Add hook "default resume" > ---and then later on > psm0: irq 12 on atkbdc0 > Add hook "PS/2 mouse" > > after going 'apmconf -e' > apm shows: > > APM version: 1.2 > APM Managment: Enabled > AC Line status: on-line > > Resume timer: disabled > Resume on ring indicator: enabled > APM Capacities: > global standby state > global suspend state > resume timer from standby > resume timer from suspend > > ---- > 'apm -Z' for standby jumps into standby mode for like.. an instant, then > comes right back out (while playing mp3) > > dmesg: > > APM ioctl: cmd = 0x2000500c > Received APM Event: PMEV_STANDBYRESUME > Execute APM hook "default resume." > resumed from suspended mode (slept 00:00:00) > Execute APM hook "PS/2 mouse." > > 'zzz' or 'apm -z' for suspend jumps into suspend mode, and just the same > way, comes right back out (while playing mp3s again) > > dmesg: > > APM ioctl: cmd = 0x20005001 > Execute APM hook "default suspend." > Received APM Event: PMEV_NORMRESUME > Execute APM hook "default resume." > resumed from suspended mode (slept 00:00:01) > Execute APM hook "PS/2 mouse." > > it should be noted that the cpu fan does turn off momentarily for both > of these events, and the mp3 that is playing stops, then starts up again > where it left off. > Even without playing anything through the sound device, it does the same > thing. > If i leave the thing on with no activity, while running apmd, it goes > into suspend or standby (depending on the timers set in the bios) every > now and again, but jumps back out as soon as it does. > Also, all the PM timer interrupts are disabled. > > Motherboard is an Abit BH-6 > > cheers, > mike. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:41:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 289451547E for ; Mon, 23 Aug 1999 23:41:30 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA01409; Tue, 24 Aug 1999 08:39:26 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908240639.IAA01409@freebsd.dk> Subject: Re: problem with the ata driver In-Reply-To: <19990823230625.37897@breizh.teaser.fr> from Nicolas Souchu at "Aug 23, 1999 11: 6:25 pm" To: nsouch@teaser.fr (Nicolas Souchu) Date: Tue, 24 Aug 1999 08:39:25 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nicolas Souchu wrote: > On Mon, Aug 23, 1999 at 08:27:15AM +0200, Soren Schmidt wrote: > > > >It seems Nicolas Souchu wrote: > >> acd0: CDROM drive at ata0 as master > >> acd0: drive speed 0KB/sec > >> acd0: supported read types: > >> acd0: Mechanism: caddy > >> acd0: Medium: CD-ROM unknown medium > >> > >> Any clue? > >> > >> The drive was running flawlessly with the old wdc driver and with various > >> primary releases of the new ata driver (some, not all). > > > >Hmm, looks like the timeout I've chosen for timing out on the probes > >*might* be too short for some devices.. > > Which ones, I found nothing in the LINT file related to ATA. "There is no user serviceable parts inside" :) and if patch someone just posted works it seems like the drive is abusing the standard. I'll look at it asap, then lets see how far it comes... -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 Aug 23 23:44:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 71DAE1576A for ; Mon, 23 Aug 1999 23:42:05 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04865; Mon, 23 Aug 1999 23:28:29 -0700 (PDT) Date: Wed, 18 Aug 1999 13:09:41 -0700 (PDT) Message-Id: <199908240628.XAA04865@gilliam.users.flyingcroc.net> To: "Kenneth D. Merry" Cc: dillon@apollo.backplane.com, wilko@yedi.iaf.nl, current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Amancio Hasty wrote... > > > There is a generic SCSI bus enumerator API, and one for PCI as well. There > > > isn't a generic API to get trees of devices of any type in the system, > > > though. With new-bus that might be possible, but having done two > > > enumerator APIs already (I wrote the CAM and PCI enumerator code), I can > > > predict that it might be very complicated to do properly. (Things get > > > really hairy when you have to keep the device tree from changing while > > > you're traversing it.) > > > > > > In any case, for the two applications you specified, cdrecord is only > > > interested in SCSI devices, and there is already an API -- that cdrecord > > > already supports -- to do bus/device enumeration. The cdrecord -scanbus > > > code already uses that API. > > > > > > Similarly, there is already a PCI device listing interface, so fxtv should > > > be able to easily pull out the devices it is interested in. All it has to > > > do is search for all "meteor" or "bktr" devices to find what it wants. > > > > > > Ken > > > > Now how can I map a device name from this bus enumeration so that I can issue > > an "open" to the device: > > > > pciconf -l > > chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x12378086 rev=0x02 > > hdr=0x00 > > isab0@pci0:1:0: class=0x060100 card=0x00000000 chip=0x70008086 rev=0x01 > > hdr=0x00 > > ide_pci0@pci0:1:1: class=0x010180 card=0x00000000 chip=0x70108086 > > rev=0x00 hdr=0x00 > > chip1@pci0:1:2: class=0x0c0300 card=0x00000000 chip=0x70208086 rev=0x01 > > hdr=0x00 > > de0@pci0:9:0: class=0x020000 card=0x11001385 chip=0x00091011 rev=0x22 > > hdr=0x00 > > bktr0@pci0:10:0: class=0x040000 card=0x13eb0070 chip=0x036e109e > > rev=0x02 hdr=0x00 > > none0@pci0:10:1: class=0x048000 card=0x13eb0070 chip=0x0878109e > > rev=0x02 hdr=0x00 > > ahc0@pci0:11:0: class=0x010000 card=0x00000000 chip=0x81789004 rev=0x00 > > hdr=0x00 > > ahc1@pci0:12:0: class=0x010000 card=0x00000000 chip=0x71789004 rev=0x03 > > hdr=0x00 > > vga-pci0@pci0:13:0: class=0x030000 card=0x00000000 chip=0x0519102b > > rev=0x01 hdr=0x00 > > Only one of the above devices actually has a character device interface in > /dev. All you have to do is something like this: > > sprintf(foo, "/dev/%s%d", p->pd_name, p->pd_unit); > > The only way it would become complicated is if the device name in the > kernel were different than the device name in /dev. > > Ken Or if there is a system call or modification to open such that I can issue : open("pci0:10:0", .....) On the kernel side, I hope that the pci code can translate a bus enumeration to an actual major , minor device. The only problem that I see with such an approach is security and I would rather deal with that later. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:46:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id B5CCE1593C for ; Mon, 23 Aug 1999 23:45:43 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id IAA40250 for ; Tue, 24 Aug 1999 08:44:25 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id IAA16458 for freebsd-current@freebsd.org; Tue, 24 Aug 1999 08:44:25 +0200 (CEST) Date: Tue, 24 Aug 1999 08:44:25 +0200 From: Cejka Rudolf To: freebsd-current@freebsd.org Subject: Re: Any chances to solve bin/7973? Message-ID: <19990824084425.A15735@dcse.fee.vutbr.cz> References: <19990823223742.A6198@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Garance A Drosihn on Mon, Aug 23, 1999 at 04:56:27PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn wrote (1999/08/23): > Why would the filter be reading the control file? It is just a > filter, supposedly reading from stdin and writing to stdout... Yes and not. You can look into apsfilter for example. It gets from control file JOB, USER and HOST items in case of ASCII input printing. This information is used for "better" printing - ASCII input is converted into PostScript and some additional headers are added: "Printed by USER from HOST', "JOB name", date of printing and others. Why we should lose this feature? (But I don't know, if there is any other and better way how to fix this problem.) -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:47:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id CCEFF15831 for ; Mon, 23 Aug 1999 23:47:21 -0700 (PDT) (envelope-from ross@gilliam.users.flyingcroc.net) Received: (from ross@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) id XAA04869; Mon, 23 Aug 1999 23:28:29 -0700 (PDT) Date: Wed, 18 Aug 1999 13:13:05 -0700 (PDT) Message-Id: <199908240628.XAA04869@gilliam.users.flyingcroc.net> From: Garrett Wollman To: Amancio Hasty Cc: "Kenneth D. Merry" , dillon@apollo.backplane.com, wilko@yedi.iaf.nl, current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Or if there is a system call or modification to open such that I can issue : > open("pci0:10:0", .....) Don't be silly. > On the kernel side, I hope that the pci code can translate a bus enumeration > to an actual major , minor device. No, it knows nothing about special files, nor should it. -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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 23 23:49: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id D261215810 for ; Mon, 23 Aug 1999 23:49:00 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id QAA18879; Tue, 24 Aug 1999 16:48:27 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: nate@mt.sri.com (Nate Williams) Cc: freebsd-current@FreeBSD.ORG Subject: Re: SIO "lost interrupt" status in current? In-reply-to: Your message of "Mon, 23 Aug 1999 21:26:02 CST." <199908240326.VAA04652@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Aug 1999 16:48:19 +1000 Message-ID: <16540.935477299@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm actually pretty sure it happens even without X11 live. This worries m e! > changing the modem serial speed down from 57600 through 33600 to 19200 ma de > no difference. This also worries me. If the speed isn't being set down, then somehow interrupts are being turned off for a very long time, possibly by another device driver, or possibly you have bad hardware. If interrupts were off, wouldn't I see other things like mice freezes or X-repaint problems? I'd go with either of these actually. Any suggestions for debug methods? (for instance, would swapping the sio used for mouse and modem make sense? or do they use common paths in the motherboard such that a fault in serial is going to kill both of them..) I would *love* this to turn out to be hardware! cheers -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 0:22:42 1999 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 6F0131585A for ; Tue, 24 Aug 1999 00:22:37 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id AAA38003; Tue, 24 Aug 1999 00:01:04 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908240701.AAA38003@gndrsh.dnsmgr.net> Subject: Re: [re]writable cdrom drive In-Reply-To: <199908240628.XAA04869@gilliam.users.flyingcroc.net> from Garrett Wollman at "Aug 18, 1999 01:13:05 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 24 Aug 1999 00:01:04 -0700 (PDT) Cc: hasty@rah.star-gate.com (Amancio Hasty), ken@kdm.org (Kenneth D. Merry), dillon@apollo.backplane.com, wilko@yedi.iaf.nl, 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 Ahhh.. did we just experience a major time warp some place? I just received about 15 messages I know I have read before, all dated 18 Aug 1999. > < said: > > > Or if there is a system call or modification to open such that I can issue : > > open("pci0:10:0", .....) > > Don't be silly. > > > On the kernel side, I hope that the pci code can translate a bus enumeration > > to an actual major , minor device. > > No, it knows nothing about special files, nor should it. > > -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 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX - (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 Tue Aug 24 0:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-1.uoregon.edu (metriclient-1.uoregon.edu [128.223.172.1]) by hub.freebsd.org (Postfix) with ESMTP id B578414EB8 for ; Tue, 24 Aug 1999 00:48:52 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-1.uoregon.edu (8.9.1/8.8.7) id AAA21315; Tue, 24 Aug 1999 00:47:58 -0700 (PDT) Message-ID: <19990824004758.37930@hydrogen.fircrest.net> Date: Tue, 24 Aug 1999 00:47:58 -0700 From: John-Mark Gurney To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG Subject: Re: [re]writable cdrom drive References: <199908240628.XAA04869@gilliam.users.flyingcroc.net> <199908240701.AAA38003@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199908240701.AAA38003@gndrsh.dnsmgr.net>; from Rodney W. Grimes on Tue, Aug 24, 1999 at 12:01:04AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodney W. Grimes scribbled this message on Aug 24: > Ahhh.. did we just experience a major time warp some place? I just > received about 15 messages I know I have read before, all dated > 18 Aug 1999. if you notice that the bottoms have TWO unsubscribe messages attached.. looks like someone acidentally mailed a set of messages or something... I've mailed jmb about it... [actual message deleted] > > 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 one and then two... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 1: 1:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id A3A3315476 for ; Tue, 24 Aug 1999 01:01:05 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id RAA18761; Tue, 24 Aug 1999 17:59:40 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma018751; Tue, 24 Aug 99 17:59:24 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id RAA27940; Tue, 24 Aug 1999 17:59:24 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id RAA27240; Tue, 24 Aug 1999 17:59:25 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id RAA14712; Tue, 24 Aug 1999 17:59:22 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908240759.RAA14712@nymph.detir.qld.gov.au> To: Peter Jeremy Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Softupdates reliability? References: <99Aug24.075148est.40322@border.alcanet.com.au> In-Reply-To: <99Aug24.075148est.40322@border.alcanet.com.au> from Peter Jeremy at "Tue, 24 Aug 1999 07:52:41 +1000" Date: Tue, 24 Aug 1999 17:59:22 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 24th August 1999, Peter Jeremy wrote: >The exact order of events is not clear from this. In general, I'd say >that if something managed to upset the SCSI bus sufficiently to >confuse every target on it, then there's a reasonably likelihood that >data transfers were also corrupted. A serious bus corruption during a >disk write (either command or data phase) would have a reasonable >chance of resulting in corrupt data on the disk (either the wrong data >in the right place or the right data in the wrong place). Yes, I can't tell whether the confused SCSI adapter upset the Exabyte and maybe zero'd some disk sectors, or whether the Exabyte went bananas first and took out everything else. This system gets a LOT of use (I'm using it right now), but the Exabyte obviously isn't used as often as the disks. I might move the Exabyte on to an aha1542 as a precaution. >I'm not sure how to go about isolating the problem. I don't suppose >you happened to bump one of the cables, or suffer a power glitch? No power glitch or bumped cables. All quality gear, no overclocking, good cooling, surge suppressors, etc. I don't like "It was just one of those things". That's not how computers work. I've either got bad hardware or there are bugs. To counter the bugs, I'm about to go to the latest -stable. Bad hardware will show itself eventually. What I really should do is build a test system with softupdates and crash it a lot. (Using DDB to pause, then switch off, so no partial writes.) Could take a while... Oh, and Brian wanted to know the processor revision. I don't know of any problems with K6-2/300s, but here's the info: CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 2:13:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by hub.freebsd.org (Postfix) with ESMTP id EEC241576C; Tue, 24 Aug 1999 02:13:27 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix10.ix.netcom.com (8.8.4/8.8.4) id EAA25688; Tue, 24 Aug 1999 04:10:04 -0500 (CDT) Received: from sji-ca5-176.ix.netcom.com(209.109.234.176) by dfw-ix10.ix.netcom.com via smap (V1.3) id rma025673; Tue Aug 24 04:09:36 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id CAA11296; Tue, 24 Aug 1999 02:09:32 -0700 (PDT) To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: whither readline.h? References: <199908231219.FAA07566@silvia.hip.berkeley.edu> <19990823095451.A52275@dragon.nuxi.com> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 24 Aug 1999 02:09:31 -0700 In-Reply-To: "David O'Brien"'s message of "Mon, 23 Aug 1999 09:54:51 -0700" Message-ID: Lines: 12 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * > /usr/include/readline/readline.h (and whatever else that's supposed to * > be in that directory) has been missing from 4-current and 3-stable * > snaps for awhile. Does anyone know why? * * I just checked that cd /usr/src/gnu/lib/libreadline ; make obj all install * does the right thing. Ideas where to look next? I dunno. Maybe the release Makefiles? (Jordan CC'd) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 2:14: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id 018D615880 for ; Tue, 24 Aug 1999 02:14:03 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p90-max8.dun.ihug.co.nz [216.132.34.94]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id VAA12877; Tue, 24 Aug 1999 21:11:27 +1200 Message-ID: <37C261A2.A4FDF587@es.co.nz> Date: Tue, 24 Aug 1999 21:10:58 +1200 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Nick Hibma Cc: freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeh, i just got all the latest sources (as of 24th August) and made em: $Id: apm.c,v 1.103 1999/08/23 20:58:36 phk Exp $ So yes i do have that recent version, but my problems persist. :( Nick Hibma wrote: > > Are you running CURRENT? > > Could you check whether you have at least rev. 101 of > src/sys/i386/apm/apm.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 3: 8:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A52861504E for ; Tue, 24 Aug 1999 03:08:25 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA26393; Tue, 24 Aug 1999 12:00:11 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA55756; Tue, 24 Aug 1999 00:43:00 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908232243.AAA55756@yedi.iaf.nl> Subject: Re: Softupdates reliability? In-Reply-To: <99Aug24.075148est.40322@border.alcanet.com.au> from Peter Jeremy at "Aug 24, 1999 7:52:41 am" To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Date: Tue, 24 Aug 1999 00:43:00 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Peter Jeremy wrote ... > Stephen McKay wrote: > >I was extracting from the Exabyte to the DDRS disk while applying a CTM > >update from that disk against one of the DCAS disks when it crashed. The > >Exabyte went wonky (took about 6 goes to get the tape ejected) and the > >rest of the disk system locked up. The SCSI adapter was so confused I > >had to power down. > > The exact order of events is not clear from this. In general, I'd say > that if something managed to upset the SCSI bus sufficiently to > confuse every target on it, then there's a reasonably likelihood that > data transfers were also corrupted. A serious bus corruption during a > disk write (either command or data phase) would have a reasonable > chance of resulting in corrupt data on the disk (either the wrong data > in the right place or the right data in the wrong place). Hmm. I would generally expect SCSI errors etc to occur. Assuming the driver reports those one would at least know the bus was whacko. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Aug 24 3:16:21 1999 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 2EAD714EA1; Tue, 24 Aug 1999 03:16:08 -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 LAA09964; Tue, 24 Aug 1999 11:56:30 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199908240956.LAA09964@zibbi.mikom.csir.co.za> Subject: Re: whither readline.h? In-Reply-To: from Satoshi - Ports Wraith - Asami at "Aug 24, 1999 02:09:31 am" To: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: Tue, 24 Aug 1999 11:56:30 +0200 (SAT) Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG, jkh@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 > * From: "David O'Brien" > > * > /usr/include/readline/readline.h (and whatever else that's supposed to > * > be in that directory) has been missing from 4-current and 3-stable > * > snaps for awhile. Does anyone know why? > * > * I just checked that cd /usr/src/gnu/lib/libreadline ; make obj all install > * does the right thing. Ideas where to look next? > > I dunno. Maybe the release Makefiles? (Jordan CC'd) > It is probably because /usr/src/gnu/lib/libreadline/Makefile use bsd.subdir.mk and not bsd.lib.mk. Their distribute targets are different. I don't know if you can just slot bsd.lib.mk in there because the libreadline have some subdirs that have to be handled. 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 Aug 24 4:13:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 205A515096 for ; Tue, 24 Aug 1999 04:13:13 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id NAA84461 for ; Tue, 24 Aug 1999 13:11:40 +0200 (CEST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id NAA23951 for current@FreeBSD.ORG; Tue, 24 Aug 1999 13:11:40 +0200 (CEST) Date: Tue, 24 Aug 1999 13:11:39 +0200 From: Cejka Rudolf To: current@FreeBSD.ORG Subject: Re: NFSv3 on freebsd<-->solaris Message-ID: <19990824131139.A23427@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from David O'Brien on Mon, Aug 23, 1999 at 02:06:08PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote (1999/08/23): > - ----- Forwarded message from vladimir@math.uic.edu ----- > Solaris 7 machines cannot use NFSv3 mounts from a FreeBSD NFS server. > ... > # rm -r /home/2/vladimir > rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists > ... Yes, this is very well known problem. Please look at kern/5890 (by Remy Nonnenmacher). In our environment we had to use suggested patch to use FreeBSD as NFS server and Solaris NFS clients (v3). There was another discussion about it in the middle of November 1998 (initiated by me and followed by helpful answer from Remy) on -current mailing list. As I see, the kern/5890 is stopped with following question: Hi Remy, (Sat Apr 25 22:21:50 PDT 1998) Can you retest this bug? Peter made many changes to sys/nfs/nfs_serv.c over the summer. From the commit logs, I suspect it might be fixed. I can answer: Yes, the problem is still here (3.2-RELEASE and -CURRENT). I am closely observing cvs logs and looking for fix because this is unpleasant bug for us - but latest fix for readdirplus() still didn't help... (What about new kernel compilation option SOLARIS_NFSV3 or new sysctl variable? :-) -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 9:21:17 1999 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 4102F159D1; Tue, 24 Aug 1999 09:20:52 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id IAA99443; Tue, 24 Aug 1999 08:01:43 -0700 (PDT) (envelope-from green@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: green owned process doing -bs Date: Tue, 24 Aug 1999 08:01:43 -0700 (PDT) From: "Brian F. Feldman" To: Stephen McKay Cc: Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-Reply-To: <199908240759.RAA14712@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Aug 1999, Stephen McKay wrote: > > Oh, and Brian wanted to know the processor revision. I don't know of any > problems with K6-2/300s, but here's the info: > > CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > Features=0x8001bf You have one of the first K6-2s off the line. There were definite problems with these, and as such, they were specially distinguished by having 66 printed on top. What is your FSB running at? These chips (the very early 300s) can not handle >66MHz, and I've had a K6-2 0x580 go _completely_ bad easily. For peace of mind, even if it's not the problem (which it very well could be), I'd upgrade to a later revision. You can get one of these relatively cheap: CPU: AMD-K6(tm) 3D processor (350.81-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 > > Stephen > -- Brian Fundakowski Feldman / "Any sufficiently advanced bug is \ green@FreeBSD.org | indistinguishable from a feature." | FreeBSD: The Power to Serve! \ -- Rich Kulawiec / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 9:41:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 9B91215985 for ; Tue, 24 Aug 1999 09:31:47 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA12446; Tue, 24 Aug 1999 08:57:44 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA06970; Tue, 24 Aug 1999 08:57:43 -0600 Date: Tue, 24 Aug 1999 08:57:43 -0600 Message-Id: <199908241457.IAA06970@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: George Michaelson Cc: nate@mt.sri.com (Nate Williams), freebsd-current@FreeBSD.ORG Subject: Re: SIO "lost interrupt" status in current? In-Reply-To: <16540.935477299@dstc.edu.au> References: <199908240326.VAA04652@mt.sri.com> <16540.935477299@dstc.edu.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm actually pretty sure it happens even without X11 live. This worries m > e! > > changing the modem serial speed down from 57600 through 33600 to 19200 ma > de > > no difference. This also worries me. > > If the speed isn't being set down, then somehow interrupts are being > turned off for a very long time, possibly by another device driver, or > possibly you have bad hardware. > > If interrupts were off, wouldn't I see other things like mice freezes or > X-repaint problems? Nope, because they are less sensitive to the timing then serial lines. > I'd go with either of these actually. Any suggestions for debug methods? Look through the mailing lists. I'm sure Bruce had some debug ideas in the past. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 11:11:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from newton.math.uic.edu (dns.math.uic.edu [131.193.178.229]) by hub.freebsd.org (Postfix) with SMTP id CFDE114D4C for ; Tue, 24 Aug 1999 11:11:40 -0700 (PDT) (envelope-from vladimir@math.uic.edu) Received: (qmail 28292 invoked from network); 24 Aug 1999 18:10:42 -0000 Received: from galois.math.uic.edu (HELO math.uic.edu) (131.193.178.114) by newton.math.uic.edu with SMTP; 24 Aug 1999 18:10:42 -0000 Received: (qmail 4492 invoked by uid 31415); 24 Aug 1999 18:10:40 -0000 Date: 24 Aug 1999 18:10:40 -0000 Message-ID: <19990824181040.4491.qmail@math.uic.edu> From: vladimir@math.uic.edu To: freebsd-current@freebsd.org Subject: Re: NFSv3 on freebsd<-->solaris Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following advice from Cejka Rudolf , I have edited /src/sys/nfs/nfs_syscalls.c (commented out the lines after the "Solaris 2.5" comment). The "File exists" errors went away, everything seemed normal, but then I ran into another problem. mailx on solaris client could not lock the mailbox file anymore. The snoop output is below (I am not an NFS guru, but hope it will be useful to somebody). Here galileo is the FBSD server, galois is a Solaris 7 NFS client. Why would solaris machine make a request with vers=4: galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP ? (am I right that vers here is the same as the NFS version)? Vladimir PS I am not sure these questions are appropriate for this list, please direct me to some other resource if this is not the case. Thanks! galois.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=6CF3 Maildir galileo.math.uic.edu -> galois.math.uic.edu NFS R LOOKUP3 OK FH=20ED galois.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=9EF4 galileo.math.uic.edu -> galois.math.uic.edu NFS R GETATTR3 OK galois.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=B452 galileo.math.uic.edu -> galois.math.uic.edu NFS R GETATTR3 OK galois.math.uic.edu -> galileo.math.uic.edu NFS C GETATTR3 FH=107B galileo.math.uic.edu -> galois.math.uic.edu NFS R GETATTR3 OK galois.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=92D1 vladimir galileo.math.uic.edu -> galois.math.uic.edu NFS R LOOKUP3 OK FH=6CF3 galois.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=6CF3 Mailbox galileo.math.uic.edu -> galois.math.uic.edu NFS R LOOKUP3 OK FH=0BEF galois.math.uic.edu -> galileo.math.uic.edu NFS C LOOKUP3 FH=6CF3 Mailbox galileo.math.uic.edu -> galois.math.uic.edu NFS R LOOKUP3 OK FH=0BEF galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP galileo.math.uic.edu -> galois.math.uic.edu PORTMAP R GETPORT port=1005 galois.math.uic.edu -> galileo.math.uic.edu NLM C LOCK4 OH=1FAB FH=0BEF PID=4106 Region=0:0 galileo.math.uic.edu -> galois.math.uic.edu RPC R (#17) XID=4282729491 Program number mismatch (low=1, high=3) galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP galileo.math.uic.edu -> galois.math.uic.edu PORTMAP R GETPORT port=1005 galois.math.uic.edu -> galileo.math.uic.edu NLM C UNLOCK4 OH=1FAC FH=0BEF PID=4106 Region=0:0 galileo.math.uic.edu -> galois.math.uic.edu RPC R (#21) XID=4282729493 Program number mismatch (low=1, high=3) > >From dillon@apollo.backplane.com Tue Aug 24 03:44:09 1999 > >Delivered-To: vladimir@mailhost2.math.uic.edu > >Delivered-To: vladimir@math.uic.edu > >Date: Mon, 23 Aug 1999 20:44:39 -0700 (PDT) > >From: Matthew Dillon > >To: "David O'Brien" > >Cc: current@FreeBSD.ORG, vladimir@math.uic.edu > >Subject: Re: NFSv3 on freebsd<-->solaris > > > >:... > >:am not implying that the problem might be on the FreeBSD side, it might > >:as well be a bug in solaris NFS implementation). > >: > >:I would greatly appreciate any help with the following problem. I have > >:a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 > >:client. I run into problems when trying to use NFSv3 mounts on the > >:client. Trying to remove files from the mounted partition (on the nfs > >:client) results in multiple errors, for example: > >: > >: # rm -r /home/2/vladimir > >: rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists > >: rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists > >: rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists > >: > >:I have tried using tcp and udp mount options with the same result. NFSv2 > >:works fine. > >: > >:Solaris client has the latest patches applied. I would very much appreciate > >:any comments on that. > > > > When you look at those directories on the server from the server are there any > > files left over? > >There are files left over. > > > > > If so then the rm -r is somehow missing some files and then is unable to > > rmdir the directory because it isn't yet empty. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 11:24:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 6C37E14A2F for ; Tue, 24 Aug 1999 11:24:27 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA08431 for current@freebsd.org; Tue, 24 Aug 1999 14:26:28 -0400 From: Bill Paul Message-Id: <199908241826.OAA08431@skynet.ctr.columbia.edu> Subject: Monday part II: The Terror Continues To: current@freebsd.org Date: Tue, 24 Aug 1999 14:26:27 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1659 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So today my ISA bus is detected properly and the kernel gets as far as trying to launch /stand/sysinstall, but then, just when I thought it was safe to try and load a new snapshot: rootfs is 2880 Kbyte compiled in MFS spec_getpages: I/O read failure: (error code=0) bp 0xc34fc3a0 vp 0xc7ed8ec0 size: 0, resid: 0, a_count: 49152, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 12 exec /stand/sysinstall: error 5 init: not found panic: no init This has nothing to do with the 486 though; I tried it on a laptop that was handy and it blew up the same way. I tried yesterday's mfsroot image and it doesn't work with that either. The August 16th snapshot's kernel and mfsroot images seem to work. The August 16th snapshot's kernel and yesterday's mfsroot image also works. This is the third unusable snap in a row that I've had the misfortune to encounter. I'm starting to think this is more than a coincidence. Did somebody launch a "Piss Bill Off" contest when I wasn't looking or something? If so, let me stress that you really don't want to find out what first prize is. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 11:37:42 1999 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 6C4F3150E2 for ; Tue, 24 Aug 1999 11:37:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA01837; Tue, 24 Aug 1999 20:36:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: Monday part II: The Terror Continues In-reply-to: Your message of "Tue, 24 Aug 1999 14:26:27 EDT." <199908241826.OAA08431@skynet.ctr.columbia.edu> Date: Tue, 24 Aug 1999 20:36:28 +0200 Message-ID: <1835.935519788@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just found out myself, fix (I hope) committed. >spec_getpages: I/O read failure: (error code=0) bp 0xc34fc3a0 vp 0xc7ed8ec0 > size: 0, resid: 0, a_count: 49152, valid: 0x0 > nread: 0, reqpage: 0, pindex: 0, pcount: 12 -- 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 Aug 24 12:41:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 484C614C41; Tue, 24 Aug 1999 12:41:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA02697; Wed, 25 Aug 1999 05:38:31 +1000 Date: Wed, 25 Aug 1999 05:38:31 +1000 From: Bruce Evans Message-Id: <199908241938.FAA02697@godzilla.zeta.org.au> To: asami@FreeBSD.ORG, jhay@mikom.csir.co.za Subject: Re: whither readline.h? Cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG, obrien@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It is probably because /usr/src/gnu/lib/libreadline/Makefile use >bsd.subdir.mk and not bsd.lib.mk. Their distribute targets are different. >I don't know if you can just slot bsd.lib.mk in there because the >libreadline have some subdirs that have to be handled. I think using bsd.subdir.mk is an error if there is anything more to be done than traversing subdirs. bsd.subdir.mk is mainly for optimising this special case. Using bsd.lib.mk would be bogus since there are no libraries to be made, and in fact it seems to be broken (it attempts to handle "lib.a"). bsd.prog.mk is supposed to be usable here and seems to work right for normal builds. We use it routinely in similar (but more top heavy) setups elsewhere. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 13:53: 2 1999 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 ABCBE15202 for ; Tue, 24 Aug 1999 13:52:53 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA00460; Tue, 24 Aug 1999 15:52:15 -0500 (CDT) Date: Tue, 24 Aug 1999 15:52:15 -0500 From: "Matthew D. Fuller" To: Doug Rabson Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: Monday strikes again Message-ID: <19990824155215.J28846@futuresouth.com> References: <199908231835.OAA06292@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Doug Rabson on Mon, Aug 23, 1999 at 09:44:10PM +0100 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 23, 1999 at 09:44:10PM +0100, a little birdie told me that Doug Rabson remarked > > It seems like isa bus is never being attached for some reason. Have a > look at nexus_attach() and see if anything suspicious is happening (like > an error return from device_probe_and_attach()). FWIW, I've been getting a panic on bootup for months (mid-April, maybe?) on -CURRENT on one of my systems; could this be at all related? Here is some info from the panic I got mid-late April. I'll try cvsup'ing and building a new kernel tonite and see if it's fixed, but in case it isn't here's some info. Bootup gets to here: isab0: at device 15.0 on pci0 and them *boom* Fatal trap 12: page fault while in kernel mode fault virtual address = 0x24000208 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01456f5 stack pointer = 0x10:0xc02d5ef8 frame pointer = 0x10:0xc02d5f04 code segment = base 0x0, limit 0xfffff, type 0x1b = DRL 0, pres 1, def32 1, gran 1 processor eflags = interrupts enabled, resume, IOPL=0 current process = 0 ( ) interrupt mask = net tty bio cam kernel: type 12 trap, code:0 DDB reveals Stopped at device_probe_and_attach+0x9 movl 0x8(%ebx),%edi trace shows: device_probe_and_attach(24000200) at device_probe_and_attach+0x9 bus_generic_attach(c09e1880, c02d5f38, c0145737, c09e1880, c09e1880) at bus_generic_attach+0x16 DEVICE_ATTACH(c09e1880, c09e1880, 0, c061cb40, c02d5f48) at DEVICE_ATTACH+0x25 -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "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 Aug 24 14: 6:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 9E4691516C for ; Tue, 24 Aug 1999 14:06:46 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA43044; Tue, 24 Aug 1999 17:06:43 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <19990824084425.A15735@dcse.fee.vutbr.cz> References: <19990823223742.A6198@dcse.fee.vutbr.cz> <19990824084425.A15735@dcse.fee.vutbr.cz> Date: Tue, 24 Aug 1999 17:07:09 -0400 To: Cejka Rudolf , freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Any chances to solve bin/7973? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:44 AM +0200 8/24/99, Cejka Rudolf wrote: >Garance A Drosihn wrote (1999/08/23): > > > Why would the filter be reading the control file? It is just a > > filter, supposedly reading from stdin and writing to stdout... > >Yes and not. > >You can look into apsfilter for example. It gets from control file >JOB, USER and HOST items in case of ASCII input printing. This >information is used for "better" printing - ASCII input is converted >into PostScript and some additional headers are added: "Printed by USER >from HOST', "JOB name", date of printing and others. Why we should >lose this feature? (But I don't know, if there is any other and better >way how to fix this problem.) My own preference is to get lpd to set environment variables for this sort of thing. That way the values could be effected by other inputs (printcap entries, etc). I don't have any deep-seated objection to your change (and my opinion doesn't really count for much even if I did... :-), but my general preference is that nothing but the lpr/lpd programs should have any idea of the format (or even existence) of the control file. In the specific case of USER and HOST, aren't those already passed as parameters to the filter? We have a somewhat customized print empire here at RPI, but I believe it's true that the distributed lpd starts up a print-filter with '-n -h '. At one point we added another parameter to this list, only to find out that it broke several of the filter scripts we use. Thus, I went with environment variables. :-) --- 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 Tue Aug 24 14:21:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.free.fr (smtp2.free.fr [212.27.32.6]) by hub.freebsd.org (Postfix) with ESMTP id 59722151A8 for ; Tue, 24 Aug 1999 14:21:11 -0700 (PDT) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-53-204.dial.proxad.net [212.27.53.204]) by smtp2.free.fr (8.9.3/8.9.3/Debian/GNU) with ESMTP id XAA28426; Tue, 24 Aug 1999 23:18:51 +0200 Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id VAA00883; Tue, 24 Aug 1999 21:42:50 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990824214250.44680@breizh.teaser.fr> Date: Tue, 24 Aug 1999 21:42:50 +0200 From: Nicolas Souchu To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with the ata driver References: <19990823230625.37897@breizh.teaser.fr> <199908240639.IAA01409@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: <199908240639.IAA01409@freebsd.dk>; from Soren Schmidt on Tue, Aug 24, 1999 at 08:39:25AM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 24, 1999 at 08:39:25AM +0200, Soren Schmidt wrote: >> Which ones, I found nothing in the LINT file related to ATA. > >"There is no user serviceable parts inside" :) and if patch someone just >posted works it seems like the drive is abusing the standard. I'll look >at it asap, then lets see how far it comes... Ok nice, let me know. > >-Søren > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 14:58:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8C313151D5 for ; Tue, 24 Aug 1999 14:58:30 -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.1) with ESMTP id OAA01216; Tue, 24 Aug 1999 14:56:31 -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 OAA78568; Tue, 24 Aug 1999 14:56:31 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 24 Aug 1999 14:56:31 -0700 (PDT) Message-Id: <199908242156.OAA78568@vashon.polstra.com> To: jkh@zippy.cdrom.com Subject: Re: libalias or libnat. Vote ? In-Reply-To: <3843.935363694@localhost> References: <3843.935363694@localhost> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3843.935363694@localhost>, Jordan K. Hubbard wrote: > > I've been on both sides of this issue, to be sure, but I have to say > that looking at it now, I can't see any reason to change the actual > name of the library right now unless we're also going to go whole-hog > and change the API functions to PacketNATFoo() and such, something > that would only really make sense (or be worth the effort, anyway) if > we had a bunch of improvements to bring in at the same time, e.g. a > significant rearchitecting effort. > > If we don't have anything like that planned, then simply changing the > user visible flags and man pages to strongly encourage use of -nat > style options rather than the deprecated -alias ones will probably > be enough of a step in the right direction for now. I agree. Users don't know or care about the name of the library. Programmers are used to dealing with quirks like having NAT implemented in a library named libalias. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 15:11: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (Postfix) with ESMTP id BB3DE15261; Tue, 24 Aug 1999 15:10:56 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by stevenson.cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id XAA01479; Tue, 24 Aug 1999 23:09:59 +0100 (BST) Date: Tue, 24 Aug 1999 23:09:58 +0100 Message-Id: <550.199908242209@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Softupdates reliability? To: "Brian F. Feldman" , Stephen McKay In-Reply-To: Brian F. Feldman's message of Tue, 24 Aug 1999 08:01:43 -0700 (PDT) Organization: just say no Cc: Peter Jeremy , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > You have one of the first K6-2s off the line. There were definite problems > with these, and as such, they were specially distinguished by having 66 > printed on top. I have a 0x580 which has had no problems at all. I'm pretty certain it doesn't have 66 stamped on it. Are they all supposed to have this, or were they tested and the dodgy ones stamped 66? -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 15:35:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by hub.freebsd.org (Postfix) with ESMTP id DFE5D15273; Tue, 24 Aug 1999 15:35:34 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix10.ix.netcom.com (8.8.4/8.8.4) id RAA03213; Tue, 24 Aug 1999 17:34:02 -0500 (CDT) Received: from sji-ca5-176.ix.netcom.com(209.109.234.176) by dfw-ix10.ix.netcom.com via smap (V1.3) id rma003174; Tue Aug 24 17:33:32 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id PAA14601; Tue, 24 Aug 1999 15:33:20 -0700 (PDT) To: Bruce Evans Cc: jhay@mikom.csir.co.za, current@FreeBSD.ORG, jkh@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: whither readline.h? References: <199908241938.FAA02697@godzilla.zeta.org.au> From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 24 Aug 1999 15:33:20 -0700 In-Reply-To: Bruce Evans's message of "Wed, 25 Aug 1999 05:38:31 +1000" Message-ID: Lines: 18 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bruce Evans * I think using bsd.subdir.mk is an error if there is anything more to * be done than traversing subdirs. bsd.subdir.mk is mainly for optimising * this special case. * * Using bsd.lib.mk would be bogus since there are no libraries to be made, * and in fact it seems to be broken (it attempts to handle "lib.a"). * * bsd.prog.mk is supposed to be usable here and seems to work right for * normal builds. We use it routinely in similar (but more top heavy) * setups elsewhere. Ok, can someone with a release build setup try this? Or should I just take Bruce's word and commit the bsd.subdir.mk -> bsd.prog.mk change to /usr/src/gnu/lib/libreadline/Makefile ? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 15:48:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9810C158A8 for ; Tue, 24 Aug 1999 15:48:17 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA32529; Wed, 25 Aug 1999 00:33:52 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA70386; Tue, 24 Aug 1999 23:52:42 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908242152.XAA70386@yedi.iaf.nl> Subject: Re: Monday part II: The Terror Continues In-Reply-To: <199908241826.OAA08431@skynet.ctr.columbia.edu> from Bill Paul at "Aug 24, 1999 2:26:27 pm" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 24 Aug 1999 23:52:42 +0200 (CEST) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Bill Paul wrote ... [...] > This is the third unusable snap in a row that I've had the misfortune > to encounter. I'm starting to think this is more than a coincidence. Did > somebody launch a "Piss Bill Off" contest when I wasn't looking or > something? If so, let me stress that you really don't want to find out > what first prize is. Not me. But I do assume you played an appropriate CD in the background? By the "Boom Town Rats" ? ;-) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Aug 24 17:43: 4 1999 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 510C114BCE; Tue, 24 Aug 1999 17:43:02 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA48812; Tue, 24 Aug 1999 17:39:56 -0700 (PDT) (envelope-from green@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: green owned process doing -bs Date: Tue, 24 Aug 1999 17:39:56 -0700 (PDT) From: "Brian F. Feldman" To: Richard Tobin Cc: Stephen McKay , Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-Reply-To: <550.199908242209@doyle.cogsci.ed.ac.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 Tue, 24 Aug 1999, Richard Tobin wrote: > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > > You have one of the first K6-2s off the line. There were definite problems > > with these, and as such, they were specially distinguished by having 66 > > printed on top. > > I have a 0x580 which has had no problems at all. I'm pretty certain > it doesn't have 66 stamped on it. Are they all supposed to have this, > or were they tested and the dodgy ones stamped 66? It must be the latter. My 0x580 had the 66, so it must be that the dodgy ones got labelled 66 and not all the 0x580s were defective. > > -- Richard > -- Brian Fundakowski Feldman / "Any sufficiently advanced bug is \ green@FreeBSD.org | indistinguishable from a feature." | FreeBSD: The Power to Serve! \ -- Rich Kulawiec / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 17:55:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id ABBA3151B7 for ; Tue, 24 Aug 1999 17:54:59 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id IAA08283 for ; Wed, 25 Aug 1999 08:52:12 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id IAA04918 for ; Wed, 25 Aug 1999 08:53:40 +0800 (WST) Received: from ariadne.prth.tensor.pgs.com by ariadne.tensor.pgs.com (8.9.1b+Sun/SMI-SVR4) id IAA21394; Wed, 25 Aug 1999 08:53:41 +0800 (WST) Message-Id: <199908250053.IAA21394@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: New kernel crashes as of yesterday Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Aug 1999 08:53:41 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the vm subsystem changes that went in yesterday, I expierence crashes under heavy load situations (typically when running quake2 in OpenGL mode). A kernel built on the 23rd works fine. A kernel backtrace follows # gdb -k kernel.debug /var/crash/vmcore.12 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3088384 initial pcb at 27a000 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x28 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01647fa stack pointer = 0x10:0xc58ecdd0 frame pointer = 0x10:0xc58ecddc 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 = 2 (pagedaemon) interrupt mask = net bio cam trap number = 12 panic: page fault syncing disks... 3 done dumping to dev (116,1), offset 483456 dump 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 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 281 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 #1 0xc0131741 in panic (fmt=0xc024cfaf "page fault") at ../../kern/kern_shutdown.c:529 #2 0xc0210fc6 in trap_fatal (frame=0xc58ecd90, eva=40) at ../../i386/i386/trap.c:907 #3 0xc0210c79 in trap_pfault (frame=0xc58ecd90, usermode=0, eva=40) at ../../i386/i386/trap.c:800 #4 0xc02108e7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = 34, tf_ebp = -980496932, tf_isp = -980496964, tf_ebx = -1044768408, tf_edx = -980496860, tf_ecx = 34, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072281606, tf_cs = 8, tf_eflags = 66195, tf_esp = -1044768408, tf_ss = -1065942592}) at ../../i386/i386/trap.c:426 #5 0xc01647fa in spec_strategy (ap=0xc58ece24) at ../../miscfs/specfs/spec_vnops.c:549 #6 0xc0163f69 in spec_vnoperate (ap=0xc58ece24) at ../../miscfs/specfs/spec_vnops.c:124 #7 0xc01cfc9d in ufs_vnoperatespec (ap=0xc58ece24) at ../../ufs/ufs/ufs_vnops.c:2330 #8 0xc01d10f0 in swap_pager_putpages (object=0xc5fc6dac, m=0xc58eced4, count=1, sync=0, rtvals=0xc58ece68) at vnode_if.h:891 #9 0xc01cfd07 in default_pager_putpages (object=0xc5fc6dac, m=0xc58eced4, c=1, sync=0, rtvals=0xc58ece68) at ../../vm/default_pager.c:137 #10 0xc01daf47 in vm_pageout_flush (mc=0xc58eced4, count=1, flags=0) at ../../vm/vm_pager.h:145 #11 0xc01daea5 in vm_pageout_clean (m=0xc046ea10) at ../../vm/vm_pageout.c:339 #12 0xc01db7d6 in vm_pageout_scan () at ../../vm/vm_pageout.c:917 #13 0xc01dc0a9 in vm_pageout () at ../../vm/vm_pageout.c:1348 #14 0xc0204d40 in fork_trampoline () Cannot access memory at address 0xa000. (kgdb) -- 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 Tue Aug 24 18:15:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 84C0815145 for ; Tue, 24 Aug 1999 18:15:30 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id VAA25664; Tue, 24 Aug 1999 21:21:28 -0400 (EDT) Date: Tue, 24 Aug 1999 21:21:27 -0400 (EDT) From: Alfred Perlstein To: vladimir@math.uic.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFSv3 on freebsd<-->solaris In-Reply-To: <19990824181040.4491.qmail@math.uic.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Aug 1999 vladimir@math.uic.edu wrote: > Following advice from Cejka Rudolf , I have edited > /src/sys/nfs/nfs_syscalls.c (commented out the lines after the "Solaris 2.5" > comment). The "File exists" errors went away, everything seemed normal, > but then I ran into another problem. mailx on solaris > client could not lock the mailbox file anymore. The snoop output is > below (I am not an NFS guru, but hope it will be useful to somebody). > Here galileo is the FBSD server, galois is a Solaris 7 NFS client. > Why would solaris machine make a request with vers=4: > galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP > ? > (am I right that vers here is the same as the NFS version)? The NLM version 4 protocol is not supported, I am working on this. Question: did you delete both checks after the Solaris 2.5 mention? or just one? which one? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 19:34:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 67CAC1593B; Tue, 24 Aug 1999 19:34:50 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id MAA03843; Wed, 25 Aug 1999 12:34:26 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma003808; Wed, 25 Aug 99 12:34:19 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA13294; Wed, 25 Aug 1999 12:34:18 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id MAA01581; Wed, 25 Aug 1999 12:34:17 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id MAA09128; Wed, 25 Aug 1999 12:34:17 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908250234.MAA09128@nymph.detir.qld.gov.au> To: "Brian F. Feldman" Cc: Richard Tobin , Stephen McKay , Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: K6-2 revisions (was: Re: Softupdates reliability?) References: In-Reply-To: from "Brian F. Feldman" at "Tue, 24 Aug 1999 17:39:56 -0700" Date: Wed, 25 Aug 1999 12:34:16 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 24th August 1999, "Brian F. Feldman" wrote: >On Tue, 24 Aug 1999, Richard Tobin wrote: > >> > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 >> >> > You have one of the first K6-2s off the line. There were definite problems >> > with these, and as such, they were specially distinguished by having 66 >> > printed on top. >> >> I have a 0x580 which has had no problems at all. I'm pretty certain >> it doesn't have 66 stamped on it. Are they all supposed to have this, >> or were they tested and the dodgy ones stamped 66? > >It must be the latter. My 0x580 had the 66, so it must be that the dodgy >ones got labelled 66 and not all the 0x580s were defective. I think the story went along the lines that AMD were making K6-2/300's for a while, then went to a less rigorous test procedure for just a short time until they realised that some of the processors they released wouldn't work at 100MHz bus speeds, though they were ok at 66MHz. So they went back to the better testing procedure for the 100MHz models, but also released some 66MHz only models. Mine was indeed one of the earliest, but there have been no problem with it, and during my strange disk crash the CPU kept updating the X11 load graph and stuff. The problem(s) must be elsewhere. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 20:16:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0AFB1152B8 for ; Tue, 24 Aug 1999 20:16:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA23429; Tue, 24 Aug 1999 20:16:03 -0700 (PDT) (envelope-from dillon) Date: Tue, 24 Aug 1999 20:16:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199908250316.UAA23429@apollo.backplane.com> To: Luigi Rizzo Cc: julian@whistle.com (Julian Elischer), phk@critter.freebsd.dk, bde@zeta.org.au, jb@cimlogic.com.au, atrens@nortelnetworks.com, current@FreeBSD.ORG Subject: VN fixed References: <199908221115.NAA05282@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have submitted a patch to DG that fixes VN for CURRENT. Since VN is currently broken on CURRENT, the patch is on a fast-track for commit. I've include the patch below, but beware that it may be committed quickly. This also fixes swap-backed VN. The -S option can be applied to files now and two new options -T (truncate/create file) and -Z (write zero's to file to pre-allocate the file blocks) have been added. Example usage: vnconfig -e -s labels -T -Z -S 64m /dev/vn0 /usr/obj/test disklabel -w -r vn0 auto newfs /dev/rvn0c mount /dev/vn0c ....some_mount_point.... ... umount ....the_mount_point... vnconfig -u /dev/vn0 The VN device can also be used with direct-swap backing store by not specifying a backing file. Note that the sector size is the system page size (4K on intel). vnconfig -e -s labels -S 256m /dev/vn0 disklabel -w -r vn0 auto newfs /dev/rvn0c mount /dev/vn0c ....some_mount_point.... ... umount ....the_mount_point... vnconfig -u /dev/vn0 Performance: The VN device operates as a raw disk device. This means that 'disk I/O' operations are written to the underlying storage whereas with MFS 'disk I/O' operations are written to memory. VN should be reasonably efficient memory-wise at the cost of some performance (e.g. the I/O performed). MFS is less memory efficient (each cached block exists in main memory twice instead of once) but if you have lots of memory MFS will not perform any I/O. Note that VN does take advantage of the VM cache, of course, because the filesystem running on top of it caches things in the VM cache. What does this mean? For small filesystems use MFS. For large filesystems use VN. Use of file-backed vs swap-backed VN. It's your choice. A swap-backed VN device has lower I/O overhead but is not persistant and you must be sure to have sufficient swap to hold the entire size of the VN device to avoid running the system out of swap if someone fills up the VN partition. file-backed storage can be made persistant (you can even run fsck on the file prior to mounting it). -Matt Index: sys/vm/vm_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_pager.c,v retrieving revision 1.51 diff -u -r1.51 vm_pager.c --- vm_pager.c 1999/07/05 12:50:54 1.51 +++ vm_pager.c 1999/08/25 02:20:02 @@ -566,6 +566,7 @@ nbp->b_bufsize = nbp->b_bcount; if ((nbp->b_flags & B_READ) == 0) nbp->b_dirtyend = nbp->b_bcount; + BUF_KERNPROC(nbp); VOP_STRATEGY(nbp->b_vp, nbp); } else { biodone(nbp); Index: sys/vm/swap_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v retrieving revision 1.124 diff -u -r1.124 swap_pager.c --- swap_pager.c 1999/08/23 23:55:03 1.124 +++ swap_pager.c 1999/08/25 02:20:42 @@ -857,6 +857,7 @@ if (nbp == NULL) { nbp = getchainbuf(bp, swapdev_vp, B_READ|B_ASYNC); nbp->b_blkno = blk; + nbp->b_bcount = 0; nbp->b_data = data; } nbp->b_bcount += PAGE_SIZE; Index: sys/dev/vn/vn.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vn/vn.c,v retrieving revision 1.86 diff -u -r1.86 vn.c --- vn.c 1999/08/23 20:35:16 1.86 +++ vn.c 1999/08/25 02:21:50 @@ -207,18 +207,23 @@ static int vnopen(dev_t dev, int flags, int mode, struct proc *p) { - int unit; struct vn_softc *vn; - unit = dkunit(dev); - vn = dev->si_drv1; - if (!vn) + /* + * Locate preexisting device + */ + + if ((vn = dev->si_drv1) == NULL) vn = vnfindvn(dev); IFOPT(vn, VN_FOLLOW) printf("vnopen(%s, 0x%x, 0x%x, %p)\n", devtoname(dev), flags, mode, (void *)p); + /* + * Initialize label + */ + IFOPT(vn, VN_LABELS) { if (vn->sc_flags & VNF_INITED) { struct disklabel label; @@ -238,8 +243,9 @@ } if (dkslice(dev) != WHOLE_DISK_SLICE || dkpart(dev) != RAW_PART || - mode != S_IFCHR) + mode != S_IFCHR) { return (ENXIO); + } } return(0); } @@ -500,7 +506,15 @@ VOP_UNLOCK(nd.ni_vp, 0, p); vn->sc_secsize = DEV_BSIZE; vn->sc_vp = nd.ni_vp; - vn->sc_size = vattr.va_size / vn->sc_secsize; /* note truncation */ + + /* + * If the size is specified, override the file attributes. Note that + * the vn_size argument is in PAGE_SIZE sized blocks. + */ + if (vio->vn_size) + vn->sc_size = (quad_t)vio->vn_size * PAGE_SIZE / vn->sc_secsize; + else + vn->sc_size = vattr.va_size / vn->sc_secsize; error = vnsetcred(vn, p->p_ucred); if (error) { (void) vn_close(nd.ni_vp, FREAD|FWRITE, p->p_ucred, p); Index: usr.sbin/vnconfig/vnconfig.8 =================================================================== RCS file: /home/ncvs/src/usr.sbin/vnconfig/vnconfig.8,v retrieving revision 1.8 diff -u -r1.8 vnconfig.8 --- vnconfig.8 1999/07/12 20:12:29 1.8 +++ vnconfig.8 1999/08/25 02:52:49 @@ -133,7 +133,18 @@ If no regular file is specified, VN will use swap for backing store. This option specifies the size of the device. For example, '23m' for 23 megabytes. The VN device will round the size up to a machine page boundry. -Filesystems up to 7.9 terrabytes are supported. +Filesystems up to 7.9 terrabytes are supported. When specified along with +a regular file, this option overrides the regular file's size insofar as +VN is concerned. +.It Fl T +When a regular file is specified, VN will ftruncate() the file to 0 first. +Normally you should also specify the -S option to set the size of the file. +This option also creates the file if it did not previously exist. +This option is only meaningful if the -S option has been specified. +.It Fl Z +When a regular file is specified, VN will zero the contents of the file to +ensure that all blocks have been allocated by the filesystem. This option is +only meaningful if the -S option has been specified. .It Fl u Disable and ``unconfigure'' the device. .It Fl v Index: usr.sbin/vnconfig/vnconfig.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/vnconfig/vnconfig.c,v retrieving revision 1.10 diff -u -r1.10 vnconfig.c --- vnconfig.c 1999/05/16 08:09:23 1.10 +++ vnconfig.c 1999/08/25 02:51:51 @@ -50,6 +50,7 @@ #include #include #include +#include #include #include #include @@ -62,6 +63,7 @@ #define MAXVNDISK 16 #define LINESIZE 1024 +#define ZBUFSIZE 32768 struct vndisk { char *dev; @@ -82,6 +84,8 @@ #define VN_IGNORE 0x80 #define VN_SET 0x100 #define VN_RESET 0x200 +#define VN_TRUNCATE 0x400 +#define VN_ZERO 0x800 int nvndisks; @@ -111,7 +115,7 @@ char *autolabel = NULL; configfile = _PATH_VNTAB; - while ((i = getopt(argc, argv, "acdef:gr:s:S:L:uv")) != -1) + while ((i = getopt(argc, argv, "acdef:gr:s:S:TZL:uv")) != -1) switch (i) { /* all -- use config file */ @@ -176,6 +180,14 @@ size = getsize(optarg); break; + case 'T': + flags |= VN_TRUNCATE; + break; + + case 'Z': + flags |= VN_ZERO; + break; + case 'L': autolabel = optarg; break; @@ -190,13 +202,13 @@ if (flags == 0) flags = VN_CONFIG; - if (all) + if (all) { readconfig(flags); - else { + } else { if (argc < optind + 1) usage(); vndisks[0].dev = argv[optind++]; - vndisks[0].file = argv[optind++]; + vndisks[0].file = argv[optind++]; /* may be NULL */ vndisks[0].flags = flags; vndisks[0].size = size; vndisks[0].autolabel = autolabel; @@ -235,6 +247,7 @@ char *rdev; FILE *f; u_long l; + int pgsize = getpagesize(); dev = vnp->dev; file = vnp->file; @@ -243,6 +256,47 @@ if (flags & VN_IGNORE) return(0); + + /* + * When a regular file has been specified, do any requested setup + * of the file. Truncation (also creates the file if necessary), + * sizing, and zeroing. + */ + + if (file && vnp->size != 0 && (flags & VN_CONFIG)) { + int fd; + struct stat st; + + if (flags & VN_TRUNCATE) + fd = open(file, O_RDWR|O_CREAT|O_TRUNC); + else + fd = open(file, O_RDWR); + if (fd >= 0 && fstat(fd, &st) == 0 && S_ISREG(st.st_mode)) { + if (st.st_size < (off_t)vnp->size * pgsize) + ftruncate(fd, (off_t)vnp->size * pgsize); + if (vnp->size != 0) + st.st_size = (off_t)vnp->size * pgsize; + + if (flags & VN_ZERO) { + char *buf = malloc(ZBUFSIZE); + bzero(buf, ZBUFSIZE); + while (st.st_size > 0) { + int n = (st.st_size > ZBUFSIZE) ? + ZBUFSIZE : (int)st.st_size; + if (write(fd, buf, n) != n) { + ftruncate(fd, 0); + printf("Unable to ZERO file %s\n", file); + return(0); + } + st.st_size -= (off_t)n; + } + } + close(fd); + } else { + printf("Unable to open file %s\n", file); + return(0); + } + } rdev = rawdevice(dev); f = fopen(rdev, "rw"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 20:35:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from newton.math.uic.edu (newton.math.uic.edu [131.193.178.229]) by hub.freebsd.org (Postfix) with SMTP id F41D6152A6 for ; Tue, 24 Aug 1999 20:35:16 -0700 (PDT) (envelope-from vladimir@math.uic.edu) Received: (qmail 10808 invoked from network); 25 Aug 1999 03:35:13 -0000 Received: from galois.math.uic.edu (HELO math.uic.edu) (131.193.178.114) by newton.math.uic.edu with SMTP; 25 Aug 1999 03:35:13 -0000 Received: (qmail 26003 invoked by uid 31415); 25 Aug 1999 03:35:10 -0000 Date: 25 Aug 1999 03:35:10 -0000 Message-ID: <19990825033510.26002.qmail@math.uic.edu> From: vladimir@math.uic.edu To: bright@rush.net Subject: Re: NFSv3 on freebsd<-->solaris Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From bright@rush.net Wed Aug 25 01:11:10 1999 >Delivered-To: vladimir@mailhost2.math.uic.edu >Delivered-To: vladimir@math.uic.edu >Date: Tue, 24 Aug 1999 21:21:27 -0400 (EDT) >From: Alfred Perlstein >To: vladimir@math.uic.edu >cc: freebsd-current@FreeBSD.ORG >Subject: Re: NFSv3 on freebsd<-->solaris >MIME-Version: 1.0 > >On 24 Aug 1999 vladimir@math.uic.edu wrote: > >> Following advice from Cejka Rudolf , I have edited >> /src/sys/nfs/nfs_syscalls.c (commented out the lines after the "Solaris 2.5" >> comment). The "File exists" errors went away, everything seemed normal, >> but then I ran into another problem. mailx on solaris >> client could not lock the mailbox file anymore. The snoop output is >> below (I am not an NFS guru, but hope it will be useful to somebody). >> Here galileo is the FBSD server, galois is a Solaris 7 NFS client. >> Why would solaris machine make a request with vers=4: >> galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP >> ? >> (am I right that vers here is the same as the NFS version)? > >The NLM version 4 protocol is not supported, I am working on this. > >Question: did you delete both checks after the Solaris 2.5 mention? >or just one? which one? > >-Alfred > > Ah, so vers=4 has nothing to do with NFS's vers 3. I have deleted both checks. Please let me know if you need more info or testing done. Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 21: 0:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id A97EA14FF5 for ; Tue, 24 Aug 1999 21:00:20 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn34.imasy.or.jp [202.227.24.226]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id MAA04574; Wed, 25 Aug 1999 12:58:43 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908250358.MAA04574@tasogare.imasy.or.jp> To: mmuir@es.co.nz Cc: freebsd-current@freebsd.org Subject: Re: followup to apm problems. In-Reply-To: Your message of "Tue, 24 Aug 1999 12:39:25 +1200" <37C1E9BD.F3584C38@es.co.nz> References: <37C1E9BD.F3584C38@es.co.nz> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 25 Aug 1999 13:02:07 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 52 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to have full output of dmesg to investigate hardware interference in apm. Could you send me it later? > 'apm -Z' for standby jumps into standby mode for like.. an instant, then > comes right back out (while playing mp3) [snip] > 'zzz' or 'apm -z' for suspend jumps into suspend mode, and just the same > way, comes right back out (while playing mp3s again) > it should be noted that the cpu fan does turn off momentarily for both > of these events, and the mp3 that is playing stops, then starts up again > where it left off. > Even without playing anything through the sound device, it does the same > thing. I have more questions and requests :) When did this problem appear? Have you put your PC in suspend/standby state successfully before? Did you try it on other OS? (Win, Linux, etc.) How about executing zzz on console (non X)? Is cli-hack helpful in your case? http://www.freebsd.org/cgi/getmsg.cgi?fetch=56429+60225+/usr/local/www/db/text/1999/freebsd-current/19990815.freebsd-current+raw Message-Id: <199908091431.XAA01774@tasogare.imasy.or.jp> Could you try following script and send me the output? ---- #!/bin/sh iostat -c 3 echo SUSPENDING zzz echo RESUMING iostat -c 3 --- > If i leave the thing on with no activity, while running apmd, it goes > into suspend or standby (depending on the timers set in the bios) every > now and again, but jumps back out as soon as it does. > Also, all the PM timer interrupts are disabled. > > Motherboard is an Abit BH-6 I'm not familiar with Abit BH-6... Could you tell me current configuration of PM related BIOS setting (and BIOS version if you know)? Sorry for too many questions and my poor english :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 21:31:23 1999 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 F0A311504A; Tue, 24 Aug 1999 21:31:19 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA41950; Tue, 24 Aug 1999 21:29:50 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908250429.VAA41950@gndrsh.dnsmgr.net> Subject: Re: Softupdates reliability? In-Reply-To: from "Brian F. Feldman" at "Aug 24, 1999 05:39:56 pm" To: green@FreeBSD.ORG (Brian F. Feldman) Date: Tue, 24 Aug 1999 21:29:50 -0700 (PDT) Cc: richard@cogsci.ed.ac.uk (Richard Tobin), syssgm@detir.qld.gov.au (Stephen McKay), jeremyp@gsmx07.alcatel.com.au (Peter Jeremy), 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 > On Tue, 24 Aug 1999, Richard Tobin wrote: > > > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > > > > You have one of the first K6-2s off the line. There were definite problems > > > with these, and as such, they were specially distinguished by having 66 > > > printed on top. > > > > I have a 0x580 which has had no problems at all. I'm pretty certain > > it doesn't have 66 stamped on it. Are they all supposed to have this, > > or were they tested and the dodgy ones stamped 66? > > It must be the latter. My 0x580 had the 66, so it must be that the dodgy > ones got labelled 66 and not all the 0x580s were defective. The original K6-2's off the line where all 100MHz parts, it was later when AMD found that some people where sticking these in 66MHz boards and trying to run them with a 66MHz FSB and having troubles that AMD started to test the parts for 66MHz operation, they had to make some changes in the I/O buffers and then qualify a new part number and those are the ones stamped 66. Aka AMD 6K86-2-P300/66 vs AMD 6K86-2-P300/100 for those who know what a real AMD part number is. To the best of my knowledge no 0x580 stepping 0 chip is qualified by AMD to run with a 66MHz FSB. -- Rod Grimes - KD7CAX - (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 Tue Aug 24 21:44: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id EDC981594F for ; Tue, 24 Aug 1999 21:43:53 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id AAA01488; Wed, 25 Aug 1999 00:53:21 -0400 (EDT) Date: Wed, 25 Aug 1999 00:53:19 -0400 (EDT) From: Alfred Perlstein To: vladimir@math.uic.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFSv3 on freebsd<-->solaris In-Reply-To: <19990825033510.26002.qmail@math.uic.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Aug 1999 vladimir@math.uic.edu wrote: > >> Why would solaris machine make a request with vers=4: > >> galois.math.uic.edu -> galileo.math.uic.edu PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP > >> ? > >> (am I right that vers here is the same as the NFS version)? > > > >The NLM version 4 protocol is not supported, I am working on this. > > > >Question: did you delete both checks after the Solaris 2.5 mention? > >or just one? which one? > > > >-Alfred > > > > > > Ah, so vers=4 has nothing to do with NFS's vers 3. From reading the Open Group's XNFS book, NFSv3 clients use the NLM version 4 protocol to gain locks, FreeBSD's rpc.lockd doesn't have stub functions for NLMv4 locking _yet_ :) > > I have deleted both checks. > Interesting... > Please let me know if you need more info or testing done. Soon enough. :) thank you, -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 24 22:21:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id BC16715842 for ; Tue, 24 Aug 1999 22:21:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00766; Tue, 24 Aug 1999 22:15:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908250515.WAA00766@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: current@freebsd.org Subject: Re: Monday part II: The Terror Continues In-reply-to: Your message of "Tue, 24 Aug 1999 14:26:27 EDT." <199908241826.OAA08431@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Aug 1999 22:15:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is the third unusable snap in a row that I've had the misfortune > to encounter. I'm starting to think this is more than a coincidence. Did > somebody launch a "Piss Bill Off" contest when I wasn't looking or > something? If so, let me stress that you really don't want to find out > what first prize is. This is -current you're talking about. I'd recommend just backing off a little, or don't you even care to think how good you've had it lately? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Aug 24 23:20:36 1999 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 9F184154C0 for ; Tue, 24 Aug 1999 23:20:33 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id BAA10920 for current@freebsd.org; Wed, 25 Aug 1999 01:20:32 -0500 (CDT) Date: Wed, 25 Aug 1999 01:20:32 -0500 From: "Matthew D. Fuller" To: current@freebsd.org Subject: Unhappy recent -CURRENT's (was Re: Monday strikes again) Message-ID: <19990825012032.A10701@futuresouth.com> References: <199908231835.OAA06292@skynet.ctr.columbia.edu> <19990824155215.J28846@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990824155215.J28846@futuresouth.com>; from Matthew D. Fuller on Tue, Aug 24, 1999 at 03:52:15PM -0500 X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 24, 1999 at 03:52:15PM -0500, a little birdie told me that Matthew D. Fuller remarked > > Here is some info from the panic I got mid-late April. I'll try > cvsup'ing and building a new kernel tonite and see if it's fixed, but in > case it isn't here's some info. Update: -CURRENT now boots just fine, no problems, except the minor detail that it fails utterly to detect my PCI bus. Which, needless to say, is a bit of an inconvenience, since my ethernet card is on PCI. This is a Compaq Presario 575, Pentium 120 processor with 80 megs of RAM. Ethernet card is a 3c905. Everything else seems to work just fine (w/ and w/o PnP included in kernel config, tho I don't think it affects any hardware I have). Verbose boot messages available if someone has time to take a look. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "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 Aug 24 23:28: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9657C14C81 for ; Tue, 24 Aug 1999 23:28:01 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id XAA83473 for ; Tue, 24 Aug 1999 23:27:44 -0700 (PDT) Date: Tue, 24 Aug 1999 23:27:54 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: Alpha/PC98/ i4b patches 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 been moving devfs forward to match PHK's latest changes, however there are some files I cannot test. These effect the ISDN stack, the alpha port and the PC98 code. If you can test these, apply the patch file found at http://www.freebsd.org/~julian/ and let me know if it breaks anything. If you don't compile DEVFS you shouldn't see any changes. if you do you should see devices as per normal in a devfs. I'm more interested in just checking that they don't break the NON_devfs case at the moment. but I can't test those 3 cases. Could anyone who can test those parts let me know if they are safe, so I can check them in? Until I can check them (and a couple of others) in, I can't make some API changes to DEVFS that make it less intrusive. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 0: 7:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 6657715260 for ; Wed, 25 Aug 1999 00:07:18 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id RAA26818; Wed, 25 Aug 1999 17:04:10 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xmab26778; Wed, 25 Aug 99 17:03:51 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id QAA19178; Wed, 25 Aug 1999 16:47:46 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id QAA19862; Wed, 25 Aug 1999 16:05:55 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id QAA13045; Wed, 25 Aug 1999 16:05:53 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908250605.QAA13045@nymph.detir.qld.gov.au> To: Wilko Bulte Cc: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy), freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Softupdates reliability? References: <199908232243.AAA55756@yedi.iaf.nl> In-Reply-To: <199908232243.AAA55756@yedi.iaf.nl> from Wilko Bulte at "Tue, 24 Aug 1999 00:43:00 +0200" Date: Wed, 25 Aug 1999 16:05:53 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 24th August 1999, Wilko Bulte wrote: >Hmm. I would generally expect SCSI errors etc to occur. Assuming the driver >reports those one would at least know the bus was whacko. I saw no errors, but that's not entirely surprising since I was running X11 and by that time xconsole was probably swapped out, and the disk system was stuck, so it wouldn't have been able to report anything. I gave up on a serial console a very long time ago because this machine is so reliable. :-) Also, I recall (rumour?) that the ncr driver is not as robust in the face of errors as the adaptec driver, at least with CAM. Anybody know the facts? I know, for example, that I can't get bad block lists using my scsi adapter, but people using adaptecs can. That shows that the ncr driver is in some sense incomplete. I've been meaning to look into that, but you know how time gets away. So, after all this, I still don't know if I have any real evidence of anything at all. I'll just have to keep at it until it happens again. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 0:29: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 71B60159AB; Wed, 25 Aug 1999 00:23:47 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-29.iptelecom.net.ua [212.42.74.29]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA09065; Wed, 25 Aug 1999 10:24:15 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id KAA19732; Wed, 25 Aug 1999 10:23:41 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37C399F7.E5ED74D0@altavista.net> Date: Wed, 25 Aug 1999 10:23:36 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Richard Tobin Cc: "Brian F. Feldman" , Stephen McKay , Peter Jeremy , freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? References: <550.199908242209@doyle.cogsci.ed.ac.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Tobin wrote: > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > > You have one of the first K6-2s off the line. There were definite problems > > with these, and as such, they were specially distinguished by having 66 > > printed on top. > > I have a 0x580 which has had no problems at all. I'm pretty certain > it doesn't have 66 stamped on it. Are they all supposed to have this, > or were they tested and the dodgy ones stamped 66? I'm also have 0x580 without 66 stamped and it runs at 100MHz without any remarkable problems. -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 0:42:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CC6FB153F0 for ; Wed, 25 Aug 1999 00:42:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 IAA10533; Wed, 25 Aug 1999 08:52:40 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 25 Aug 1999 08:52:40 +0100 (BST) From: Doug Rabson To: Matthew Dillon Cc: "David O'Brien" , current@freebsd.org, vladimir@math.uic.edu Subject: Re: NFSv3 on freebsd<-->solaris In-Reply-To: <199908240344.UAA12309@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 Mon, 23 Aug 1999, Matthew Dillon wrote: > :... > :am not implying that the problem might be on the FreeBSD side, it might > :as well be a bug in solaris NFS implementation). > : > :I would greatly appreciate any help with the following problem. I have > :a FreeBSD NFS server (3.2-STABLE, built on Aug 3), and a Solaris 2.7 > :client. I run into problems when trying to use NFSv3 mounts on the > :client. Trying to remove files from the mounted partition (on the nfs > :client) results in multiple errors, for example: > : > : # rm -r /home/2/vladimir > : rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists > : rm: Unable to remove directory /home/2/vladimir/CVS/blowup: File exists > : rm: Unable to remove directory /home/2/vladimir/CVS/useradd: File exists > : > :I have tried using tcp and udp mount options with the same result. NFSv2 > :works fine. > : > :Solaris client has the latest patches applied. I would very much appreciate > :any comments on that. > > When you look at those directories on the server from the server are there any > files left over? > > If so then the rm -r is somehow missing some files and then is unable to > rmdir the directory because it isn't yet empty. This is probably because our server detects that the directory has been modified and rejects the solaris client's directory cookies. Instead of recovering, the solaris client barfs. Its a solaris bug really but perhaps we can add a knob to relax our directory modified checks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 2:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C2994152B7; Wed, 25 Aug 1999 02:56:41 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA26522; Wed, 25 Aug 1999 11:36:17 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA77550; Wed, 25 Aug 1999 11:23:41 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908250923.LAA77550@yedi.iaf.nl> Subject: Re: Softupdates reliability? In-Reply-To: <199908250429.VAA41950@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Aug 24, 1999 9:29:50 pm" To: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes) Date: Wed, 25 Aug 1999 11:23:41 +0200 (CEST) Cc: green@FreeBSD.ORG, richard@cogsci.ed.ac.uk, syssgm@detir.qld.gov.au, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Rodney W. Grimes wrote ... > > On Tue, 24 Aug 1999, Richard Tobin wrote: > > > > > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > The original K6-2's off the line where all 100MHz parts, it was later when > AMD found that some people where sticking these in 66MHz boards and trying > to run them with a 66MHz FSB and having troubles that AMD started to test > the parts for 66MHz operation, they had to make some changes in the I/O > buffers and then qualify a new part number and those are the ones stamped 66. > Aka AMD 6K86-2-P300/66 vs AMD 6K86-2-P300/100 for those who know what a > real AMD part number is. Rod, Do I understand you correctly that I should get a 66Mc variant for my Asus T2P4 because a 100Mc is unlikely to work? Or are the newer 100Mc chips also coping OK with 66Mc FSB? (I'm aware of the slight hardware hack required to make a T2P4 accept a K6-2. What would be the fastest K6-2 running ok with a 66 FSB? And is this potential upgrade worthwhile, with K6-2 going here for around 80-90$ or so?) Thanks, Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Aug 25 3:26:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 4000F1532E; Wed, 25 Aug 1999 03:26:40 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id DAA70040; Wed, 25 Aug 1999 03:23:28 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908251023.DAA70040@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte Cc: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes), green@FreeBSD.ORG, richard@cogsci.ed.ac.uk, syssgm@detir.qld.gov.au, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-reply-to: Your message of "Wed, 25 Aug 1999 11:23:41 +0200." <199908250923.LAA77550@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Aug 1999 03:23:28 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PIII 450Mhz are going for about $175 see http://www.pricewatch.com . Heck , at that price get two 8) Enjoy -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 4:52:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 616851526B for ; Wed, 25 Aug 1999 04:52:38 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id VAA21274; Wed, 25 Aug 1999 21:49:29 +1000 (EST) To: Peter Jeremy Cc: nate@mt.sri.com, freebsd-current@freebsd.org Subject: Re: SIO "lost interrupt" status in current? In-reply-to: Your message of "Wed, 25 Aug 1999 10:45:59 +1000." <99Aug25.104500est.40348@border.alcanet.com.au> Date: Wed, 25 Aug 1999 21:49:29 +1000 Message-ID: <10005.935581769@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wasn't using the DMA, 32-bit, multi-block-16 flags on wdc. Added that. still got the drops.. I removed the ed0 ISA card from the kernel, seemed to reduce freq. still dropped. I then tried harder to look for a correlation. doing virtual desktop pans caused every drop every time. small incremental moves fine, but a complete X11 redraw triggers things. I'd say I have the X11 bug. If I can do any useful debug (since I can re-create this) let me know. If this is a dead horse, I can live with it. cheers and thanks for advice! -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 7:46:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id E241215356 for ; Wed, 25 Aug 1999 07:46:47 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA20493 for ; Wed, 25 Aug 1999 10:46:43 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18707; Wed, 25 Aug 1999 10:46:13 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA31803 for freebsd-current@freebsd.org; Wed, 25 Aug 1999 10:46:12 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908251446.KAA31803@bb01f39.unx.sas.com> Subject: make release and DOC failures (diskless doc) To: freebsd-current@freebsd.org Date: Wed, 25 Aug 1999 10:46:12 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, the following has been happenning for some time now... is anyone else seeing this, or is it time to turn of doc again? Thanks, John cd /usr/doc/en_US.ISO_8859-1 ; make afterdistribute DESTDIR=/R/stage/trees/bin ===> en_US.ISO_8859-1/articles cd /usr/doc/en_US.ISO_8859-1/articles ; make afterdistribute DESTDIR=/R/stage/trees/bin ===> en_US.ISO_8859-1/articles/diskless-x make: don't know how to make distribute. Stop *** Error code 2 Stop in /usr/doc/en_US.ISO_8859-1/articles. *** Error code 1 Stop in /usr/doc/en_US.ISO_8859-1. *** Error code 1 Stop in /usr/doc. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 8:13:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E20E14C35 for ; Wed, 25 Aug 1999 08:13:44 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA10546; Wed, 25 Aug 1999 08:10:35 -0700 (PDT) (envelope-from dillon) Date: Wed, 25 Aug 1999 08:10:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199908251510.IAA10546@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: New combo patch avail Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A new combo patch is now avaiable: http://www.backplane.com/FreeBSD4/ first section, multipatch-2.diff hotlink. The fixes are too numerous to mention. Portions of the patch may be committed by Alan or dg at any time so anyone who uses the above should beware. Also included is other work discussed by Alan, DG, and I, not classified as a 'bug fix', such as the removal of vnode->v_lastr. This patch should be considered experimental, mainly due to the BOOTP related patches which mess around with the rootfsid. There may be slight (temporary) degredation in I/O performance due to lack of tuning of the new sequential detection code. The patch includes everything not committed to date including bug fixes to NFS, VN, CCD, BOOTP, mmap/dirty lockups, and so on. Performance improvements to NFS, mmap (faults), and certain filesystem I/O ops have also been made. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 8:25:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from grisu.bik-gmbh.de (grisu.bik-gmbh.de [194.233.237.82]) by hub.freebsd.org (Postfix) with ESMTP id 27A1C15322; Wed, 25 Aug 1999 08:25:37 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by grisu.bik-gmbh.de (8.8.8/8.6.9) with ESMTP id RAA10244; Wed, 25 Aug 1999 17:22:15 +0200 (MEST) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id RAA67578; Wed, 25 Aug 1999 17:21:49 +0200 (MET DST) Date: Wed, 25 Aug 1999 17:21:49 +0200 From: Martin Cracauer To: Daniel Eischen Cc: obrien@FreeBSD.ORG, tich@ma.ikos.com, current@FreeBSD.ORG, tich@par28.ma.ikos.com Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT Message-ID: <19990825172149.A66149@cons.org> References: <199908230046.UAA23102@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908230046.UAA23102@pcnet1.pcnet.com>; from Daniel Eischen on Sun, Aug 22, 1999 at 08:46:42PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199908230046.UAA23102@pcnet1.pcnet.com>, Daniel Eischen wrote: > Richard Cownie wrote: > > On Sat, 21 Aug 1999, David O'Brien wrote: > > > Are you saying 4.17 is better than 4.18 for debugging C++? Or are you > > > saying you didn't know FreeBSD comes with gdb: > > > > gdb-4.18 is badly broken on all platforms (at least for C++). You can't > > call methods from the gdb command line, and also it frequently freezes > > to the point where you have to kill the window. gdb-4.17 is much better > > for C++. > > There's a port for gdb-4.17 sitting on my ftp site at: > > ftp://ftp.pcnet.com/users/eischen/FreeBSD/gdb-4.17-port.tar.gz > > The port includes changes made to the gdb in our base system > (then, Mar 1999, it was gdb-4.15 I believe). I haven't made > any further updates to it since. You're welcome to play around > with it. Did anyone of you took care that you can build an aout gdb on an ELF FreeBSD system? I don't mean a gdb that is aout, but one that can debug aout binaries. That would be most useful to have as a port. Just step to `/usr/ports/devel/aout-gdb && make install` and it uses /usr/src/gnu/usr.bin/gdb or fetches some other source by itself if it can't use native sources. The modula-3 port does something in that line, uses /usr/src if it can. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 8:39: 8 1999 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 721ED14C02; Wed, 25 Aug 1999 08:39:02 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA04490; Wed, 25 Aug 1999 11:38:00 -0400 (EDT) Date: Wed, 25 Aug 1999 11:38:00 -0400 (EDT) From: Daniel Eischen Message-Id: <199908251538.LAA04490@pcnet1.pcnet.com> To: cracauer@cons.org, eischen@vigrid.com Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG, tich@ma.ikos.com, tich@par28.ma.ikos.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Did anyone of you took care that you can build an aout gdb on an ELF > FreeBSD system? > > I don't mean a gdb that is aout, but one that can debug aout binaries. I thought the gdb in our base system could debug aout binaries. Or am I sadly mistaken. > That would be most useful to have as a port. Just step to > `/usr/ports/devel/aout-gdb && make install` and it uses > /usr/src/gnu/usr.bin/gdb or fetches some other source by itself if it > can't use native sources. The modula-3 port does something in that > line, uses /usr/src if it can. I haven't tested the port on aout. The main reason I did the port was to make an Ada-aware version of gdb. The GNAT maintainers release patches to a specific version of gdb (in this case gdb-4.17), so basing a port of gdb on what's in our base system was a bad idea. The gdb port I mentioned wasn't the Ada-aware gdb port, it was just a step to get there. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 8:44:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id DD49715211; Wed, 25 Aug 1999 08:44:35 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id RAA10265; Wed, 25 Aug 1999 17:43:36 +0200 (CEST) Date: Wed, 25 Aug 1999 17:43:36 +0200 From: Martin Cracauer To: Daniel Eischen Cc: cracauer@cons.org, current@FreeBSD.ORG, obrien@FreeBSD.ORG, tich@ma.ikos.com, tich@par28.ma.ikos.com Subject: Re: gdb-4.17 in FreeBSD 4.0-CURRENT Message-ID: <19990825174336.A10236@cons.org> References: <199908251538.LAA04490@pcnet1.pcnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199908251538.LAA04490@pcnet1.pcnet.com>; from Daniel Eischen on Wed, Aug 25, 1999 at 11:38:00AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199908251538.LAA04490@pcnet1.pcnet.com>, Daniel Eischen wrote: > > Did anyone of you took care that you can build an aout gdb on an ELF > > FreeBSD system? > > > > I don't mean a gdb that is aout, but one that can debug aout binaries. > > I thought the gdb in our base system could debug aout binaries. Or > am I sadly mistaken. You can compile it so that the gdb binary is aout (`cd /usr/src/gnu/usr.bin/binutils && make OBJFORMAT=aout), but that's still a debugger that debugs ELF binaries. It can't handle aout binaries unless you explicitly configure it to do so and this ability seems to be broken by the FreeBSD-specific changes. > > That would be most useful to have as a port. Just step to > > `/usr/ports/devel/aout-gdb && make install` and it uses > > /usr/src/gnu/usr.bin/gdb or fetches some other source by itself if it > > can't use native sources. The modula-3 port does something in that > > line, uses /usr/src if it can. > > I haven't tested the port on aout. The main reason I did the port > was to make an Ada-aware version of gdb. The GNAT maintainers > release patches to a specific version of gdb (in this case gdb-4.17), > so basing a port of gdb on what's in our base system was a bad > idea. The gdb port I mentioned wasn't the Ada-aware gdb port, it > was just a step to get there. Well, on second thinking the idea to build from /usr/src might not save much. You need the binutils libraries and friends as aout, so it might be easier to start from a source that carries everything you need with it and link it statically. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 9:29:44 1999 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 8065D15AEB; Wed, 25 Aug 1999 09:29:03 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id JAA43994; Wed, 25 Aug 1999 09:28:15 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908251628.JAA43994@gndrsh.dnsmgr.net> Subject: Re: Softupdates reliability? In-Reply-To: <199908250923.LAA77550@yedi.iaf.nl> from Wilko Bulte at "Aug 25, 1999 11:23:41 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 25 Aug 1999 09:28:15 -0700 (PDT) Cc: green@FreeBSD.ORG, richard@cogsci.ed.ac.uk, syssgm@detir.qld.gov.au, jeremyp@gsmx07.alcatel.com.au, 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 > As Rodney W. Grimes wrote ... > > > On Tue, 24 Aug 1999, Richard Tobin wrote: > > > > > > > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > > The original K6-2's off the line where all 100MHz parts, it was later when > > AMD found that some people where sticking these in 66MHz boards and trying > > to run them with a 66MHz FSB and having troubles that AMD started to test > > the parts for 66MHz operation, they had to make some changes in the I/O > > buffers and then qualify a new part number and those are the ones stamped 66. > > Aka AMD 6K86-2-P300/66 vs AMD 6K86-2-P300/100 for those who know what a > > real AMD part number is. > > Rod, > > Do I understand you correctly that I should get a 66Mc variant for my Asus > T2P4 because a 100Mc is unlikely to work? Or are the newer 100Mc chips also > coping OK with 66Mc FSB? Yes, you stand a far better chance of making this hack work with a 66MHz part. No the newer std parts are not designed to run with a 66MHz FSB, you should always order them as /66. Note that AMD has stopped making these chips due to low demand for them (with 100MHz boards <$80 USA the price/performance is usually worth it for most folks.) > (I'm aware of the slight hardware hack required to make a T2P4 accept a K6-2. > What would be the fastest K6-2 running ok with a 66 FSB? And is this > potential upgrade worthwhile, with K6-2 going here for around 80-90$ or so?) I've got about 8 of the T2P4's here and I'm not going to bother with it, they are all getting replaced with 100MHz boards... and 450MHz chips that have now fallen to <$82 US. And I pick up 1MB L2 cache while I'm at it :-) -- Rod Grimes - KD7CAX - (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 Wed Aug 25 9:31: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id D1EBB14C37 for ; Wed, 25 Aug 1999 09:30:54 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id MAA25351; Wed, 25 Aug 1999 12:28:24 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199908251510.IAA10546@apollo.backplane.com> Date: Wed, 25 Aug 1999 12:33:22 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: Matthew Dillon Subject: RE: New combo patch avail Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I am currently experimenting with BOOTP in -current, I patched ONLY vfs_conf.c and vfs_subr.c with your rootfsid changes. Works fine in a BOOTP configuration. -current sources are as of last night. I can now boot a -current system from only a floppy disk with a (kgzipped) kernel on it! (plus some patches (see below) to rc.diskless1 where it (bogusly) temporarily mounts /usr, since it is already there (it should check for "-d /usr/bin" first), and rc.diskless2 to mfs a /var/msgs dir) -Mark Taylor Index: rc.diskless1 =================================================================== RCS file: /FreeBSD/CVS/src/etc/rc.diskless1,v retrieving revision 1.1 diff -c -2 -r1.1 rc.diskless1 *** rc.diskless1 1999/02/09 17:17:18 1.1 --- rc.diskless1 1999/08/25 16:24:32 *************** *** 48,57 **** # retargeted /etc/fstab. See instructions in /usr/share/examples/diskless. # - set `/bin/df /` - nfs_root=$8 - mount_nfs -o ro ${nfs_root}/usr /usr ! chkerr $? "mount of /usr" # Figure out our interface and IP. # --- 48,61 ---- # retargeted /etc/fstab. See instructions in /usr/share/examples/diskless. # ! nfs_root="" ! if [ ! -d /usr/bin ]; then ! set `/bin/df /` ! nfs_root=$8 ! mount_nfs -o ro ${nfs_root}/usr /usr + chkerr $? "mount of /usr" + fi + # Figure out our interface and IP. # *************** *** 62,66 **** echo "Interface $bootp_ifc IP-Address $bootp_ipa" ! umount /usr # retarget /conf/ME --- 66,72 ---- echo "Interface $bootp_ifc IP-Address $bootp_ipa" ! if [ ! -z $nfs_root ]; then ! umount /usr ! fi # retarget /conf/ME Index: rc.diskless2 =================================================================== RCS file: /FreeBSD/CVS/src/etc/rc.diskless2,v retrieving revision 1.2 diff -c -2 -r1.2 rc.diskless2 *** rc.diskless2 1999/02/10 18:08:16 1.2 --- rc.diskless2 1999/08/25 16:26:56 *************** *** 14,17 **** --- 14,18 ---- mount_mfs -s ${var_tmp_sectors:=65536} -T qp120at dummy /var/tmp mount_mfs -s ${var_spool_sectors:=65536} -T qp120at dummy /var/spool + mount_mfs -s ${var_msgs_sectors:=2048} -T qp120at dummy /var/msgs chmod 755 /var/run chmod 755 /var/db On 25-Aug-99 Matthew Dillon wrote: > A new combo patch is now avaiable: > > http://www.backplane.com/FreeBSD4/ > first section, multipatch-2.diff hotlink. > > The fixes are too numerous to mention. Portions of the patch may be > committed by Alan or dg at any time so anyone who uses the above should > beware. Also included is other work discussed by Alan, DG, and I, not > classified as a 'bug fix', such as the removal of vnode->v_lastr. > > This patch should be considered experimental, mainly due to the BOOTP > related patches which mess around with the rootfsid. > > There may be slight (temporary) degredation in I/O performance due > to lack of tuning of the new sequential detection code. > > The patch includes everything not committed to date including bug fixes > to NFS, VN, CCD, BOOTP, mmap/dirty lockups, and so on. Performance > improvements to NFS, mmap (faults), and certain filesystem I/O ops have > also been made. > > -Matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 9:32:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7280F15AD7 for ; Wed, 25 Aug 1999 09:31:27 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA15458; Wed, 25 Aug 1999 09:30:12 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Mon, 23 Aug 1999 08:35:16 PDT." <199908231535.IAA00802@dingo.cdrom.com> Date: Wed, 25 Aug 1999 09:30:12 -0700 Message-ID: <15454.935598612@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But it's not going into the tree, no. I think Kevin's point and the > experiences we had with Hasbro should already have convinced people of > that much. I think people are being almost clinically paranoid here. Hasbro and folks got upset over TRADEMARK infringement, e.g. from using a name they had trademarked. I rather doubt that Warner Bros. have managed to trademark the name "matrix" since it's already a common english word. "Boggle" and "Tetris" don't fall into that category. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 9:33:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 54B83151FD for ; Wed, 25 Aug 1999 09:33:47 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA11149; Wed, 25 Aug 1999 09:33:40 -0700 (PDT) (envelope-from dillon) Date: Wed, 25 Aug 1999 09:33:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199908251633.JAA11149@apollo.backplane.com> To: "Mark J. Taylor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: RE: New combo patch avail References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Since I am currently experimenting with BOOTP in -current, I patched ONLY :vfs_conf.c and vfs_subr.c with your rootfsid changes. Works fine in a BOOTP :configuration. -current sources are as of last night. : :I can now boot a -current system from only a floppy disk with a (kgzipped) kernel :on it! : : :(plus some patches (see below) to rc.diskless1 where it (bogusly) temporarily : mounts /usr, since it is already there (it should check for "-d /usr/bin" first), : and rc.diskless2 to mfs a /var/msgs dir) Yah, there's a lot of bogosity in the rc.diskless stuff -- it kinda got stale and needs a major update. My latest rc.diskless stuff avoids mounting /var R+W, which means all the NFS mounts are RO now except for the swap mount. Hopefully I'll get back to it soon. I'll save your patch. Oh shoot, I just realized I forgot the utility support portions in the multi-patch #2 (e.g. the updated vnconfig utility). Ugh. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 9:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles553.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id D911015316 for ; Wed, 25 Aug 1999 09:40:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA04358; Wed, 25 Aug 1999 09:34:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908251634.JAA04358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Wed, 25 Aug 1999 09:30:12 PDT." <15454.935598612@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Aug 1999 09:34:03 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But it's not going into the tree, no. I think Kevin's point and the > > experiences we had with Hasbro should already have convinced people of > > that much. > > I think people are being almost clinically paranoid here. Hasbro and > folks got upset over TRADEMARK infringement, e.g. from using a name > they had trademarked. I rather doubt that Warner Bros. have managed > to trademark the name "matrix" since it's already a common english > word. "Boggle" and "Tetris" don't fall into that category. The issue with boggle and tetris wasn't the name, it was "look and feel". That's the same issue here; the "matrix" screensaver mimics the "distinctive likeness" of a portion of WB's entertainment product, and being a screensaver (rather than, say, a car component) it's also an "entertainment product". -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Aug 25 9:56:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 831CE1598C for ; Wed, 25 Aug 1999 09:56:40 -0700 (PDT) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id MAA28051 for ; Wed, 25 Aug 1999 12:56:17 -0400 (EDT) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 25 Aug 1999 13:01:14 -0400 (EDT) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: current@freebsd.org Subject: newfs of a ccd failing? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had this problem since at least FreeBSD 3.1-RELEASE (it works in 2.2.7/2.2.8). Same problem in 3.2-RELEASE and -current (as of last night). Can someone reproduce this error? I can't believe that you can't newfs a ccd... did I miss something? spiffy# ./ccdtest.sh [snip] newfs /dev/rccd0c Warning: 16 sector(s) in last cylinder unallocated /dev/rccd0c: 204784 sectors in 50 cylinders of 1 tracks, 4096 sectors 100.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 6272 i/g) super-block backups (for fsck -b #) at: 32, 65568, 131104, 196640 newfs: ioctl (WDINFO): No such process newfs: /dev/rccd0c: can't rewrite disk label I believe that there is a problem in/near ufs/ufs/ufs_disksubr.c where it says that it requires an existing disklabel before it writes a new one. If I change the "#if 1" to an "#if 0" in it, then I don't get this failure. Here's my test script: #!/bin/sh # # ccdtest.sh # # Build a 100 MByte linear ccd from a vnode and newfs it. # set -v set -e ccdconfig -u ccd0 2> /dev/null || true vnconfig -u /dev/vn0 2> /dev/null || true (cd /dev && ./MAKEDEV ccd0 vn0) if [ ! -f /var/tmp/vn0 ]; then dd if=/dev/zero of=/var/tmp/vn0 bs=1024 count=102400 fi vnconfig -e -s labels /dev/vn0 /var/tmp/vn0 disklabel -w -r vn0 auto echo "Make 'c' a 4.2BSD type filesystem. [press Enter now]" read dummy disklabel -e vn0 ccdconfig -c ccd0 0 0 /dev/vn0c newfs /dev/rccd0c ccdconfig -u ccd0 || true vnconfig -u /dev/vn0 || true -Mark Taylor NetMAX Developer mtaylor@cybernet.com http://www.netmax.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 10: 4:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 1DCDE15A02 for ; Wed, 25 Aug 1999 10:04:38 -0700 (PDT) (envelope-from tejblum@arc.hq.cti.ru) Received: from arc.hq.cti.ru (localhost [127.0.0.1]) by arc.hq.cti.ru (8.9.3/8.9.3) with ESMTP id VAA96761; Wed, 25 Aug 1999 21:03:44 +0400 (MSD) (envelope-from tejblum@arc.hq.cti.ru) Message-Id: <199908251703.VAA96761@arc.hq.cti.ru> X-Mailer: exmh version 2.0zeta 7/24/97 To: mtaylor@cybernet.com Cc: current@FreeBSD.ORG Subject: Re: newfs of a ccd failing? In-reply-to: Your message of "Wed, 25 Aug 1999 13:01:14 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Aug 1999 21:03:44 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've had this problem since at least FreeBSD 3.1-RELEASE (it works in > 2.2.7/2.2.8). Same problem in 3.2-RELEASE and -current (as of last night). > > Can someone reproduce this error? I can't believe that you can't newfs > a ccd... did I miss something? I always see the error message last months, but it is harmless in practice - the filesystem is OK, the ccd is ready to use. > newfs: ioctl (WDINFO): No such process > newfs: /dev/rccd0c: can't rewrite disk label Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 10:29: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 32874153E6 for ; Wed, 25 Aug 1999 10:28:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA11414; Wed, 25 Aug 1999 10:28:50 -0700 (PDT) (envelope-from dillon) Date: Wed, 25 Aug 1999 10:28:50 -0700 (PDT) From: Matthew Dillon Message-Id: <199908251728.KAA11414@apollo.backplane.com> To: "Mark J. Taylor" Cc: current@FreeBSD.ORG Subject: Re: newfs of a ccd failing? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've had this problem since at least FreeBSD 3.1-RELEASE (it works in :2.2.7/2.2.8). Same problem in 3.2-RELEASE and -current (as of last night). : :Can someone reproduce this error? I can't believe that you can't newfs :a ccd... did I miss something? :[snip] :newfs /dev/rccd0c :Warning: 16 sector(s) in last cylinder unallocated :/dev/rccd0c: 204784 sectors in 50 cylinders of 1 tracks, 4096 sectors : 100.0MB in 4 cyl groups (16 c/g, 32.00MB/g, 6272 i/g) :super-block backups (for fsck -b #) at: : 32, 65568, 131104, 196640 :newfs: ioctl (WDINFO): No such process :newfs: /dev/rccd0c: can't rewrite disk label You have two problems. First, you are using a VN device for which you have enabled labels. The label is stored in the first few sectors of the VN's device. You have then created a CCD on top of the VN device and tried to create a label in it as well, using 'c' which starts at offset 0. The two label areas overlap. Creating a real label under the ccd device will destroy the VN device's label. Problem #2: the ccd device creates a 'garbage' label. It does not create a real label. newfs tries to rewrite the real label, but since no label exists it gets an error. You can create a real label like this: disklabel ccd0 > /tmp/ccd0.label disklabel -R -r ccd0 /tmp/ccd0.label And then your newfs will not generate any errors. BUT, you've just destroyed the VN label by doing this. Ok, so how to fix? * Create a 'd' partition in the VN device which is offset by 16 sectors. 'disklabel -e vn0' 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 204800 0 unused 0 0 # (Cyl. 0 - 99) d: 204784 16 4.2BSD 0 0 0 # (Cyl. 0*- 99*) * Configure the ccd on top of the vn device's 'd' partition. * Create a real label for the ccd * newfs your filesystem. : :I believe that there is a problem in/near ufs/ufs/ufs_disksubr.c where it :says that it requires an existing disklabel before it writes a new one. :If I change the "#if 1" to an "#if 0" in it, then I don't get this failure. It's probably safer for the system to generate an error if no preexisting label exists. It is fairly easy to create a label. The CCD device is rather archaic and needs to be babied a bit when you use it on top of artificially constructed devices. The real problem is that the CCD device requires a block device with an fstype of '4.2BSD'. If we got rid of that requirement then you could run it on top of a 'raw' VN device (without -s labels). If the ccd device didn't try to fake up its label then newfs would not attempt to rewrite it and thus would not complain. -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 Aug 25 11:20:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 64E9B15848 for ; Wed, 25 Aug 1999 11:20:48 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA29389; Thu, 26 Aug 1999 04:20:44 +1000 Date: Thu, 26 Aug 1999 04:20:44 +1000 From: Bruce Evans Message-Id: <199908251820.EAA29389@godzilla.zeta.org.au> To: mtaylor@cybernet.com, tejblum@arc.hq.cti.ru Subject: Re: newfs of a ccd failing? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've had this problem since at least FreeBSD 3.1-RELEASE (it works in >> 2.2.7/2.2.8). Same problem in 3.2-RELEASE and -current (as of last night). This is because writing of the newfs parameters to the label is broken (not done) for all disk devices in 2.2.x. Now it is only broken for devices that don't support labels properly. >I always see the error message last months, but it is harmless in >practice - the filesystem is OK, the ccd is ready to use. > >> newfs: ioctl (WDINFO): No such process I don't know why the errno is ESRCH. >> newfs: /dev/rccd0c: can't rewrite disk label Its harm is limited to fsck no being able to find backup superblocks automatically if the primary superblock is damaged, and newfs not being able to find some previous fsize and bsize paramters if it is rerun. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 11:51:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2BBDE14C06; Wed, 25 Aug 1999 11:51:15 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA22874; Wed, 25 Aug 1999 20:42:25 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA00709; Wed, 25 Aug 1999 20:08:12 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908251808.UAA00709@yedi.iaf.nl> Subject: Re: Softupdates reliability? In-Reply-To: <199908251628.JAA43994@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Aug 25, 1999 9:28:15 am" To: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes) Date: Wed, 25 Aug 1999 20:08:12 +0200 (CEST) Cc: green@FreeBSD.ORG, richard@cogsci.ed.ac.uk, syssgm@detir.qld.gov.au, jeremyp@gsmx07.alcatel.com.au, freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Rodney W. Grimes wrote ... > > As Rodney W. Grimes wrote ... > > > > On Tue, 24 Aug 1999, Richard Tobin wrote: > > > > > > > > > > > Origin = "AuthenticAMD" Id = 0x580 Stepping=0 > > > > > The original K6-2's off the line where all 100MHz parts, it was later when > > > AMD found that some people where sticking these in 66MHz boards and trying > > > to run them with a 66MHz FSB and having troubles that AMD started to test > > > the parts for 66MHz operation, they had to make some changes in the I/O > > > buffers and then qualify a new part number and those are the ones stamped 66. > > > Aka AMD 6K86-2-P300/66 vs AMD 6K86-2-P300/100 for those who know what a > > > real AMD part number is. > > > > Rod, > > > > Do I understand you correctly that I should get a 66Mc variant for my Asus > > T2P4 because a 100Mc is unlikely to work? Or are the newer 100Mc chips also > > coping OK with 66Mc FSB? > > Yes, you stand a far better chance of making this hack work with a 66MHz > part. No the newer std parts are not designed to run with a 66MHz FSB, > you should always order them as /66. Note that AMD has stopped making > these chips due to low demand for them (with 100MHz boards <$80 USA the > price/performance is usually worth it for most folks.) The USA... your prices tend to be a lot better than ours. I could can the T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs now), get an AGP videocard and can the perfectly fine Millenium II (I need the extra PCI slot quite badly) and buy a new CPU. Oh, and buy an ATX case. In the end that is quite a bit more than $80. Unfortunately. > > (I'm aware of the slight hardware hack required to make a T2P4 accept a K6-2. > > What would be the fastest K6-2 running ok with a 66 FSB? And is this > > potential upgrade worthwhile, with K6-2 going here for around 80-90$ or so?) > > I've got about 8 of the T2P4's here and I'm not going to bother with it, I must say I still like the T2P4 a alot. Works just fine for me. > they are all getting replaced with 100MHz boards... and 450MHz chips > that have now fallen to <$82 US. And I pick up 1MB L2 cache while I'm > at it :-) Yep, there are more goodies included ;) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl 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 Aug 25 11:52:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 6295215A2F; Wed, 25 Aug 1999 11:52:07 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA04562; Wed, 25 Aug 1999 19:37:46 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id MAA05413; Wed, 25 Aug 1999 12:38:19 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 25 Aug 1999 12:38:19 +0100 From: Nik Clayton To: "Jordan K. Hubbard" Cc: Nik Clayton , jack , current@FreeBSD.ORG, asami@freebsd.org, doc@freebsd.org Subject: Re: Docs blows up make release Message-ID: <19990825123819.A2177@kilt.nothing-going-on.org> References: <19990822110511.A89933@kilt.nothing-going-on.org> <3164.935357152@localhost> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=NzB8fVQJ5HfG6fxh X-Mailer: Mutt 0.95.4i In-Reply-To: <3164.935357152@localhost>; from Jordan K. Hubbard on Sun, Aug 22, 1999 at 02:25:52PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii [ I've added Satoshi Asami to the cc: list -- I figure he's almost certainly on -current, but I wanted to make sure he sees this and can add his input as necessary. I've also added -doc, for information. ] On Sun, Aug 22, 1999 at 02:25:52PM -0700, Jordan K. Hubbard wrote: > Nik Clayton wrote: > > For the immediate future, it looks like it will -- it seems as though > > we don't have the man power to make the necessary changes to sysinstall > > to support "installing the docs as packages", so I'm going to fix up > > src/release/Makefile as necessary to cope with the new directory structure. Just an update on that. I've been working on this with Jack O'Neill, and if the reports are favourable I'll have one small patch to src/release/Makefile and one small patch to doc/*/Makefile to go in some time in the next 48 hours or so which should get release builds working. Note that this won't include any fixes to teach sysinstall about the new paths under /usr/share/doc/, although you should have seen a patch I sent you about that by now. > I also should note that there's nothing to preclude supplying the docs > as packages *also*, assuming that they appear in the INDEX and get > built as part of Satoshi's ports build. This assumes that the documentation is also listed in the ports tree. I don't think this is a great idea -- more specifically, I don't think this is a great idea as the primary mechanism for making packages of the documentation. I've got no problems with it being another way to make doc packages. As the comment for ports/japanese/handbook says, "this is pretty useless as a port, but is here so I can build a package -- Satoshi". This makes the ports tree have a dependency on the doc tree. I don't think this dependency should be there. It's bad enough that the src/ tree depends on doc/ (and the reason I want the documentation available as packages is to remove this dependency), having ports depend on the doc tree as well just means that when things go out of sync in doc for a while I get both you and Satoshi complaining at me, instead of just you :-) Putting the package building rules in the doc/ Makefiles also (and this is just my personal opinion) makes it easier for people to see how the documentation packages are built. The ports Makefile structure is a marvel, but it contains a lot of code that's not necessary for building documentation packages (the "automagically add man pages to the PLIST i" code, for example) that makes it more difficult for the interested learner to browse and understand what's going on. I've attached the patch to docproj.docbook.mk that tells it how to build packages to this message. To use it. 1. Checkout a recent copy of the doc/ repository. 2. Patch doc/share/mk/docproj.docbook.mk with the attached patch. 3. Pick a directory, such as the English FAQ # cd doc/en_US.ISO_8859-1/books/faq 4. Make sure that a COMMENT and DESCR file exist. I haven't committed any of these yet, so the simplest thing to do is # touch COMMENT DESCR 5. Run "make package", ensuring that the FORMATS variable is set to the formats you want to build. # make "FORMATS=html html-split ps pdf rtf" package 6. Sit back and relax, it takes a while. When it's finished, look at the .tgz files that have been created. Note that package building *will* update the installed documentation under /usr/share/doc/. If there's a way to work around this (so that you can build the package containing files in one directory, but so that when you run pkg_add(1) the files are installed in a different directory) I'd like to know about it. This is still proof of concept. For example, when it's finished, it would be nice if the DESCR could be automatically generated by pulling out the ... that might be in the source, and the name of the generated package should probably be something like ...tgz so faq.en_US.ISO_8859-1.pdf.tgz But I think it currently fits the 80/20 rule reasonably well. If you put COMMENT and DESCR files in all the appropriate directories you should certainly be able to do something like # cd /usr/doc # make "FORMATS=html html-split ps pdf rtf" package # find . -name \*.tgz -exec scp {} wcarchive:/archive/pub/FreeBSD/doc \; which is how I intend to automate building these things and ensuring that wcarchive is kept up to date. Does that all make sense? I don't think there's anything there that's egregiously stupid, but it's been known to happen before :-) N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch Index: docproj.docbook.mk =================================================================== RCS file: /home/ncvs/doc/share/mk/docproj.docbook.mk,v retrieving revision 1.9 diff -u -r1.9 docproj.docbook.mk --- docproj.docbook.mk 1999/08/19 00:07:09 1.9 +++ docproj.docbook.mk 1999/08/22 07:40:27 @@ -90,7 +90,7 @@ JADEOPTS= ${JADEFLAGS} -c ${FREEBSDCATALOG} -c ${DSSSLCATALOG} -c ${DOCBOOKCATALOG} -c ${JADECATALOG} ${EXTRA_CATALOGS:S/^/-c /g} -KNOWN_FORMATS= html html-split html-split.tar txt rtf ps pdf tex dvi tar doc +KNOWN_FORMATS= html html-split html-split.tar txt rtf ps pdf tex dvi tar # ------------------------------------------------------------------------ # If DOC_PREFIX is not set then try and generate a sensible value for it. @@ -279,6 +279,36 @@ validate: nsgmls -s -c ${FREEBSDCATALOG} -c ${DOCBOOKCATALOG} ${EXTRA_CATALOGS:S/^/-c /g} ${DOC}.sgml + +# ------------------------------------------------------------------------ +# +# Package building +# + +# +# Build a list of package targets for each output format. Each package +# target depends on the corresponding install target running. +# +.for _curformat in ${KNOWN_FORMATS} +_cf=${_curformat} +package-${_curformat}: install-${_curformat} + rm PLIST +.if ${_cf} == "html-split" + cp HTML.manifest PLIST +.else + echo ${DOC}.${_curformat} > PLIST +.endif + pkg_create -v -c COMMENT -d DESCR -f PLIST -p ${DESTDIR} \ + ${DOC}.${_curformat}.tgz +.endfor + +# +# Build one or more pkg_add(1)'able packages, based on all the current +# values of ${FORMATS}. Do this by listing all the appropriate +# package-* targets as dependencies. +# + +package: ${FORMATS:S/^/package-/} # ------------------------------------------------------------------------ # --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 12:13:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id C3B3614C31 for ; Wed, 25 Aug 1999 12:13:44 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id VAA27520 for ; Wed, 25 Aug 1999 21:12:39 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id VAA24030 for ; Wed, 25 Aug 1999 21:12:38 +0200 (MET DST) Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id VAA19250 for ; Wed, 25 Aug 1999 21:12:38 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id TAA88084 for current@FreeBSD.ORG; Wed, 25 Aug 1999 19:12:38 GMT (envelope-from ust) Date: Wed, 25 Aug 1999 21:12:38 +0200 From: Udo Schweigert To: current@FreeBSD.ORG Subject: Libraries broken in -CURRENT Message-ID: <19990825211238.A88039@alaska.cert.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i X-Operating-System: FreeBSD 3.2-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I just cvsuped -CURRENT and got the following error (only the first of many): -------------------------------------------------------------- >>> Rebuilding bootstrap libraries -------------------------------------------------------------- cd /work/src/HEAD; BISON_SIMPLE=/usr/obj/work/src/HEAD/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/work/src/HEAD/tmp/usr/libexec:/usr/obj/work/src/HEAD/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/work/src/HEAD/tmp/usr/lib:/usr/obj/work/src/HEAD/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/work/src/HEAD/tmp/usr/lib LIBRARY_PATH=/usr/obj/work/src/HEAD/tmp/usr/lib:/usr/obj/work/src/HEAD/tmp/usr/lib NOEXTRADEPEND=t PATH=/usr/obj/work/src/HEAD/tmp/sbin:/usr/obj/work/src/HEAD/tmp/usr/sbin:/usr/obj/work/src/HEAD/tmp/bin:/usr/obj/work/src/HEAD/tmp/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:.:/usr/local/bin:/usr/local/pilot/bin:/home/ust/bin/file:/home/ust/bin/sys:/home/ust/bin/misc:/home/ust/bin/dev:/sbin:/usr/sbin:/usr/X11R6/bin:.:/usr/local/bin:/usr/local/pilot/bin:/home/ust/bin/file:/home/ust/bin/sys:/home/ust/bin/misc:/home/ust/bin/dev:/home/ust/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin OBJFORMAT_PATH=/usr/obj/work/src/HEAD/tmp/usr/libexec:/usr/libexec /usr/obj/work/src/HEAD! /t! ! mp/usr/bin/make DESTDIR=/usr/obj/work/src/HEAD/tmp -f Makefile.inc1 bootstrap-libraries cd /work/src/HEAD/lib/csu/i386-elf; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/work/src/HEAD/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/work/src/HEAD/lib/csu/i386-elf/GPATH /usr/obj/work/src/HEAD/lib/csu/i386-elf/GRTAGS /usr/obj/work/src/HEAD/lib/csu/i386-elf/GSYMS /usr/obj/work/src/HEAD/lib/csu/i386-elf/GTAGS cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crt1.c -o crt1.o cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crtbegin.c -o crtbegin.o /work/src/HEAD/lib/csu/i386-elf/crtbegin.c:32: section attributes are not supported for this target /work/src/HEAD/lib/csu/i386-elf/crtbegin.c:33: section attributes are not supported for this target *** Error code 1 (continuing) cc -O -pipe -elf -Wall -fkeep-inline-functions -I/usr/obj/work/src/HEAD/tmp/usr/include -c /work/src/HEAD/lib/csu/i386-elf/crtend.c -o crtend.o /work/src/HEAD/lib/csu/i386-elf/crtend.c:32: section attributes are not supported for this target /work/src/HEAD/lib/csu/i386-elf/crtend.c:33: section attributes are not supported for this target *** Error code 1 (continuing) Best regards ------------------------------------------------------------------------------- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT || Fax : +49 89 636 48000 ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de D-81730 Muenchen / Germany || : ust@cert.siemens.de PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 14:29:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 12CF014DC8; Wed, 25 Aug 1999 14:29:16 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA16787; Wed, 25 Aug 1999 14:27:05 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nik Clayton Cc: "Jordan K. Hubbard" , jack , current@freebsd.org, asami@freebsd.org, doc@freebsd.org Subject: Re: Docs blows up make release In-reply-to: Your message of "Wed, 25 Aug 1999 12:38:19 BST." <19990825123819.A2177@kilt.nothing-going-on.org> Date: Wed, 25 Aug 1999 14:27:05 -0700 Message-ID: <16783.935616425@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just an update on that. I've been working on this with Jack O'Neill, and > if the reports are favourable I'll have one small patch to > src/release/Makefile and one small patch to doc/*/Makefile to go in some > time in the next 48 hours or so which should get release builds working. Great, sounds good. > Note that this won't include any fixes to teach sysinstall about the new > paths under /usr/share/doc/, although you should have seen a patch I sent > you about that by now. Hmm, I still have 3000 mails I'm going through here... sysinstall required changes? I thought everything was still under /usr/share/doc, or are the subdirs different now? > This assumes that the documentation is also listed in the ports tree. > > I don't think this is a great idea -- more specifically, I don't think > this is a great idea as the primary mechanism for making packages of > the documentation. I've got no problems with it being another way to > make doc packages. Hmmm. How else were you thinking of making "doc packages" then - wasn't that the whole project you were working on? > This makes the ports tree have a dependency on the doc tree. I don't think > this dependency should be there. It's bad enough that the src/ tree > depends on doc/ (and the reason I want the documentation available as > packages is to remove this dependency), having ports depend on the doc tree > as well just means that when things go out of sync in doc for a while I get > both you and Satoshi complaining at me, instead of just you :-) Erm, I think the ports tree is pretty darn loose about "dependencies" since they're easily updated. Consider, for example, the fact that some ports are dependent on the organization of binary tarballs over at Netscape, or depend on WordPerfect's linux distribution RPM. Those are some pretty heavy deps, and depending on something in our own doc tree is certainly no worse. :) > Putting the package building rules in the doc/ Makefiles also (and this > is just my personal opinion) makes it easier for people to see how the > documentation packages are built. The ports Makefile structure is a > marvel, but it contains a lot of code that's not necessary for building > documentation packages (the "automagically add man pages to the PLIST > i" code, for example) that makes it more difficult for the interested > learner to browse and understand what's going on. Now this is a point which is more germin. So, you figure on making a similar sort of "package" target under doc? I guess it really doesn't matter where these things live, as long as it's still automated.. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 15: 7:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 264B3152CE for ; Wed, 25 Aug 1999 15:07:35 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA17129; Wed, 25 Aug 1999 15:06:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: "Jordan K. Hubbard" , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Wed, 25 Aug 1999 09:34:03 PDT." <199908251634.JAA04358@dingo.cdrom.com> Date: Wed, 25 Aug 1999 15:06:24 -0700 Message-ID: <17125.935618784@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The issue with boggle and tetris wasn't the name, it was "look and feel". No, it was the name. Believe me, I read the letters we got from their lawyers. :) Unless we produce a movie with the name "Matrix" somewhere in it, I doubt we're going to be in the same boat. Hasbro objected to our having a game in /usr/games called boggle and the Tetris folks objected to the use of the name. Other folks chose to rename their tetris clones to "tertis" and made the Tetris folks perfectly happy in so doing, even though the look-and-feel of the game remained completely unchanged. You are trying to apply rules of logic to this. This is a legal issue. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 16:14:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3]) by hub.freebsd.org (Postfix) with ESMTP id 6F7691534D for ; Wed, 25 Aug 1999 16:14:38 -0700 (PDT) (envelope-from dima@tejblum.pp.ru) Received: (from uucp@localhost) by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id DAA99345; Thu, 26 Aug 1999 03:13:51 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Received: from tejblum.pp.ru (localhost [127.0.0.1]) by tejblum.pp.ru (8.9.3/8.9.3) with ESMTP id DAA02382; Thu, 26 Aug 1999 03:15:00 +0400 (MSD) (envelope-from dima@tejblum.pp.ru) Message-Id: <199908252315.DAA02382@tejblum.pp.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Doug Rabson Cc: current@FreeBSD.ORG From: Dmitrij Tejblum Subject: Re: NFSv3 on freebsd<-->solaris In-reply-to: Your message of "Wed, 25 Aug 1999 08:52:40 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Aug 1999 03:15:00 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > This is probably because our server detects that the directory has been > modified and rejects the solaris client's directory cookies. I think we should not ever reject a client's cookie. Consider a local program that scan the directoty with the getdirentries() syscall. The offset in the directory is essentially the cookie that would be sent to an NFS client. But we never "reject" the offset, and everyone is happy. (Not to mention NFSv2, where we never reject a client's cookie too). So, what we are trying to achieve by rejecting a NFSv3 client's cookie? > Instead of > recovering, the solaris client barfs. Its a solaris bug really IMHO, it is very arguable. Why the client should "recover" after "stale cookie" error, but should not recover after "stale filehandle" error? How should it perform the recovery: If a reliable recovery is possible, why it is not done on the server? (After all, Sun know how NFSv3 should work, since they wrote the spec, right? :-|) Dima Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 19:47:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (Postfix) with ESMTP id 5DF1D15411 for ; Wed, 25 Aug 1999 19:47:41 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from HEATHER (adsl-216-102-57-10.dsl.sktn01.pacbell.net [216.102.57.10]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id TAA16647 for ; Wed, 25 Aug 1999 19:46:51 -0700 (PDT) Message-ID: <000501beef6c$874bf0c0$0a3966d8@HEATHER> From: "Bret Ford" To: Subject: 3C597 fast ethernet support Date: Wed, 25 Aug 1999 19:41:39 -0700 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a 100Mbit 3COM EISA ethernet interface. Here are the particulars: vx0: <3Com 3C597-TX Network Adapter> at 0x5000-0x501f, 0x5c80-0x5c89 vx0: irq 12 (edge) on eisa0 slot 5 I've been running it for a while now at 10Mbit. From what I can gather, the vx driver doesn't support fast ethernet. I'd be happy to lend the card to anyone interested in working on it. The reward would be my gratitude and money for your favorite pizza and beverages! :-) Any interest? Thanks, Bret Ford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 20: 3:52 1999 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 7AECF14E94 for ; Wed, 25 Aug 1999 20:03:49 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id XAA19835; Wed, 25 Aug 1999 23:03:33 -0400 (EDT) Date: Wed, 25 Aug 1999 23:03:32 -0400 (EDT) From: "Matthew N. Dodd" To: Bret Ford Cc: current@FreeBSD.ORG Subject: Re: 3C597 fast ethernet support In-Reply-To: <000501beef6c$874bf0c0$0a3966d8@HEATHER> 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, 25 Aug 1999, Bret Ford wrote: > I've got a 100Mbit 3COM EISA ethernet interface. Here are the particulars: > > vx0: <3Com 3C597-TX Network Adapter> at 0x5000-0x501f, 0x5c80-0x5c89 > vx0: irq 12 (edge) on eisa0 slot 5 > > I've been running it for a while now at 10Mbit. From what I can > gather, the vx driver doesn't support fast ethernet. I'd be happy to > lend the card to anyone interested in working on it. The reward would > be my gratitude and money for your favorite pizza and beverages! :-) > Any interest? I've actually been keeping an eye open for one of those but haven't managed to grab one yet. I've intended on getting one and fiddling with it but currently have no time. If you find one for $10 or less grab it and I'll pay cost plus shipping. If its on my shelf I'll likely look at it at some point. I've got code for the Compaq NetFlex 3/E that gloms on to Bill's Thunderland driver that I've not managed to get working correctly yet. This card also supports 100 meg mode. (Damn Compaq for not having doc available.) -- | 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 Wed Aug 25 20: 4:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A962614E94 for ; Wed, 25 Aug 1999 20:04:50 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA00956; Wed, 25 Aug 1999 20:03:14 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Andrzej Bialecki Cc: Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Mon, 23 Aug 1999 23:57:23 +0200." Date: Wed, 25 Aug 1999 20:03:14 -0700 Message-ID: <953.935636594@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry you got so beaten up over this one. All due respect to the contributors aside, I think we have too many old women around here, all shrieking and holding up their skirts at the rumor of a mouse somewhere in the building. :) - Jordan > On Mon, 23 Aug 1999, Mike Smith wrote: > > > Just make it a port, for crap's sake, and distribute it from Poland. > > By the time WB's American lawyers work out where you are on the map, > > the statute of limitations will have expired and you'll be fine. > > > > But it's not going into the tree, no. I think Kevin's point and the > > experiences we had with Hasbro should already have convinced people of > > that much. > > I'm tired of this. It has priority number -infinity on my list. Do with it > what you want - the code is there. I won"t put it in the tree. > > 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 Aug 25 20:12:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 5BA5F14E94 for ; Wed, 25 Aug 1999 20:12:50 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org (ppp-207-214-149-48.snrf01.pacbell.net [207.214.149.48]) by mta1.snfc21.pbi.net (8.9.3/8.9.3) with ESMTP id UAA03354; Wed, 25 Aug 1999 20:12:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 7ACB49155C; Wed, 25 Aug 1999 20:10:44 -0700 (PDT) Date: Wed, 25 Aug 1999 20:10:44 -0700 (PDT) From: Alex Zepeda To: Wilko Bulte Cc: freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-Reply-To: <199908251808.UAA00709@yedi.iaf.nl> 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, 25 Aug 1999, Wilko Bulte wrote: > The USA... your prices tend to be a lot better than ours. I could can the > T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs > now), get an AGP videocard and can the perfectly fine Millenium II (I need > the extra PCI slot quite badly) and buy a new CPU. Oh, and buy an ATX case. > In the end that is quite a bit more than $80. Unfortunately. Doesn't Asus make an AT formfactor Super 7 motherboard w/ a 100mhz bus? I'm pretty sure it has DIMM and SIMM slots on it too (well I think their ATX board does too); obviously using both at the same time won't work well.. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 20:42:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 1DFF514EE7 for ; Wed, 25 Aug 1999 20:42:35 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id XAA25550 for ; Wed, 25 Aug 1999 23:40:26 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA09870; Wed, 25 Aug 1999 23:39:56 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA36428 for freebsd-current@freebsd.org; Wed, 25 Aug 1999 23:39:56 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908260339.XAA36428@bb01f39.unx.sas.com> Subject: make world failure (signal 11 in cpp) To: freebsd-current@freebsd.org Date: Wed, 25 Aug 1999 23:39:56 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having problems making world... before I dig into this, does anyone already know what's going on? My source is current as of 11:30pm EST. thanks, John ===> cpp cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y *** Signal 11 Stop in /usr/src/gnu/usr.bin/cc/cpp. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 20:45:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5A56414CF0 for ; Wed, 25 Aug 1999 20:45:25 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA05182; Thu, 26 Aug 1999 13:15:17 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA09108; Thu, 26 Aug 1999 13:15:16 +0930 (CST) Date: Thu, 26 Aug 1999 13:15:15 +0930 From: Greg Lehey To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world failure (signal 11 in cpp) Message-ID: <19990826131514.B8184@freebie.lemis.com> References: <199908260339.XAA36428@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908260339.XAA36428@bb01f39.unx.sas.com>; from John W. DeBoskey on Wed, Aug 25, 1999 at 11:39:56PM -0400 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, 25 August 1999 at 23:39:56 -0400, John W. DeBoskey wrote: > Hi, > > I'm having problems making world... before I dig into this, does > anyone already know what's going on? My source is current as of > 11:30pm EST. > > thanks, > John > > ===> cpp > cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c > yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y > *** Signal 11 The canonical explanation for this sort of thing is processor or memory problems. Would that fit? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 21:14:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 1BB2B153C9 for ; Wed, 25 Aug 1999 21:14:43 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id AAA26798; Thu, 26 Aug 1999 00:11:50 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA11604; Thu, 26 Aug 1999 00:11:20 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id AAA36535; Thu, 26 Aug 1999 00:11:20 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908260411.AAA36535@bb01f39.unx.sas.com> Subject: Re: make world failure (signal 11 in cpp) In-Reply-To: <19990826131514.B8184@freebie.lemis.com> from Greg Lehey at "Aug 26, 1999 1:15:15 pm" To: grog@lemis.com (Greg Lehey) Date: Thu, 26 Aug 1999 00:11:20 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wednesday, 25 August 1999 at 23:39:56 -0400, John W. DeBoskey wrote: > > Hi, > > > > I'm having problems making world... before I dig into this, does > > anyone already know what's going on? My source is current as of > > 11:30pm EST. > > > > thanks, > > John > > > > ===> cpp > > cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c > > yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y > > *** Signal 11 > > The canonical explanation for this sort of thing is processor or > memory problems. Would that fit? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key I really doubt it, though I can replace the memory and swap machines tomorrow if I need to. It is a stock machine from Dell with no mods. This machine has been dedicated to building -current SNAP's for more than 8 months. When this machine has problems, the typical problem is bad code getting into the system, or a corrupted filesystem (I nolonger run any of my filesystems async for this reason). fyi, this problem does replicate at the exact same location. It appears to actually be yacc... /usr/obj/usr/src/gnu/usr.bin/cc/cpp %ls -al drwxr-xr-x 2 root wheel 512 Aug 25 23:53 . drwxr-xr-x 16 root wheel 512 Aug 25 23:47 .. -rw-r--r-- 1 root wheel 92936 Aug 25 23:53 cccp.o -rw------- 1 root wheel 147456 Aug 25 23:53 yacc.core /usr/obj/usr/src/gnu/usr.bin/cc/cpp %file yacc.core yacc.core: ELF 32-bit LSB core file, Intel 80386, version 1 (FreeBSD), from 'yacc' gdb says the following: (no debugging symbols found)... Core was generated by `yacc'. Program terminated with signal 11, Segmentation fault. #0 0x8051bec in free () I guess I'll try to build a debug version next... Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 25 22:14:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 17D5F153EC for ; Wed, 25 Aug 1999 22:14:26 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.158]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAAE0B; Thu, 26 Aug 1999 07:13:24 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id HAA33323; Thu, 26 Aug 1999 07:03:15 +0200 (CEST) (envelope-from asmodai) Date: Thu, 26 Aug 1999 07:03:15 +0200 From: Jeroen Ruigrok/Asmodai To: Greg Lehey Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: make world failure (signal 11 in cpp) Message-ID: <19990826070315.A33283@daemon.ninth-circle.org> References: <199908260339.XAA36428@bb01f39.unx.sas.com> <19990826131514.B8184@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19990826131514.B8184@freebie.lemis.com> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey (grog@lemis.com) [990826 06:19]: >On Wednesday, 25 August 1999 at 23:39:56 -0400, John W. DeBoskey wrote: >> ===> cpp >> cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c >> yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y >> *** Signal 11 > >The canonical explanation for this sort of thing is processor or >memory problems. Would that fit? Could I think, but... Last time I had that when making a week/two week old CURRENT to the current CURRENT I got sig 11's on all my compiles. I had to install a snapshot cc in order to rebuilt libc and cc and then make world again. Everything compiled core dumped with the first compiler. After reinstalling cc, no more problems. So compliers and Sig 11's are harder to troubleshoot, at least IMHO. HTH, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Man shall not live by bread alone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 1:54: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id DB57314F18 for ; Thu, 26 Aug 1999 01:54:04 -0700 (PDT) (envelope-from dfr@nlsystems.com) 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 KAA46928; Thu, 26 Aug 1999 10:04:06 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 26 Aug 1999 10:04:06 +0100 (BST) From: Doug Rabson To: Dmitrij Tejblum Cc: current@FreeBSD.ORG Subject: Re: NFSv3 on freebsd<-->solaris In-Reply-To: <199908252315.DAA02382@tejblum.pp.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 Thu, 26 Aug 1999, Dmitrij Tejblum wrote: > Doug Rabson wrote: > > > > This is probably because our server detects that the directory has been > > modified and rejects the solaris client's directory cookies. > > I think we should not ever reject a client's cookie. Consider a local > program that scan the directoty with the getdirentries() syscall. The > offset in the directory is essentially the cookie that would be sent to > an NFS client. But we never "reject" the offset, and everyone is happy. > (Not to mention NFSv2, where we never reject a client's cookie too). > So, what we are trying to achieve by rejecting a NFSv3 client's cookie? Notify the client that the directory contents may have been compacted and therefore that their seek offsets are now wrong. > > > Instead of > > recovering, the solaris client barfs. Its a solaris bug really > > IMHO, it is very arguable. Why the client should "recover" after "stale > cookie" error, but should not recover after "stale filehandle" error? > How should it perform the recovery: If a reliable recovery is possible, > why it is not done on the server? Stale cookie is completely different from stale filehandle and in general it isn't possible to recover on the server. > > (After all, Sun know how NFSv3 should work, since they wrote the spec, > right? :-|) From rfc1813: In the NFS version 3 protocol, each READDIR request includes both a cookie and a cookie verifier. For the first call, both are set to 0. The response includes a new cookie verifier, with a cookie per entry. For subsequent READDIRs, the client must present both the cookie and the corresponding cookie verifier. If the server detects that the cookie is no longer valid, the server will reject the READDIR request with the status, NFS3ERR_BAD_COOKIE. The client should be careful to avoid holding directory entry cookies across operations that modify the directory contents, such as REMOVE and CREATE. It seems to me that the solaris client is holding directory cookies across a REMOVE operation and therefore should expect to get stale cookie errors occaisionally. Our NFS client used to have the same problem (a long time ago) and I put code into it to re-read the directory if its cookies are stale. -- 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 Thu Aug 26 2:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-7.cpinternet.com [208.149.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 0832514E6D; Thu, 26 Aug 1999 02:12:49 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id EAA32087; Thu, 26 Aug 1999 04:12:44 -0500 (CDT) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 26 Aug 1999 04:12:44 -0500 (CDT) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: wilko@yedi.iaf.nl Cc: chat@freebsd.org Subject: K6-2 motherboards Was, Re: Softupdates reliability? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14277.853.14817.919574@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to chat] : > Yes, you stand a far better chance of making this hack work with a 66MHz : > part. No the newer std parts are not designed to run with a 66MHz FSB, : > you should always order them as /66. Note that AMD has stopped making : > these chips due to low demand for them (with 100MHz boards <$80 USA the : > price/performance is usually worth it for most folks.) : : The USA... your prices tend to be a lot better than ours. I could can the : T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs : now), get an AGP videocard and can the perfectly fine Millenium II (I need : the extra PCI slot quite badly) and buy a new CPU. Oh, and buy an ATX case. : In the end that is quite a bit more than $80. Unfortunately. I like the Tyan "Trinity", S1590AT. SIMM sockets, DIMM sockets, highly variable clocks and voltages throughout, AT *or* ATX power, PS/2 mouse, USB header, IR support. Works with K6-2 and K6-3 to 500MHz. 1AGP + 4PCI + 4ISA. Very flexible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 3: 1:45 1999 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 CD5CE15509 for ; Thu, 26 Aug 1999 03:01:37 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id DAA47384; Thu, 26 Aug 1999 03:00:27 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908261000.DAA47384@gndrsh.dnsmgr.net> Subject: Re: Softupdates reliability? In-Reply-To: from Alex Zepeda at "Aug 25, 1999 08:10:44 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Thu, 26 Aug 1999 03:00:26 -0700 (PDT) Cc: wilko@yedi.iaf.nl (Wilko Bulte), 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 > On Wed, 25 Aug 1999, Wilko Bulte wrote: > > > The USA... your prices tend to be a lot better than ours. I could can the > > T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs > > now), get an AGP videocard and can the perfectly fine Millenium II (I need > > the extra PCI slot quite badly) and buy a new CPU. Oh, and buy an ATX case. > > In the end that is quite a bit more than $80. Unfortunately. > > Doesn't Asus make an AT formfactor Super 7 motherboard w/ a 100mhz bus? > > I'm pretty sure it has DIMM and SIMM slots on it too (well I think their > ATX board does too); obviously using both at the same time won't work > well.. Yes, the do, forget the model number, but the few we looked at we did not like the ASUS version as they went with the Ali chipset, and we have had better luck with the Via MVP3. We use the Soltek SL54U1/U5, works great, and if you want it in ATX DIMM only order the SL56D1. You can look at thier products on www.soltek.com.tw, we are an authorized distributor who stocks both the SL54U5 (was stocking SL54U1, but they are in very short supply due to cache chip shortage) and SL56D1. Both are sub $80.00 boards, both run FreeBSD just dandy. -- Rod Grimes - KD7CAX - (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 Thu Aug 26 3:26:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.iol.ie (mail2.mail.iol.ie [194.125.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 5243015CCF for ; Thu, 26 Aug 1999 03:26:20 -0700 (PDT) (envelope-from nick@iol.ie) Received: from beckett.earlsfort.iol.ie (beckett.earlsfort.iol.ie [194.125.21.2]) by mail.iol.ie Sendmail (v8.9.3) with ESMTP id LAA38245; Thu, 26 Aug 1999 11:24:37 +0100 (IST) Received: (from nick@localhost) by beckett.earlsfort.iol.ie Sendmail (v8.8.8) id LAA25895; Thu, 26 Aug 1999 11:24:36 +0100 From: Nick Hilliard Message-Id: <199908261024.LAA25895@beckett.earlsfort.iol.ie> Subject: Re: 3C597 fast ethernet support To: bford@uop.cs.uop.edu Date: Thu, 26 Aug 1999 11:24:36 +0100 (IST) Cc: current@FreeBSD.ORG X-NCC-RegID: ie.iol Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a 100Mbit 3COM EISA ethernet interface. Here are the particulars: > > vx0: <3Com 3C597-TX Network Adapter> at 0x5000-0x501f, 0x5c80-0x5c89 > vx0: irq 12 (edge) on eisa0 slot 5 > > I've been running it for a while now at 10Mbit. From what I can gather, the > vx driver doesn't support fast ethernet. I'd be happy to lend the card to > anyone interested The vx driver supports FE speeds, just not very well. The problem is caused by the fact that the vx driver uses the 3com programmed I/O mechanism for talking to the nic, and this protocol is just not up to dealing with 100mbit speeds because its 4-byte buffer is far too small to handle large amounts of data very quickly. Its been some while since I've used the vx driver myself, but I remember being pretty disappointed by the speed of it. There's more about this in http://www.freebsd.org/~wpaul/3Com/. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 7:21:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 5425614E4A for ; Thu, 26 Aug 1999 07:21:49 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA25515; Thu, 26 Aug 1999 10:21:39 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15752; Thu, 26 Aug 1999 10:21:09 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA43149; Thu, 26 Aug 1999 10:21:08 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908261421.KAA43149@bb01f39.unx.sas.com> Subject: Re: make world failure (signal 11 in cpp) In-Reply-To: <19990826131514.B8184@freebie.lemis.com> from Greg Lehey at "Aug 26, 1999 1:15:15 pm" To: grog@lemis.com (Greg Lehey) Date: Thu, 26 Aug 1999 10:21:08 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, To answer my own question, I came into work this morning and found my console full of messages... spec_getpages: I/O read failure: (error code=0) bp 0xc36fe9a0 vp 0xc92ce000 size: 0, resid: 0, a_count: 4096, valid: 0x0 nread: 0, reqpage: 0, pindex: 9, pcount: 1 vm_fault: pager read error, pid 56587 (yacc) Aug 25 23:53:56 FreeBSD /kernel: pid 56587 (yacc), uid 0: exited on signal 11 (c ore dumped) spec_getpages: I/O read failure: (error code=0) bp 0xc36ffe20 vp 0xc92ce000 size: 0, resid: 0, a_count: 65536, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 16 spec_getpages: I/O read failure: (error code=0) bp 0xc37000b0 vp 0xc92ce000 size: 0, resid: 0, a_count: 4096, valid: 0x0 nread: 0, reqpage: 0, pindex: 9, pcount: 1 vm_fault: pager read error, pid 6178 (yacc) Aug 26 00:34:27 FreeBSD /kernel: pid 6178 (yacc), uid 0: exited on signal 11 (co re dumped) If I reboot my system with a kernel which is about two weeks old, things run fine... I'm not sure where to go from here... I'd appreciate any help. Again, my source (and kernel which is failing) is current as of 11:30pm EST, 8/25/99. Thanks, -John > On Wednesday, 25 August 1999 at 23:39:56 -0400, John W. DeBoskey wrote: > > Hi, > > > > I'm having problems making world... before I dig into this, does > > anyone already know what's going on? My source is current as of > > 11:30pm EST. > > > > thanks, > > John > > > > ===> cpp > > cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config -DFREEBSD_NATIVE -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"egcs-2.91.66\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -I/usr/src/gnu/usr.bin/cc/cpp/../cc_tools -DPREFIX=\"/usr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cccp.c > > yacc -o cexp.c /usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/cexp.y > > *** Signal 11 > > The canonical explanation for this sort of thing is processor or > memory problems. Would that fit? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12: 2:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 00B09153E4 for ; Thu, 26 Aug 1999 12:02:41 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id PAA09908 for ; Thu, 26 Aug 1999 15:00:26 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA10227; Thu, 26 Aug 1999 14:59:56 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id OAA46012 for freebsd-current@freebsd.org; Thu, 26 Aug 1999 14:59:55 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908261859.OAA46012@bb01f39.unx.sas.com> Subject: -current kernel problems (spec_getpages & vm_fault) To: freebsd-current@freebsd.org Date: Thu, 26 Aug 1999 14:59:55 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Following up my own mail on sig 11 problems, I beleive the problem is kernel related. Running a kernel with sources current as of 11:30am EST, I get the following during a make world: spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 size: 0, resid: 0, a_count: 12288, valid: 0x0 nread: 0, reqpage: 0, pindex: 14, pcount: 3 vm_fault: pager read error, pid 37394 (install) Aug 26 14:08:44 FreeBSD /kernel: pid 37394 (install), uid 0: exited on signal 11 (core dumped) which is generated by this portion of the make world: install -c -s -o root -g wheel -m 555 nvi /usr/obj/usr/src/tmp/usr/bin *** Signal 11 If I reboot with a kernel built on Aug 16, I can run a complete make world with no failures. I realize alot of changes have gone into the system over the last few days. If someone can give me some pointers on getting the information required to debug the problem, I'll be more than happy to dig into it. Thanks, John -- dmesg output for the machine in question: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Aug 26 13:47:34 EDT 1999 toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 398775825 Hz CPU: Pentium II/Xeon/Celeron (398.78-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 126881792 (123908K bytes) Preloaded elf kernel "kernel" at 0xc0306000. Pentium Pro MTRR support enabled ccd0-3: Concatenated disk drivers npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 3 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 fxp0: irq 10 at device 13.0 on pci0 fxp0: Ethernet address 00:a0:c9:2d:14:1b ahc0: irq 9 at device 14.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs pcib2: at device 15.0 on pci0 pci2: on pcib2 vga-pci1: irq 3 at device 9.0 on pci2 ahc1: irq 11 at device 10.0 on pci2 ahc1: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: irq 10 at device 10.1 on pci2 ahc2: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs ti0: <3Com 3c985-SX Gigabit Ethernet> irq 3 at device 11.0 on pci2 ti0: Ethernet address: 00:60:08:f5:c6:e5 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, dma, iordy wdc1: ATAPI CD-ROMs not configured atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 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: configured irq 3 not in bitmap of probed irqs 0 Waiting 5 seconds for SCSI devices to settle changing root device to wd0s1a da5 at ahc2 bus 0 target 3 lun 0 da5: Removable Direct Access SCSI-2 device da5: 20.000MB/s transfers (20.000MHz, offset 15) da5: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C) da2 at ahc0 bus 0 target 3 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da4 at ahc0 bus 0 target 5 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da4: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) cd0 at ahc2 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 size: 0, resid: 0, a_count: 12288, valid: 0x0 nread: 0, reqpage: 0, pindex: 14, pcount: 3 vm_fault: pager read error, pid 37394 (install) pid 37394 (install), uid 0: exited on signal 11 (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:14:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0BDAD153E4 for ; Thu, 26 Aug 1999 12:14:24 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA78875; Thu, 26 Aug 1999 12:13:17 -0700 (PDT) Date: Thu, 26 Aug 1999 12:13:36 -0700 (PDT) From: Julian Elischer To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <199908261859.OAA46012@bb01f39.unx.sas.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 fixed earlier today... On Thu, 26 Aug 1999, John W. DeBoskey wrote: > Hi, > > Following up my own mail on sig 11 problems, I beleive the > problem is kernel related. Running a kernel with sources current > as of 11:30am EST, I get the following during a make world: > > spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > size: 0, resid: 0, a_count: 12288, valid: 0x0 > nread: 0, reqpage: 0, pindex: 14, pcount: 3 > vm_fault: pager read error, pid 37394 (install) > Aug 26 14:08:44 FreeBSD /kernel: pid 37394 (install), uid 0: exited on signal 11 > (core dumped) > > > which is generated by this portion of the make world: > > install -c -s -o root -g wheel -m 555 nvi /usr/obj/usr/src/tmp/usr/bin > *** Signal 11 > > > > If I reboot with a kernel built on Aug 16, I can run a complete > make world with no failures. I realize alot of changes have gone > into the system over the last few days. If someone can give me some > pointers on getting the information required to debug the problem, I'll > be more than happy to dig into it. > > > Thanks, > John > > > -- > dmesg output for the machine in question: > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Thu Aug 26 13:47:34 EDT 1999 > toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 398775825 Hz > CPU: Pentium II/Xeon/Celeron (398.78-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > Features=0x183f9ff > real memory = 134217728 (131072K bytes) > avail memory = 126881792 (123908K bytes) > Preloaded elf kernel "kernel" at 0xc0306000. > Pentium Pro MTRR support enabled > ccd0-3: Concatenated disk drivers > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 3 at device 0.0 on pci1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ide_pci0: at device 7.1 on pci0 > chip1: irq 11 at device 7.2 on pci0 > chip2: at device 7.3 on pci0 > fxp0: irq 10 at device 13.0 on pci0 > fxp0: Ethernet address 00:a0:c9:2d:14:1b > ahc0: irq 9 at device 14.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > pcib2: at device 15.0 on pci0 > pci2: on pcib2 > vga-pci1: irq 3 at device 9.0 on pci2 > ahc1: irq 11 at device 10.0 on pci2 > ahc1: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc2: irq 10 at device 10.1 on pci2 > ahc2: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs > ti0: <3Com 3c985-SX Gigabit Ethernet> irq 3 at device 11.0 on pci2 > ti0: Ethernet address: 00:60:08:f5:c6:e5 > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at port 0x170-0x177 irq 15 on isa0 > wdc1: unit 0 (atapi): , removable, dma, iordy > wdc1: ATAPI CD-ROMs not configured > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > 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: configured irq 3 not in bitmap of probed irqs 0 > Waiting 5 seconds for SCSI devices to settle > changing root device to wd0s1a > da5 at ahc2 bus 0 target 3 lun 0 > da5: Removable Direct Access SCSI-2 device > da5: 20.000MB/s transfers (20.000MHz, offset 15) > da5: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C) > da2 at ahc0 bus 0 target 3 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > da3 at ahc0 bus 0 target 4 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > da0 at ahc0 bus 0 target 1 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da4 at ahc0 bus 0 target 5 lun 0 > da4: Fixed Direct Access SCSI-2 device > da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da4: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > cd0 at ahc2 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 3.300MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed > spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > size: 0, resid: 0, a_count: 12288, valid: 0x0 > nread: 0, reqpage: 0, pindex: 14, pcount: 3 > vm_fault: pager read error, pid 37394 (install) > pid 37394 (install), uid 0: exited on signal 11 (core dumped) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:17: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0489215C96 for ; Thu, 26 Aug 1999 12:16:55 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA79191; Thu, 26 Aug 1999 12:16:32 -0700 (PDT) Date: Thu, 26 Aug 1999 12:16:51 -0700 (PDT) From: Julian Elischer To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <199908261859.OAA46012@bb01f39.unx.sas.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 swapping on a vn device? the 'size' and 'resid' of 0 looks suspicious. a fix was just committed to teh vn code that may fix this if that's your problem. On Thu, 26 Aug 1999, John W. DeBoskey wrote: > Hi, > > Following up my own mail on sig 11 problems, I beleive the > problem is kernel related. Running a kernel with sources current > as of 11:30am EST, I get the following during a make world: > > spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > size: 0, resid: 0, a_count: 12288, valid: 0x0 > nread: 0, reqpage: 0, pindex: 14, pcount: 3 > vm_fault: pager read error, pid 37394 (install) > Aug 26 14:08:44 FreeBSD /kernel: pid 37394 (install), uid 0: exited on signal 11 > (core dumped) > > > which is generated by this portion of the make world: > > install -c -s -o root -g wheel -m 555 nvi /usr/obj/usr/src/tmp/usr/bin > *** Signal 11 > > > > If I reboot with a kernel built on Aug 16, I can run a complete > make world with no failures. I realize alot of changes have gone > into the system over the last few days. If someone can give me some > pointers on getting the information required to debug the problem, I'll > be more than happy to dig into it. > > > Thanks, > John > > > -- > dmesg output for the machine in question: > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Thu Aug 26 13:47:34 EDT 1999 > toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 398775825 Hz > CPU: Pentium II/Xeon/Celeron (398.78-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > Features=0x183f9ff > real memory = 134217728 (131072K bytes) > avail memory = 126881792 (123908K bytes) > Preloaded elf kernel "kernel" at 0xc0306000. > Pentium Pro MTRR support enabled > ccd0-3: Concatenated disk drivers > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > vga-pci0: irq 3 at device 0.0 on pci1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ide_pci0: at device 7.1 on pci0 > chip1: irq 11 at device 7.2 on pci0 > chip2: at device 7.3 on pci0 > fxp0: irq 10 at device 13.0 on pci0 > fxp0: Ethernet address 00:a0:c9:2d:14:1b > ahc0: irq 9 at device 14.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > pcib2: at device 15.0 on pci0 > pci2: on pcib2 > vga-pci1: irq 3 at device 9.0 on pci2 > ahc1: irq 11 at device 10.0 on pci2 > ahc1: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc2: irq 10 at device 10.1 on pci2 > ahc2: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs > ti0: <3Com 3c985-SX Gigabit Ethernet> irq 3 at device 11.0 on pci2 > ti0: Ethernet address: 00:60:08:f5:c6:e5 > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 > wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at port 0x170-0x177 irq 15 on isa0 > wdc1: unit 0 (atapi): , removable, dma, iordy > wdc1: ATAPI CD-ROMs not configured > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > 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: configured irq 3 not in bitmap of probed irqs 0 > Waiting 5 seconds for SCSI devices to settle > changing root device to wd0s1a > da5 at ahc2 bus 0 target 3 lun 0 > da5: Removable Direct Access SCSI-2 device > da5: 20.000MB/s transfers (20.000MHz, offset 15) > da5: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C) > da2 at ahc0 bus 0 target 3 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > da3 at ahc0 bus 0 target 4 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > da0 at ahc0 bus 0 target 1 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da4 at ahc0 bus 0 target 5 lun 0 > da4: Fixed Direct Access SCSI-2 device > da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da4: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > cd0 at ahc2 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 3.300MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed > spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > size: 0, resid: 0, a_count: 12288, valid: 0x0 > nread: 0, reqpage: 0, pindex: 14, pcount: 3 > vm_fault: pager read error, pid 37394 (install) > pid 37394 (install), uid 0: exited on signal 11 (core dumped) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:19:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CA96515C6C for ; Thu, 26 Aug 1999 12:19:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA24349; Thu, 26 Aug 1999 12:19:14 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Aug 1999 12:19:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199908261919.MAA24349@apollo.backplane.com> To: Julian Elischer Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :swapping on a vn device? :the 'size' and 'resid' of 0 looks suspicious. : :a fix was just committed to teh vn code that may fix this if that's your :problem. A fix was? When? Where? What? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:53:55 1999 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 7303E15446 for ; Thu, 26 Aug 1999 12:53:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA00515; Thu, 26 Aug 1999 21:52:20 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Thu, 26 Aug 1999 12:16:51 PDT." Date: Thu, 26 Aug 1999 21:52:20 +0200 Message-ID: <513.935697140@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The size and resid of 0 is because it decides to use a sectorsize of zero due to the si_bsize fields being empty. In message , Jul ian Elischer writes: >swapping on a vn device? >the 'size' and 'resid' of 0 looks suspicious. > >a fix was just committed to teh vn code that may fix this if that's your >problem. > > >On Thu, 26 Aug 1999, John W. DeBoskey wrote: > >> Hi, >> >> Following up my own mail on sig 11 problems, I beleive the >> problem is kernel related. Running a kernel with sources current >> as of 11:30am EST, I get the following during a make world: >> >> spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 >> size: 0, resid: 0, a_count: 12288, valid: 0x0 >> nread: 0, reqpage: 0, pindex: 14, pcount: 3 >> vm_fault: pager read error, pid 37394 (install) >> Aug 26 14:08:44 FreeBSD /kernel: pid 37394 (install), uid 0: exited on signal 11 >> (core dumped) >> >> >> which is generated by this portion of the make world: >> >> install -c -s -o root -g wheel -m 555 nvi /usr/obj/usr/src/tmp/usr/bin >> *** Signal 11 >> >> >> >> If I reboot with a kernel built on Aug 16, I can run a complete >> make world with no failures. I realize alot of changes have gone >> into the system over the last few days. If someone can give me some >> pointers on getting the information required to debug the problem, I'll >> be more than happy to dig into it. >> >> >> Thanks, >> John >> >> >> -- >> dmesg output for the machine in question: >> >> Copyright (c) 1992-1999 The FreeBSD Project. >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >> The Regents of the University of California. All rights reserved. >> FreeBSD 4.0-CURRENT #0: Thu Aug 26 13:47:34 EDT 1999 >> toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD >> Timecounter "i8254" frequency 1193182 Hz >> Timecounter "TSC" frequency 398775825 Hz >> CPU: Pentium II/Xeon/Celeron (398.78-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0x652 Stepping = 2 >> Features=0x183f9ff >> real memory = 134217728 (131072K bytes) >> avail memory = 126881792 (123908K bytes) >> Preloaded elf kernel "kernel" at 0xc0306000. >> Pentium Pro MTRR support enabled >> ccd0-3: Concatenated disk drivers >> npx0: on motherboard >> npx0: INT 16 interface >> pcib0: on motherboard >> pci0: on pcib0 >> pcib1: at device 1.0 on pci0 >> pci1: on pcib1 >> vga-pci0: irq 3 at device 0.0 on pci1 >> isab0: at device 7.0 on pci0 >> isa0: on isab0 >> ide_pci0: at device 7.1 on pci0 >> chip1: irq 11 at device 7.2 on pci0 >> chip2: at device 7.3 on pci0 >> fxp0: irq 10 at device 13.0 on pci0 >> fxp0: Ethernet address 00:a0:c9:2d:14:1b >> ahc0: irq 9 at device 14.0 on pci0 >> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs >> pcib2: at device 15.0 on pci0 >> pci2: on pcib2 >> vga-pci1: irq 3 at device 9.0 on pci2 >> ahc1: irq 11 at device 10.0 on pci2 >> ahc1: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs >> ahc2: irq 10 at device 10.1 on pci2 >> ahc2: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs >> ti0: <3Com 3c985-SX Gigabit Ethernet> irq 3 at device 11.0 on pci2 >> ti0: Ethernet address: 00:60:08:f5:c6:e5 >> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 >> fdc0: FIFO enabled, 8 bytes threshold >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 >> wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 >> wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S >> wdc1 at port 0x170-0x177 irq 15 on isa0 >> wdc1: unit 0 (atapi): , removable, dma, iordy >> wdc1: ATAPI CD-ROMs not configured >> atkbdc0: at port 0x60-0x6f on isa0 >> atkbd0: irq 1 on atkbdc0 >> psm0: irq 12 on atkbdc0 >> psm0: model Generic PS/2 mouse, device ID 0 >> 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: configured irq 3 not in bitmap of probed irqs 0 >> Waiting 5 seconds for SCSI devices to settle >> changing root device to wd0s1a >> da5 at ahc2 bus 0 target 3 lun 0 >> da5: Removable Direct Access SCSI-2 device >> da5: 20.000MB/s transfers (20.000MHz, offset 15) >> da5: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C) >> da2 at ahc0 bus 0 target 3 lun 0 >> da2: Fixed Direct Access SCSI-2 device >> da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >> da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) >> da3 at ahc0 bus 0 target 4 lun 0 >> da3: Fixed Direct Access SCSI-2 device >> da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >> da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) >> da0 at ahc0 bus 0 target 1 lun 0 >> da0: Fixed Direct Access SCSI-2 device >> da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >> da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) >> da1 at ahc0 bus 0 target 2 lun 0 >> da1: Fixed Direct Access SCSI-2 device >> da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >> da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) >> da4 at ahc0 bus 0 target 5 lun 0 >> da4: Fixed Direct Access SCSI-2 device >> da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled >> da4: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) >> cd0 at ahc2 bus 0 target 6 lun 0 >> cd0: Removable CD-ROM SCSI-2 device >> cd0: 3.300MB/s transfers >> cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed >> spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 >> size: 0, resid: 0, a_count: 12288, valid: 0x0 >> nread: 0, reqpage: 0, pindex: 14, pcount: 3 >> vm_fault: pager read error, pid 37394 (install) >> pid 37394 (install), uid 0: exited on signal 11 (core dumped) >> >> >> 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 > -- 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 Thu Aug 26 12:55:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id B9D0C15443; Thu, 26 Aug 1999 12:53:54 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id UAA93733; Thu, 26 Aug 1999 20:53:00 +0100 (BST) (envelope-from nik) Date: Thu, 26 Aug 1999 20:53:00 +0100 From: Nik Clayton To: stable@freebsd.org, current@freebsd.org Cc: jack Subject: Re: Docs blows up make release Message-ID: <19990826205300.A93397@catkin.nothing-going-on.org> References: <19990822110511.A89933@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990822110511.A89933@kilt.nothing-going-on.org>; from Nik Clayton on Sun, Aug 22, 1999 at 11:05:11AM +0100 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -stable, -current, On Sun, Aug 22, 1999 at 11:05:11AM +0100, Nik Clayton wrote: > [ cc'd to -current ] > > On Sat, Aug 21, 1999 at 07:54:51PM -0400, jack wrote: > > > > Will support for building release docs in English only be > > revived? > > > > For the immediate future, it looks like it will -- it seems as though > we don't have the man power to make the necessary changes to sysinstall > to support "installing the docs as packages", so I'm going to fix up > src/release/Makefile as necessary to cope with the new directory structure. With thanks to Jack O'Neill, this is now done. They're only in -current at the moment, but they should backport to -stable fairly easily. I'd be obliged if those if you who like to do these things grabbed a copy of -current that has r1.504 of src/release/Makefile, and tried building a release with that, and a copy of the doc/ tree that's of a similar vintage. Everything should pretty much work. Brickbats should be sent my way if it doesn't. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:56:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7D06C15CE8 for ; Thu, 26 Aug 1999 12:56:50 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA82438; Thu, 26 Aug 1999 12:55:42 -0700 (PDT) Date: Thu, 26 Aug 1999 12:56:01 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <199908261919.MAA24349@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 I am positive that I just saw a checkin from phk that initialised the initial default transfer size. On Thu, 26 Aug 1999, Matthew Dillon wrote: > :swapping on a vn device? > :the 'size' and 'resid' of 0 looks suspicious. > : > :a fix was just committed to teh vn code that may fix this if that's your > :problem. > > A fix was? When? Where? What? > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 12:59:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 1805714C97 for ; Thu, 26 Aug 1999 12:59:21 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA82642; Thu, 26 Aug 1999 12:58:38 -0700 (PDT) Date: Thu, 26 Aug 1999 12:58:58 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <513.935697140@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Aug 1999, Poul-Henning Kamp wrote: > > The size and resid of 0 is because it decides to use a sectorsize of > zero due to the si_bsize fields being empty. yes, but didn't I just see you commit a fix for that? > > In message , Jul > ian Elischer writes: > >swapping on a vn device? > >the 'size' and 'resid' of 0 looks suspicious. > > > >a fix was just committed to teh vn code that may fix this if that's your > >problem. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 13: 4:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 10CD415475 for ; Thu, 26 Aug 1999 13:02:36 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id PAA12894; Thu, 26 Aug 1999 15:59:17 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15723; Thu, 26 Aug 1999 15:58:46 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id PAA46391; Thu, 26 Aug 1999 15:58:46 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908261958.PAA46391@bb01f39.unx.sas.com> Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <513.935697140@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 26, 1999 9:52:20 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Thu, 26 Aug 1999 15:58:46 -0400 (EDT) Cc: julian@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG which would be this commit... phk 1999/08/26 07:46:11 PDT Modified files: sys/dev/ccd ccd.c Log: Initialize the dev->si_bsize fields. Submitted by: tegge Reviewed by: phk Revision Changes Path 1.53 +5 -1 src/sys/dev/ccd/ccd.c I need to figure out why my 11:30am EST cvsup didn't pick this file up. It's 44 minutes infront of cvsup... Thanks! john > > The size and resid of 0 is because it decides to use a sectorsize of > zero due to the si_bsize fields being empty. > > In message , Jul > ian Elischer writes: > >swapping on a vn device? > >the 'size' and 'resid' of 0 looks suspicious. > > > >a fix was just committed to teh vn code that may fix this if that's your > >problem. > > > > > >On Thu, 26 Aug 1999, John W. DeBoskey wrote: > > > >> Hi, > >> > >> Following up my own mail on sig 11 problems, I beleive the > >> problem is kernel related. Running a kernel with sources current > >> as of 11:30am EST, I get the following during a make world: > >> > >> spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > >> size: 0, resid: 0, a_count: 12288, valid: 0x0 > >> nread: 0, reqpage: 0, pindex: 14, pcount: 3 > >> vm_fault: pager read error, pid 37394 (install) > >> Aug 26 14:08:44 FreeBSD /kernel: pid 37394 (install), uid 0: exited on signal 11 > >> (core dumped) > >> > >> > >> which is generated by this portion of the make world: > >> > >> install -c -s -o root -g wheel -m 555 nvi /usr/obj/usr/src/tmp/usr/bin > >> *** Signal 11 > >> > >> > >> > >> If I reboot with a kernel built on Aug 16, I can run a complete > >> make world with no failures. I realize alot of changes have gone > >> into the system over the last few days. If someone can give me some > >> pointers on getting the information required to debug the problem, I'll > >> be more than happy to dig into it. > >> > >> > >> Thanks, > >> John > >> > >> > >> -- > >> dmesg output for the machine in question: > >> > >> Copyright (c) 1992-1999 The FreeBSD Project. > >> Copyright (c) 1982, 1986, 1989, 1991, 1993 > >> The Regents of the University of California. All rights reserved. > >> FreeBSD 4.0-CURRENT #0: Thu Aug 26 13:47:34 EDT 1999 > >> toor@FreeBSD.unx.sas.com:/usr/src/sys/compile/FreeBSD > >> Timecounter "i8254" frequency 1193182 Hz > >> Timecounter "TSC" frequency 398775825 Hz > >> CPU: Pentium II/Xeon/Celeron (398.78-MHz 686-class CPU) > >> Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > >> Features=0x183f9ff > >> real memory = 134217728 (131072K bytes) > >> avail memory = 126881792 (123908K bytes) > >> Preloaded elf kernel "kernel" at 0xc0306000. > >> Pentium Pro MTRR support enabled > >> ccd0-3: Concatenated disk drivers > >> npx0: on motherboard > >> npx0: INT 16 interface > >> pcib0: on motherboard > >> pci0: on pcib0 > >> pcib1: at device 1.0 on pci0 > >> pci1: on pcib1 > >> vga-pci0: irq 3 at device 0.0 on pci1 > >> isab0: at device 7.0 on pci0 > >> isa0: on isab0 > >> ide_pci0: at device 7.1 on pci0 > >> chip1: irq 11 at device 7.2 on pci0 > >> chip2: at device 7.3 on pci0 > >> fxp0: irq 10 at device 13.0 on pci0 > >> fxp0: Ethernet address 00:a0:c9:2d:14:1b > >> ahc0: irq 9 at device 14.0 on pci0 > >> ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > >> pcib2: at device 15.0 on pci0 > >> pci2: on pcib2 > >> vga-pci1: irq 3 at device 9.0 on pci2 > >> ahc1: irq 11 at device 10.0 on pci2 > >> ahc1: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs > >> ahc2: irq 10 at device 10.1 on pci2 > >> ahc2: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs > >> ti0: <3Com 3c985-SX Gigabit Ethernet> irq 3 at device 11.0 on pci2 > >> ti0: Ethernet address: 00:60:08:f5:c6:e5 > >> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > >> fdc0: FIFO enabled, 8 bytes threshold > >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > >> wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa0 > >> wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 > >> wd0: 6149MB (12594960 sectors), 12495 cyls, 16 heads, 63 S/T, 512 B/S > >> wdc1 at port 0x170-0x177 irq 15 on isa0 > >> wdc1: unit 0 (atapi): , removable, dma, iordy > >> wdc1: ATAPI CD-ROMs not configured > >> atkbdc0: at port 0x60-0x6f on isa0 > >> atkbd0: irq 1 on atkbdc0 > >> psm0: irq 12 on atkbdc0 > >> psm0: model Generic PS/2 mouse, device ID 0 > >> 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: configured irq 3 not in bitmap of probed irqs 0 > >> Waiting 5 seconds for SCSI devices to settle > >> changing root device to wd0s1a > >> da5 at ahc2 bus 0 target 3 lun 0 > >> da5: Removable Direct Access SCSI-2 device > >> da5: 20.000MB/s transfers (20.000MHz, offset 15) > >> da5: 1911MB (3915600 512 byte sectors: 255H 63S/T 243C) > >> da2 at ahc0 bus 0 target 3 lun 0 > >> da2: Fixed Direct Access SCSI-2 device > >> da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > >> da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > >> da3 at ahc0 bus 0 target 4 lun 0 > >> da3: Fixed Direct Access SCSI-2 device > >> da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > >> da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) > >> da0 at ahc0 bus 0 target 1 lun 0 > >> da0: Fixed Direct Access SCSI-2 device > >> da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > >> da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > >> da1 at ahc0 bus 0 target 2 lun 0 > >> da1: Fixed Direct Access SCSI-2 device > >> da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > >> da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > >> da4 at ahc0 bus 0 target 5 lun 0 > >> da4: Fixed Direct Access SCSI-2 device > >> da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > >> da4: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > >> cd0 at ahc2 bus 0 target 6 lun 0 > >> cd0: Removable CD-ROM SCSI-2 device > >> cd0: 3.300MB/s transfers > >> cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed > >> spec_getpages: I/O read failure: (error code=0) bp 0xc3700ec8 vp 0xc92ce000 > >> size: 0, resid: 0, a_count: 12288, valid: 0x0 > >> nread: 0, reqpage: 0, pindex: 14, pcount: 3 > >> vm_fault: pager read error, pid 37394 (install) > >> pid 37394 (install), uid 0: exited on signal 11 (core dumped) > >> > >> > >> 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 > > > > -- > 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 Thu Aug 26 13: 9:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BF47A14C11; Thu, 26 Aug 1999 13:09:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA83447; Thu, 26 Aug 1999 13:07:28 -0700 (PDT) Date: Thu, 26 Aug 1999 13:07:47 -0700 (PDT) From: Julian Elischer To: "John W. DeBoskey" Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG, dillon@freebsd.org Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <199908261958.PAA46391@bb01f39.unx.sas.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 Ah my mistake, it was ccd. I remembered vn. I guess vinum, vn, and ccd need all have the correct bisize code...... On Thu, 26 Aug 1999, John W. DeBoskey wrote: > which would be this commit... > > phk 1999/08/26 07:46:11 PDT > > Modified files: > sys/dev/ccd ccd.c > Log: > Initialize the dev->si_bsize fields. > > Submitted by: tegge > Reviewed by: phk > > Revision Changes Path > 1.53 +5 -1 src/sys/dev/ccd/ccd.c > > > I need to figure out why my 11:30am EST cvsup didn't pick > this file up. It's 44 minutes infront of cvsup... > > Thanks! > john > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 13:15: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E2D514C38 for ; Thu, 26 Aug 1999 13:14:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA24637; Thu, 26 Aug 1999 13:13:20 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Aug 1999 13:13:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199908262013.NAA24637@apollo.backplane.com> To: "John W. DeBoskey" Cc: phk@critter.freebsd.dk (Poul-Henning Kamp), julian@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) References: <199908261958.PAA46391@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That fixes a problem with ccd, but not the one causing John's failures. You will note that with John's failure's the I/O is properly page-aligned. The fix to ccd deals with a misalignment problem. But I believe I have found the problem... it is a bug in vm/swap_pager.c that occurs when you have more then one swap partition. The code is improperly crossing a physical disk device boundry and vm/vm_swap.c is returning a failure because of that. For example, if you attempt to read 8K from a swap-backed VN device and 4K of it is in one swap partition and the other 4K is in another, vm/swap_pager.c is not properly breaking up the transaction. I'll have a fix in a moment. -Matt :which would be this commit... : :phk 1999/08/26 07:46:11 PDT : : Modified files: : sys/dev/ccd ccd.c : Log: : Initialize the dev->si_bsize fields. : : Submitted by: tegge : Reviewed by: phk : : Revision Changes Path : 1.53 +5 -1 src/sys/dev/ccd/ccd.c : : : I need to figure out why my 11:30am EST cvsup didn't pick :this file up. It's 44 minutes infront of cvsup... : :Thanks! :john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 13:37:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 941EC15404 for ; Thu, 26 Aug 1999 13:37:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA24744; Thu, 26 Aug 1999 13:34:23 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Aug 1999 13:34:23 -0700 (PDT) From: Matthew Dillon Message-Id: <199908262034.NAA24744@apollo.backplane.com> To: Matthew Dillon Cc: "John W. DeBoskey" , phk@critter.freebsd.dk (Poul-Henning Kamp), julian@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: tentative fix (was Re: -current kernel problems (spec_getpages & vm_fault)) References: <199908261958.PAA46391@bb01f39.unx.sas.com> <199908262013.NAA24637@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The first part of this patch is not yet part of my multipatch at http://www.backplane.com/FreeBSD4/ This is a tentative fix, but I believe it to be correct. Until yesterday I was testing swap-backed VN with only one swap partition, otherwise this would have been found and fixed long ago :-( I'm doing a buildworld stress test now to make sure it's been fixed. -Matt Index: swap_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v retrieving revision 1.124 diff -u -r1.124 swap_pager.c --- swap_pager.c 1999/08/23 23:55:03 1.124 +++ swap_pager.c 1999/08/26 20:20:09 @@ -830,13 +830,19 @@ splx(s); /* - * Do we have to flush our current collection? + * Do we have to flush our current collection? Yes if: + * + * - no swap block at this index + * - swap block is not contiguous + * - we cross a physical disk boundry in the + * stripe. */ if ( nbp && ( (blk & SWAPBLK_NONE) || - nbp->b_blkno + btoc(nbp->b_bcount) != blk + nbp->b_blkno + btoc(nbp->b_bcount) != blk || + ((nbp->b_blkno ^ blk) & dmmax_mask) ) ) { ++cnt.v_swapin; @@ -857,6 +863,7 @@ if (nbp == NULL) { nbp = getchainbuf(bp, swapdev_vp, B_READ|B_ASYNC); nbp->b_blkno = blk; + nbp->b_bcount = 0; nbp->b_data = data; } nbp->b_bcount += PAGE_SIZE; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 13:37:34 1999 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 3A2DF15EA7 for ; Thu, 26 Aug 1999 13:37:23 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA00848; Thu, 26 Aug 1999 22:33:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Thu, 26 Aug 1999 12:58:58 PDT." Date: Thu, 26 Aug 1999 22:33:53 +0200 Message-ID: <846.935699633@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Jul ian Elischer writes: > > >On Thu, 26 Aug 1999, Poul-Henning Kamp wrote: > >> >> The size and resid of 0 is because it decides to use a sectorsize of >> zero due to the si_bsize fields being empty. > >yes, but didn't I just see you commit a fix for that? To ccd yes. mfs was fixed before that (yesterday). >> In message , Jul >> ian Elischer writes: >> >swapping on a vn device? >> >the 'size' and 'resid' of 0 looks suspicious. >> > >> >a fix was just committed to teh vn code that may fix this if that's your >> >problem. >> > >> > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 13:38:20 1999 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 537E715C96 for ; Thu, 26 Aug 1999 13:38:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA00874; Thu, 26 Aug 1999 22:35:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Thu, 26 Aug 1999 13:13:20 PDT." <199908262013.NAA24637@apollo.backplane.com> Date: Thu, 26 Aug 1999 22:35:27 +0200 Message-ID: <872.935699727@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908262013.NAA24637@apollo.backplane.com>, Matthew Dillon writes: > That fixes a problem with ccd, but not the one causing John's failures. > > You will note that with John's failure's the I/O is properly page-aligned. > The fix to ccd deals with a misalignment problem. No it doesn't. johns failure is clearly the si_bsize* problem, the tell-tale sign is all the zeros in there. What John didn't tell us is if he uses vn, ccd or vinum (or something else!) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 14: 2:40 1999 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 A896014F36 for ; Thu, 26 Aug 1999 14:02:34 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA11305; Thu, 26 Aug 1999 17:01:52 -0400 (EDT) Message-ID: <19990826170152.A8492@netmonger.net> Date: Thu, 26 Aug 1999 17:01:52 -0400 From: Christopher Masto To: Poul-Henning Kamp , Matthew Dillon Cc: "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Mail-Followup-To: Poul-Henning Kamp , Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG References: <199908262013.NAA24637@apollo.backplane.com> <872.935699727@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <872.935699727@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Aug 26, 1999 at 10:35:27PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 26, 1999 at 10:35:27PM +0200, Poul-Henning Kamp wrote: > In message <199908262013.NAA24637@apollo.backplane.com>, Matthew Dillon writes: > > That fixes a problem with ccd, but not the one causing John's failures. > > > > You will note that with John's failure's the I/O is properly page-aligned. > > The fix to ccd deals with a misalignment problem. > > No it doesn't. johns failure is clearly the si_bsize* problem, the > tell-tale sign is all the zeros in there. What John didn't tell > us is if he uses vn, ccd or vinum (or something else!) Well, I just had much the same blowup with source from last night and I'm using vinum, (and not vn or ccd). Recompiling now to see if it's still there. -- 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 Thu Aug 26 14: 7:59 1999 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 4154F15C96; Thu, 26 Aug 1999 14:07:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA01163; Thu, 26 Aug 1999 23:04:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Christopher Masto Cc: grog@freebsd.org Cc: Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@freebsd.org Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Thu, 26 Aug 1999 17:01:52 EDT." <19990826170152.A8492@netmonger.net> Date: Thu, 26 Aug 1999 23:04:44 +0200 Message-ID: <1161.935701484@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990826170152.A8492@netmonger.net>, Christopher Masto writes: >On Thu, Aug 26, 1999 at 10:35:27PM +0200, Poul-Henning Kamp wrote: >> In message <199908262013.NAA24637@apollo.backplane.com>, Matthew Dillon writes: >> > That fixes a problem with ccd, but not the one causing John's failures. >> > >> > You will note that with John's failure's the I/O is properly page-aligned. >> > The fix to ccd deals with a misalignment problem. >> >> No it doesn't. johns failure is clearly the si_bsize* problem, the >> tell-tale sign is all the zeros in there. What John didn't tell >> us is if he uses vn, ccd or vinum (or something else!) > >Well, I just had much the same blowup with source from last night >and I'm using vinum, (and not vn or ccd). > >Recompiling now to see if it's still there. Ok, I havn't touched vinum (grog generally want to do this himself), the fix is probably something like this: Index: vinum.c =================================================================== RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v retrieving revision 1.29 diff -u -r1.29 vinum.c --- vinum.c 1999/08/24 02:18:55 1.29 +++ vinum.c 1999/08/26 21:04:03 @@ -271,6 +271,9 @@ int devminor; /* minor number */ devminor = minor(dev); + dev->si_bsize_phys = DEV_BSIZE; + dev->si_bsize_best = BLKDEV_IOSIZE; + dev->si_bsize_max = MAXBSIZE; error = 0; /* First, decide what we're looking at */ switch (DEVTYPE(dev)) { -- 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 Thu Aug 26 14:20: 0 1999 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 11B3D14FBB; Thu, 26 Aug 1999 14:19:55 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA12181; Thu, 26 Aug 1999 17:18:06 -0400 (EDT) Message-ID: <19990826171806.B8492@netmonger.net> Date: Thu, 26 Aug 1999 17:18:06 -0400 From: Christopher Masto To: Poul-Henning Kamp Cc: grog@FreeBSD.ORG, Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Mail-Followup-To: Poul-Henning Kamp , grog@FreeBSD.ORG, Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG References: <19990826170152.A8492@netmonger.net> <1161.935701484@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <1161.935701484@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Aug 26, 1999 at 11:04:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 26, 1999 at 11:04:44PM +0200, Poul-Henning Kamp wrote: > >Well, I just had much the same blowup with source from last night > >and I'm using vinum, (and not vn or ccd). > > > >Recompiling now to see if it's still there. > > Ok, I havn't touched vinum (grog generally want to do this himself), I will try that fix next. FYI, here's what it looked like: (I don't know what's with the garbage, maybe it was my serial console) [everything apparently normal until..] Doing initial network setup: hostname. lgo0: flags=8049 mt:u 16384 inet 1 27.0.0.1 netmaskI 0xff000000 /O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 60512, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 15 Flushed all rules. 00100 allow ip from any to any via lo0 00200 deny ip from asny to 127.0.0.0/p8 65000 allow iep from any to ancy Firewall rule_s loaded, startigng divert daemones:. add net deftault: gateway 16p7.206.208.254 Aadditional routingg options: tcp eextensions=NO TCPs keepalive=YES.: routing daemons :. Mounting NFSI file systems. /O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 5672, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 2 /etc/rc: chflags: I/O error /etc/rc: chown: sI/O error padditional daemoens:c_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 24352, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 6 syslogd/etc/rc: syslogds: I/O error p. ec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 8192, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 2 Doing additionals network setup: pportmape/etc/rc: /usr/sbcin/portmap: I/O _error getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 8192, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 2 . Starting finasl network daemonps:. e/etc/rc: kvm_mkdcb: I/O error _getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 4132, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 2 /etc/rc: dev_mkdb: I/O error spec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 49152, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 12 /etc/rc: /usr/bin/objformat: I/O error setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout starting standarsd daemons:p inetdec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 24576, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 6 /etc/rc: inetd: sI/O error p cronec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 24576, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 6 /etc/rc: cron: Is/O error p sendmailec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 57344, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 14 /etc/rc: /usr/sbsin/sendmail: I/Op error e. c_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 4088, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 1 /etc/rc: uname: I/O error Local package initialization:spec_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a86c0 size: 0, resid: 0, a_count: 75, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 1 /etc/rc: /usr/loscal/etc/rc.d/50.pm3.sh: I/O errore c_getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a86c0 size: 0, resid: 0, a_count: 81, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 1 /etc/rc: /usr/loscal/etc/rc.d/sshpd.sh: I/O errore c. _getpages: I/O read failure: (error code=0) bp 0xc6321358 vp 0xcc6a9500 size: 0, resid: 0, a_count: 4248, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 2 /etc/rc: mktemp: I/O error Thu Aug 26 16:14:22 EDT 1999cu: Got hangup signal I'll let you know if the patch to vinum cures 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 Thu Aug 26 14:23:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3A74F14BF2 for ; Thu, 26 Aug 1999 14:23:09 -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.1) with ESMTP id OAA08941; Thu, 26 Aug 1999 14:22:39 -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 OAA05646; Thu, 26 Aug 1999 14:22:38 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Thu, 26 Aug 1999 14:22:38 -0700 (PDT) Message-Id: <199908262122.OAA05646@vashon.polstra.com> To: jwd@unx.sas.com Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <199908261958.PAA46391@bb01f39.unx.sas.com> References: <199908261958.PAA46391@bb01f39.unx.sas.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199908261958.PAA46391@bb01f39.unx.sas.com>, John W. DeBoskey wrote: > > I need to figure out why my 11:30am EST cvsup didn't pick > this file up. It's 44 minutes infront of cvsup... Most mirror sites update themselves hourly from cvsup-master, which updates itself every 6 minutes from freefall. If the file still isn't there after 1 hour 6 minutes, then please send me the details. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 14:42:44 1999 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 B282E14DB8; Thu, 26 Aug 1999 14:42:40 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA13307; Thu, 26 Aug 1999 17:41:28 -0400 (EDT) Message-ID: <19990826174127.C8492@netmonger.net> Date: Thu, 26 Aug 1999 17:41:27 -0400 From: Christopher Masto To: Poul-Henning Kamp Cc: grog@FreeBSD.ORG, Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Mail-Followup-To: Poul-Henning Kamp , grog@FreeBSD.ORG, Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG References: <19990826170152.A8492@netmonger.net> <1161.935701484@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <1161.935701484@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Aug 26, 1999 at 11:04:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 26, 1999 at 11:04:44PM +0200, Poul-Henning Kamp wrote: > Ok, I havn't touched vinum (grog generally want to do this himself), > the fix is probably something like this: > > Index: vinum.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v > retrieving revision 1.29 > diff -u -r1.29 vinum.c > --- vinum.c 1999/08/24 02:18:55 1.29 > +++ vinum.c 1999/08/26 21:04:03 > @@ -271,6 +271,9 @@ > int devminor; /* minor number */ > > devminor = minor(dev); > + dev->si_bsize_phys = DEV_BSIZE; > + dev->si_bsize_best = BLKDEV_IOSIZE; > + dev->si_bsize_max = MAXBSIZE; Bingo! Thank you. -- 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 Thu Aug 26 14:45:43 1999 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 C627C15CE3; Thu, 26 Aug 1999 14:45:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA01675; Thu, 26 Aug 1999 23:45:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Christopher Masto Cc: grog@FreeBSD.ORG, Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Thu, 26 Aug 1999 17:41:27 EDT." <19990826174127.C8492@netmonger.net> Date: Thu, 26 Aug 1999 23:45:01 +0200 Message-ID: <1673.935703901@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990826174127.C8492@netmonger.net>, Christopher Masto writes: >> Index: vinum.c >> =================================================================== >> RCS file: /home/ncvs/src/sys/dev/vinum/vinum.c,v >> retrieving revision 1.29 >> diff -u -r1.29 vinum.c >> --- vinum.c 1999/08/24 02:18:55 1.29 >> +++ vinum.c 1999/08/26 21:04:03 >> @@ -271,6 +271,9 @@ >> int devminor; /* minor number */ >> >> devminor = minor(dev); >> + dev->si_bsize_phys = DEV_BSIZE; >> + dev->si_bsize_best = BLKDEV_IOSIZE; >> + dev->si_bsize_max = MAXBSIZE; > >Bingo! Thank you. Cool, I expect grog will commit it soon. -- 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 Thu Aug 26 15:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CFE4E1534A for ; Thu, 26 Aug 1999 15:29: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 QAA86408; Thu, 26 Aug 1999 16:27:43 -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 QAA68494; Thu, 26 Aug 1999 16:28:55 -0600 (MDT) Message-Id: <199908262228.QAA68494@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: "The Matrix" screensaver, v.0.2 Cc: Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Wed, 25 Aug 1999 09:30:12 PDT." <15454.935598612@localhost> References: <15454.935598612@localhost> Date: Thu, 26 Aug 1999 16:28:55 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <15454.935598612@localhost> "Jordan K. Hubbard" writes: : I think people are being almost clinically paranoid here. Hasbro and : folks got upset over TRADEMARK infringement, e.g. from using a name : they had trademarked. I rather doubt that Warner Bros. have managed : to trademark the name "matrix" since it's already a common english : word. "Boggle" and "Tetris" don't fall into that category. Hasbro has sued the owners of Clue.com (Clue Computing) for trademark infringement. clue is a word from the dictionary... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 16:26:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C133D1517A; Thu, 26 Aug 1999 16:26:08 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA25436; Thu, 26 Aug 1999 16:25:14 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Aug 1999 16:25:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199908262325.QAA25436@apollo.backplane.com> To: Poul-Henning Kamp Cc: Christopher Masto , grog@FreeBSD.ORG, "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) References: <1673.935703901@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>> int devminor; /* minor number */ :>> :>> devminor = minor(dev); :>> + dev->si_bsize_phys = DEV_BSIZE; :>> + dev->si_bsize_best = BLKDEV_IOSIZE; :>> + dev->si_bsize_max = MAXBSIZE; :> :>Bingo! Thank you. : :Cool, I expect grog will commit it soon. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." The patch for ccd is not quite right. Here is the patch from my big fat patch at http://www.backplane.com/FreeBSD4/ The problem is that you cannot simply set the physical sector size to DEV_BSIZE if the underlying device has a larger sector size. If you do, specfs's blocksize alignment (another fix in my big fat patch) will be incorrect and result in an I/O error on the physical media. For example, swap-backed VN devices have a sector size of one page, i.e. 4K. -Matt Matthew Dillon Index: ccd.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ccd/ccd.c,v retrieving revision 1.53 diff -u -r1.53 ccd.c --- ccd.c 1999/08/26 14:46:10 1.53 +++ ccd.c 1999/08/26 23:22:43 @@ -1417,6 +1417,12 @@ lp->d_ncylinders = ccg->ccg_ncylinders; lp->d_secpercyl = lp->d_ntracks * lp->d_nsectors; + dev->si_bsize_phys = lp->d_secsize; + dev->si_bsize_best = BLKDEV_IOSIZE; + dev->si_bsize_max = MAXBSIZE; + if (dev->si_bsize_best < lp->d_secsize) + dev->si_bsize_best = lp->d_secsize; + strncpy(lp->d_typename, "ccd", sizeof(lp->d_typename)); lp->d_type = DTYPE_CCD; strncpy(lp->d_packname, "fictitious", sizeof(lp->d_packname)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 16:28:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by hub.freebsd.org (Postfix) with ESMTP id E273214EB1; Thu, 26 Aug 1999 16:28:48 -0700 (PDT) (envelope-from Girish_Pillai@bmc.com) Received: from ec01-hou.bmc.com (ec01-hou.bmc.com [172.17.0.150]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id SAA03080; Thu, 26 Aug 1999 18:27:59 -0500 (CDT) Received: by ec01-hou.bmc.com with Internet Mail Service (5.5.2448.0) id ; Thu, 26 Aug 1999 18:27:58 -0500 Message-ID: From: "Pillai, Girish" To: "'Matthew Dillon'" , Poul-Henning Kamp Cc: Christopher Masto , grog@FreeBSD.ORG, "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: RE: -current kernel problems (spec_getpages & vm_fault) Date: Thu, 26 Aug 1999 18:27:14 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current -----Original Message----- From: Matthew Dillon [mailto:dillon@apollo.backplane.com] Sent: Thursday, August 26, 1999 6:25 PM To: Poul-Henning Kamp Cc: Christopher Masto; grog@FreeBSD.ORG; John W. DeBoskey; julian@whistle.com; freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) :>> int devminor; /* minor number */ :>> :>> devminor = minor(dev); :>> + dev->si_bsize_phys = DEV_BSIZE; :>> + dev->si_bsize_best = BLKDEV_IOSIZE; :>> + dev->si_bsize_max = MAXBSIZE; :> :>Bingo! Thank you. : :Cool, I expect grog will commit it soon. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." The patch for ccd is not quite right. Here is the patch from my big fat patch at http://www.backplane.com/FreeBSD4/ The problem is that you cannot simply set the physical sector size to DEV_BSIZE if the underlying device has a larger sector size. If you do, specfs's blocksize alignment (another fix in my big fat patch) will be incorrect and result in an I/O error on the physical media. For example, swap-backed VN devices have a sector size of one page, i.e. 4K. -Matt Matthew Dillon Index: ccd.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ccd/ccd.c,v retrieving revision 1.53 diff -u -r1.53 ccd.c --- ccd.c 1999/08/26 14:46:10 1.53 +++ ccd.c 1999/08/26 23:22:43 @@ -1417,6 +1417,12 @@ lp->d_ncylinders = ccg->ccg_ncylinders; lp->d_secpercyl = lp->d_ntracks * lp->d_nsectors; + dev->si_bsize_phys = lp->d_secsize; + dev->si_bsize_best = BLKDEV_IOSIZE; + dev->si_bsize_max = MAXBSIZE; + if (dev->si_bsize_best < lp->d_secsize) + dev->si_bsize_best = lp->d_secsize; + strncpy(lp->d_typename, "ccd", sizeof(lp->d_typename)); lp->d_type = DTYPE_CCD; strncpy(lp->d_packname, "fictitious", sizeof(lp->d_packname)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 16:35:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0EF23156AB for ; Thu, 26 Aug 1999 16:35:15 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05647; Thu, 26 Aug 1999 16:34:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Warner Losh Cc: "Jordan K. Hubbard" , Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Thu, 26 Aug 1999 16:28:55 MDT." <199908262228.QAA68494@harmony.village.org> Date: Thu, 26 Aug 1999 16:34:20 -0700 Message-ID: <5644.935710460@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seriously doubt they'll win this lawsuit. You can sue someone for anything and everything, including having a hair color which displeases you, of course, but whether you actually win the lawsuit or have it thrown out is a different matter. - Jordan > In message <15454.935598612@localhost> "Jordan K. Hubbard" writes: > : I think people are being almost clinically paranoid here. Hasbro and > : folks got upset over TRADEMARK infringement, e.g. from using a name > : they had trademarked. I rather doubt that Warner Bros. have managed > : to trademark the name "matrix" since it's already a common english > : word. "Boggle" and "Tetris" don't fall into that category. > > Hasbro has sued the owners of Clue.com (Clue Computing) for > trademark infringement. clue is a word from the dictionary... > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 16:48:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A2CB15980 for ; Thu, 26 Aug 1999 16:48:23 -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 RAA86796; Thu, 26 Aug 1999 17:48:20 -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 RAA69385; Thu, 26 Aug 1999 17:49:39 -0600 (MDT) Message-Id: <199908262349.RAA69385@harmony.village.org> To: "Jordan K. Hubbard" Subject: Re: "The Matrix" screensaver, v.0.2 Cc: Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 26 Aug 1999 16:34:20 PDT." <5644.935710460@localhost> References: <5644.935710460@localhost> Date: Thu, 26 Aug 1999 17:49:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5644.935710460@localhost> "Jordan K. Hubbard" writes: : I seriously doubt they'll win this lawsuit. You can sue someone for : anything and everything, including having a hair color which : displeases you, of course, but whether you actually win the lawsuit or : have it thrown out is a different matter. It has gone on for the last 4 years. They have gone to trial and the judge will give a ruling when he gets around to it... It has cost my friend a whole pile of money to defend it, which might be a problem for FreeBSD... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 17:29: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E0EF2154C5 for ; Thu, 26 Aug 1999 17:28:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA26015; Thu, 26 Aug 1999 17:28:58 -0700 (PDT) (envelope-from dillon) Date: Thu, 26 Aug 1999 17:28:58 -0700 (PDT) From: Matthew Dillon Message-Id: <199908270028.RAA26015@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: multipatch #5 available (includes VN & CCD fixes) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've synced my source tree and updated my big-fat patch to include fixes to the VN device and CCD device as well as all the other stuff it already contains. http://www.backplane.com/FreeBSD4/ -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 18:24:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 0955614BE4 for ; Thu, 26 Aug 1999 18:24:21 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA10300; Fri, 27 Aug 1999 10:53:11 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA03213; Fri, 27 Aug 1999 10:53:09 +0930 (CST) Date: Fri, 27 Aug 1999 10:53:09 +0930 From: Greg Lehey To: Poul-Henning Kamp Cc: Matthew Dillon , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Message-ID: <19990827105309.E483@freebie.lemis.com> References: <199908262013.NAA24637@apollo.backplane.com> <872.935699727@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <872.935699727@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Aug 26, 1999 at 10:35:27PM +0200 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 Thursday, 26 August 1999 at 22:35:27 +0200, Poul-Henning Kamp wrote: > In message <199908262013.NAA24637@apollo.backplane.com>, Matthew Dillon writes: >> That fixes a problem with ccd, but not the one causing John's failures. >> >> You will note that with John's failure's the I/O is properly page-aligned. >> The fix to ccd deals with a misalignment problem. > > No it doesn't. johns failure is clearly the si_bsize* problem, the > tell-tale sign is all the zeros in there. What John didn't tell > us is if he uses vn, ccd or vinum (or something else!) Indirectly he told us that he's not using Vinum. If you're running Vinum, you'll see something like this in the dmesg output: ... da4: Fixed Direct Access SCSI-CCS device da4: 3.300MB/s transfers da4: 573MB (1173930 512 byte sectors: 64H 32S/T 573C) vinum: loaded vinum: reading configuration from /dev/da5e vinum: updating configuration from /dev/da3h vinum: updating configuration from /dev/da4h vinum: updating configuration from /dev/da1s1h vinum: updating configuration from /dev/da2h Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 18:46:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 0745E14F64 for ; Thu, 26 Aug 1999 18:46:53 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) id VAA14598; Thu, 26 Aug 1999 21:45:27 -0400 (EDT) (envelope-from sjr) Message-Id: <199908270145.VAA14598@cc158233-a.catv1.md.home.com> Date: Thu, 26 Aug 1999 21:45:27 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: Existance of /var/backups for periodic/daily To: freebsd@gndrsh.dnsmgr.net Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199908170349.UAA10347@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Aug, Rodney W. Grimes wrote: >> The 200-220 periodic files under daily expect that the directory >> /var/backups exist when they run to back up various files. If you >> delete this directory, the "cp" commands will error. >> >> There seems to be two ways to fix the files. >> >> 1. Add a "if [ ! -d $bak ] ; then exit fi" to the top >> of the files, or >> >> 2. Add a "mkdir -p $bak" to the top. >> >> Do others consider this an error, and if so which is the preferred >> fix? > I consider it an error, but prefer neither fix, here is something more > defensive and verbose in light of failure modes: > > if [ ! -e $bak ] ; then > echo "${0}: $bak missing, creating"; > mkdir -p $bak; > else > if [ ! -d $bak ] ; then > echo "${0}: $bak exists and is not a directory, aborting"; > exit 1; > fi > fi Another take on this is to *not* do the backups if the directory doesn't exist... I'll probably send-pr something like the above however.... -- Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 18:48: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (Postfix) with ESMTP id 75F5F15434; Thu, 26 Aug 1999 18:47:58 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id UAA16310; Thu, 26 Aug 1999 20:47:48 -0500 (CDT) Received: from sji-ca5-176.ix.netcom.com(209.109.234.176) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma016293; Thu Aug 26 20:47:22 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id SAA28006; Thu, 26 Aug 1999 18:46:39 -0700 (PDT) To: "Jordan K. Hubbard" Cc: Nik Clayton , jack , current@freebsd.org, doc@freebsd.org Subject: Re: Docs blows up make release References: <16783.935616425@localhost> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 26 Aug 1999 18:46:38 -0700 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 25 Aug 1999 14:27:05 -0700" Message-ID: Lines: 45 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Jordan K. Hubbard" * > This makes the ports tree have a dependency on the doc tree. I don't think * > this dependency should be there. It's bad enough that the src/ tree * > depends on doc/ (and the reason I want the documentation available as * > packages is to remove this dependency), having ports depend on the doc tree * > as well just means that when things go out of sync in doc for a while I get * > both you and Satoshi complaining at me, instead of just you :-) * * Erm, I think the ports tree is pretty darn loose about "dependencies" * since they're easily updated. Consider, for example, the fact that * some ports are dependent on the organization of binary tarballs over * at Netscape, or depend on WordPerfect's linux distribution RPM. Those * are some pretty heavy deps, and depending on something in our own doc * tree is certainly no worse. :) Yes. It shouldn't be hard to keep them synced, just like all the other ports that require the src tree to be around. Another advantage of having them in the ports tree is the build checking done at regular intervals. All the japanese/handbook stuff that's going on right now, these are the problems of the textproc/docbook* ports (missing files from PLIST, missing dependencies). People installing these from packages will see the exact same problem when they try to build the handbook (with or without the japanese/handbook port). * > Putting the package building rules in the doc/ Makefiles also (and this * > is just my personal opinion) makes it easier for people to see how the * > documentation packages are built. The ports Makefile structure is a * > marvel, but it contains a lot of code that's not necessary for building * > documentation packages (the "automagically add man pages to the PLIST * > i" code, for example) that makes it more difficult for the interested * > learner to browse and understand what's going on. * * Now this is a point which is more germin. So, you figure on making a * similar sort of "package" target under doc? I guess it really doesn't * matter where these things live, as long as it's still automated.. The chief concern I have is that this might result in yet another place you (Jordan) have to pick up stuff from before the release. Having these as ports will at least put them on the normal distribution channel along with all the other packages. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 21:58: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail-gw3.pacbell.net (mail-gw3.pacbell.net [206.13.28.55]) by hub.freebsd.org (Postfix) with ESMTP id 3B1D815271 for ; Thu, 26 Aug 1999 21:58:03 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org (ppp-207-214-149-74.snrf01.pacbell.net [207.214.149.74]) by mail-gw3.pacbell.net (8.9.3/8.9.3) with ESMTP id VAA27117; Thu, 26 Aug 1999 21:57:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 2D26E9181C; Thu, 26 Aug 1999 21:57:15 -0700 (PDT) Date: Thu, 26 Aug 1999 21:57:15 -0700 (PDT) From: Alex Zepeda To: "Rodney W. Grimes" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? In-Reply-To: <199908261000.DAA47384@gndrsh.dnsmgr.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 Thu, 26 Aug 1999, Rodney W. Grimes wrote: > You can look at thier products on www.soltek.com.tw, we are an authorized > distributor who stocks both the SL54U5 (was stocking SL54U1, but they > are in very short supply due to cache chip shortage) and SL56D1. Both > are sub $80.00 boards, both run FreeBSD just dandy. Well, right now I'm happy with my BX based board. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 23: 5: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id B4F56152D3 for ; Thu, 26 Aug 1999 23:04:56 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id CAA08488; Fri, 27 Aug 1999 02:04:38 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14226; Fri, 27 Aug 1999 02:04:07 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id CAA51292; Fri, 27 Aug 1999 02:04:07 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908270604.CAA51292@bb01f39.unx.sas.com> Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-Reply-To: <19990827105309.E483@freebie.lemis.com> from Greg Lehey at "Aug 27, 1999 10:53: 9 am" To: grog@lemis.com (Greg Lehey) Date: Fri, 27 Aug 1999 02:04:07 -0400 (EDT) Cc: phk@critter.freebsd.dk, dillon@apollo.backplane.com, jwd@unx.sas.com, julian@whistle.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Sorry for taking so long to reply. I have an isdn line to my office which has been acting up lately (or should I say acting down?). Anyways, yes, I am using a ccd. I also have a machine with a dpt raid4 controller that I probably need to check to see if it still works.... My setup is below: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 254063 35349 198389 15% / /dev/wd0s1g 3054702 1218081 1592245 43% /mirror /dev/wd0s1f 2032623 981267 888747 52% /usr /dev/wd0s1e 508143 251009 216483 54% /var mfs:60 89287 6361 75784 8% /tmp procfs 4 4 0 100% /proc /dev/ccd0a 3277830 2 3015602 0% /usr/obj /dev/ccd0b 5384181 1100 4952347 0% /snap /dev/ccd1c 17235719 6912829 8944033 44% /pub /dev/da4c 2032500 355979 1513921 19% /cdwork bbsrv01:/afs 9000000 0 9000000 0% /afs pid209@FreeBSD:/u 0 0 0 100% /u pid209@FreeBSD:/nfs 0 0 0 100% /nfs I have 2 ccd setups, one which is the entire array, and one which is partitioned. With the new kernel from earlier today, they all seem to be behaving much better now. Thanks folks! John > On Thursday, 26 August 1999 at 22:35:27 +0200, Poul-Henning Kamp wrote: > > In message <199908262013.NAA24637@apollo.backplane.com>, Matthew Dillon writes: > >> That fixes a problem with ccd, but not the one causing John's failures. > >> > >> You will note that with John's failure's the I/O is properly page-aligned. > >> The fix to ccd deals with a misalignment problem. > > > > No it doesn't. johns failure is clearly the si_bsize* problem, the > > tell-tale sign is all the zeros in there. What John didn't tell > > us is if he uses vn, ccd or vinum (or something else!) > > Indirectly he told us that he's not using Vinum. If you're running > Vinum, you'll see something like this in the dmesg output: > > ... > da4: Fixed Direct Access SCSI-CCS device > da4: 3.300MB/s transfers > da4: 573MB (1173930 512 byte sectors: 64H 32S/T 573C) > vinum: loaded > vinum: reading configuration from /dev/da5e > vinum: updating configuration from /dev/da3h > vinum: updating configuration from /dev/da4h > vinum: updating configuration from /dev/da1s1h > vinum: updating configuration from /dev/da2h > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 23:40: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 7E546153D0 for ; Thu, 26 Aug 1999 23:39:49 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA11453; Fri, 27 Aug 1999 16:09:53 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA05764; Fri, 27 Aug 1999 16:09:50 +0930 (CST) Date: Fri, 27 Aug 1999 16:09:50 +0930 From: Greg Lehey To: Matthew Dillon Cc: Poul-Henning Kamp , Christopher Masto , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Message-ID: <19990827160950.X483@freebie.lemis.com> References: <1673.935703901@critter.freebsd.dk> <199908262325.QAA25436@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908262325.QAA25436@apollo.backplane.com>; from Matthew Dillon on Thu, Aug 26, 1999 at 04:25:14PM -0700 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 Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote: >>>> int devminor; /* minor number */ >>>> >>>> devminor = minor(dev); >>>> + dev->si_bsize_phys = DEV_BSIZE; >>>> + dev->si_bsize_best = BLKDEV_IOSIZE; >>>> + dev->si_bsize_max = MAXBSIZE; >>> >>> Bingo! Thank you. >> >> Cool, I expect grog will commit it soon. So did I until I read this message. > The patch for ccd is not quite right. Here is the patch from my > big fat patch at http://www.backplane.com/FreeBSD4/ > > The problem is that you cannot simply set the physical sector > size to DEV_BSIZE if the underlying device has a larger sector > size. If you do, specfs's blocksize alignment (another fix in > my big fat patch) will be incorrect and result in an I/O error > on the physical media. > > For example, swap-backed VN devices have a sector size of one page, > i.e. 4K. Vinum currently doesn't track the sector size of the drives. I'll have to put some code in there to DTRT. In the meantime, I'll set si_bsize_best to 4K in the hope that this will be OK. Are there any larger block sizes in current use? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 23:48:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 9A91C15442 for ; Thu, 26 Aug 1999 23:48:16 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb47.imasy.or.jp [202.227.24.175]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id PAA08317; Fri, 27 Aug 1999 15:47:24 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908270647.PAA08317@tasogare.imasy.or.jp> To: mmuir@es.co.nz Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. In-Reply-To: Your message of "Wed, 25 Aug 1999 22:18:28 +1200" <37C3C2F4.DE91BB21@es.co.nz> References: <37C3C2F4.DE91BB21@es.co.nz> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 27 Aug 1999 15:50:45 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 63 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ CC'ed current again.] > > I suspect some devices generate interrupt during suspending state, > > especially PS/2 mouse. Disabling the device driver or disconnecting > > the device from PC might solve the problem. Could you try one by one? > > > > > psm0: irq 12 on atkbdc0 > > > I had the same problem with Logitech Cordless Mouse. It seems the > > receiver is genetating intr time to time and wake my PC up from > > suspend. I reconnect it to COM1 as serial mouse, then the problem was > > gone. > > I yanked the cord then rebooted, and it seemed to make a little > difference.. > but it still came back after a while (2-3 mins) OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2 mouse, I think. Do we need something to do with psm on suspending as well as resuming? And it seems there still are other devices which wake your PC up in 2-3 mins time. Hmmm, anyone has ideas? > > > ed1: irq 3 at device 9.0 on pci0 > > > > Is your PC connected to network? Receiving packets might cause > > resuming... > > Heh, thats hardly acceptable.. I want to use the network too! :) Ahh, I meant just unplug cable tentatively to confirm. # and uninstall NIC if possible :) After the problem analyzed, we just try to fix it in proper place. > Ill try disabling the other devices at a later date, its getting late Please, please :) > > Using apmd, it could be possible something like this; > > /etc/apmd.conf: > > apm_event SUSPENDREQ { > > exec "sync && sync && sync"; > > exec "sleep 1"; > > exec "camcontrol stop [device id]"; > > exec "apm -Z"; > > } > > > > apm_event NORMRESUME { > > exec "camcontrol start [device id]"; > > exec "/etc/rc.resume"; > > } > > Yep, that works well, except the device that /, /usr, /var, /usr/home is > mounted on, spins right back up after spinning down.. (which i assume is > supposed to happen?) is there a way around that? At least, apm is in /usr/sbin/, apm -z touches /dev/apm and apmd writes log on /var/log/ via syslog :) Using `sysctl -w machdep.apm_suspend_delay=30 (or enough time for spinning down)' and moving `camcontrol stop' to the end of command list would be success. Otherwise, please forgive me. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 26 23:58:17 1999 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 94F6E14EE9 for ; Thu, 26 Aug 1999 23:58:11 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA03841; Fri, 27 Aug 1999 08:55:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Matthew Dillon , Christopher Masto , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Fri, 27 Aug 1999 16:09:50 +0930." <19990827160950.X483@freebie.lemis.com> Date: Fri, 27 Aug 1999 08:55:04 +0200 Message-ID: <3839.935736904@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg, 4K is probably too conservative, it only applies if you have a swap-backed vn device at the bottom, which would be a truly weird thing to do with vinum. Don't spend too much time on tracking the sector size yet. I think the si_bsize stuff needs some thinking before we do more with it. Poul-Henning In message <19990827160950.X483@freebie.lemis.com>, Greg Lehey writes: >On Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote: >>>>> int devminor; /* minor number */ >>>>> >>>>> devminor = minor(dev); >>>>> + dev->si_bsize_phys = DEV_BSIZE; >>>>> + dev->si_bsize_best = BLKDEV_IOSIZE; >>>>> + dev->si_bsize_max = MAXBSIZE; >>>> >>>> Bingo! Thank you. >>> >>> Cool, I expect grog will commit it soon. > >So did I until I read this message. > >> The patch for ccd is not quite right. Here is the patch from my >> big fat patch at http://www.backplane.com/FreeBSD4/ >> >> The problem is that you cannot simply set the physical sector >> size to DEV_BSIZE if the underlying device has a larger sector >> size. If you do, specfs's blocksize alignment (another fix in >> my big fat patch) will be incorrect and result in an I/O error >> on the physical media. >> >> For example, swap-backed VN devices have a sector size of one page, >> i.e. 4K. > >Vinum currently doesn't track the sector size of the drives. I'll >have to put some code in there to DTRT. In the meantime, I'll set >si_bsize_best to 4K in the hope that this will be OK. Are there any >larger block sizes in current use? > >Greg >-- >See complete headers for address, home page and phone numbers >finger grog@lemis.com for PGP public key > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 0:24:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 48C4215167 for ; Fri, 27 Aug 1999 00:22:52 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA11622; Fri, 27 Aug 1999 16:51:21 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA05866; Fri, 27 Aug 1999 16:51:20 +0930 (CST) Date: Fri, 27 Aug 1999 16:51:20 +0930 From: Greg Lehey To: Poul-Henning Kamp Cc: Matthew Dillon , Christopher Masto , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) Message-ID: <19990827165120.Y483@freebie.lemis.com> References: <19990827160950.X483@freebie.lemis.com> <3839.935736904@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3839.935736904@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Aug 27, 1999 at 08:55:04AM +0200 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 Friday, 27 August 1999 at 8:55:04 +0200, Poul-Henning Kamp wrote: > In message <19990827160950.X483@freebie.lemis.com>, Greg Lehey writes: >> On Thursday, 26 August 1999 at 16:25:14 -0700, Matthew Dillon wrote: >>>>>> int devminor; /* minor number */ >>>>>> >>>>>> devminor = minor(dev); >>>>>> + dev->si_bsize_phys = DEV_BSIZE; >>>>>> + dev->si_bsize_best = BLKDEV_IOSIZE; >>>>>> + dev->si_bsize_max = MAXBSIZE; >>>>> >>>>> Bingo! Thank you. >>>> >>>> Cool, I expect grog will commit it soon. >> >> So did I until I read this message. >> >>> The patch for ccd is not quite right. Here is the patch from my >>> big fat patch at http://www.backplane.com/FreeBSD4/ >>> >>> The problem is that you cannot simply set the physical sector >>> size to DEV_BSIZE if the underlying device has a larger sector >>> size. If you do, specfs's blocksize alignment (another fix in >>> my big fat patch) will be incorrect and result in an I/O error >>> on the physical media. >>> >>> For example, swap-backed VN devices have a sector size of one page, >>> i.e. 4K. >> >> Vinum currently doesn't track the sector size of the drives. I'll >> have to put some code in there to DTRT. In the meantime, I'll set >> si_bsize_best to 4K in the hope that this will be OK. Are there any >> larger block sizes in current use? > > 4K is probably too conservative, it only applies if you have a > swap-backed vn device at the bottom, which would be a truly > weird thing to do with vinum. I think I've heard of people doing things like this. Cybernet were thinking of it a long time ago, but I think I've talked them out of it. > Don't spend too much time on tracking the sector size yet. I think > the si_bsize stuff needs some thinking before we do more with it. OK, I'll set it to 4 kB at the moment and make a note to myself to fix it when dev_t stops changing. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 1:26: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 5271B15E01 for ; Fri, 27 Aug 1999 01:25:54 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with ESMTP id KAA11045; Fri, 27 Aug 1999 10:25:24 +0200 (MET DST) Date: Fri, 27 Aug 1999 10:25:25 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: "Jordan K. Hubbard" Cc: FreeBSD current mailing list Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <5644.935710460@localhost> 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 seriously doubt they'll win this lawsuit. You can sue someone for > anything and everything, including having a hair color which ^ in the States > displeases you, of course, but whether you actually win the lawsuit or > have it thrown out is a different matter. > > - Jordan > > > In message <15454.935598612@localhost> "Jordan K. Hubbard" writes: > > : I think people are being almost clinically paranoid here. Hasbro and > > : folks got upset over TRADEMARK infringement, e.g. from using a name > > : they had trademarked. I rather doubt that Warner Bros. have managed > > : to trademark the name "matrix" since it's already a common english > > : word. "Boggle" and "Tetris" don't fall into that category. > > > > Hasbro has sued the owners of Clue.com (Clue Computing) for > > trademark infringement. clue is a word from the dictionary... > > > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 1:43:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 1FFC1154CF for ; Fri, 27 Aug 1999 01:42:29 -0700 (PDT) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 39797 invoked by uid 1003); 27 Aug 1999 08:43:06 -0000 Date: Fri, 27 Aug 1999 10:43:06 +0200 From: Neil Blakey-Milner To: Nick Hibma Cc: "Jordan K. Hubbard" , FreeBSD current mailing list Subject: Re: "The Matrix" screensaver, v.0.2 Message-ID: <19990827104305.A39307@rucus.ru.ac.za> References: <5644.935710460@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Nick Hibma on Fri, Aug 27, 1999 at 10:25:25AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri 1999-08-27 (10:25), Nick Hibma wrote: > > I seriously doubt they'll win this lawsuit. You can sue someone for > > anything and everything, including having a hair color which > > ^ in the States Or if you're a US company. Wasn't it (the Irish?) McMuffin which Mcdonalds sued for name infringment? 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 Fri Aug 27 1:54: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7963A14DE0 for ; Fri, 27 Aug 1999 01:53:59 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA08065; Fri, 27 Aug 1999 01:52:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nick Hibma Cc: "Jordan K. Hubbard" , FreeBSD current mailing list Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Fri, 27 Aug 1999 10:25:25 +0200." Date: Fri, 27 Aug 1999 01:52:57 -0700 Message-ID: <8062.935743977@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I seriously doubt they'll win this lawsuit. You can sue someone for > > anything and everything, including having a hair color which > > ^ in the States Sorry, I've lived in Europe, you can't pull that one on me. :) In Germany, for example, it's possible to sue someone simply for sticking their finger against their forehead. The myth that only the U.S. is litigious is just that, a myth. Europeans sue the crap out of one another all the time, and for issues just as silly. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 2:24:39 1999 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 6E1B61516E for ; Fri, 27 Aug 1999 02:24:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA04522; Fri, 27 Aug 1999 11:22:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Nick Hibma , FreeBSD current mailing list Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "Fri, 27 Aug 1999 01:52:57 PDT." <8062.935743977@localhost> Date: Fri, 27 Aug 1999 11:22:45 +0200 Message-ID: <4520.935745765@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <8062.935743977@localhost>, "Jordan K. Hubbard" writes: >> > I seriously doubt they'll win this lawsuit. You can sue someone for >> > anything and everything, including having a hair color which >> >> ^ in the States > >Sorry, I've lived in Europe, you can't pull that one on me. :) > >In Germany, for example, it's possible to sue someone simply for >sticking their finger against their forehead. The myth that only the >U.S. is litigious is just that, a myth. Europeans sue the crap out of >one another all the time, and for issues just as silly. :) Jordan, I've lived in the US, Luxembourg, Italy and Denmark. While it is true that anyone can sue anybody else for anything they feel like all over the planet, the likely (lack of) outcome in europe makes it far less likely that they will do so in the first place. The main difference as far as I can tell, is that European courts apply some kind of "common sense" criteria before they award huge compensations to people who burn themselves on coffee, cut their fingers off with chain saws and so on: "Should this person not be realizing that coffee could be hot ? She has been drinking coffee for the last 50+ years ?" "If you use a chainsaw, shouldn't you be smart enough to realize that you cannot stop the chain with your hand ?" etc etc. The secondary difference is that in all the countries I know, they lawyer has to state his fee before the verdict, and it may not depend on the outcome of the verdict. The third difference is that we only use jurys in murder cases, we fully realize the ability of a showman-laywer to sway a jury, therefore we don't use them, unless the issue is the gravest crime we know off. Fourth, "puntative damages" fall to the state over here, so the potential for getting rich that way is simply not present. So while you're technically correct reality looks far different. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 2:47: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id E544A15485 for ; Fri, 27 Aug 1999 02:47:01 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-37.iptelecom.net.ua [212.42.74.101]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id MAA06576 for ; Fri, 27 Aug 1999 12:46:07 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id MAA33627 for ; Fri, 27 Aug 1999 12:44:37 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <37C65E04.399159BF@altavista.net> Date: Fri, 27 Aug 1999 12:44:36 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: current@freebsd.org Subject: VESA_800x600 mode on CT65554 based videocard. Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to get VESA_800x600 mode to work on my notebook (Toshiba SatellitePro 445, CT65554 videocard, 2MB, 800x600 LCD), and unfortunately found that it is impossible. Any ideas of what is wrong? Following is relevant pieces from dmesg, vidcontrol, kernel debug (VESA_DEBUG=1 in my kernel config), and trace of syscalls made by vidcontrol: Output of vidcontrol -i mode: mode# flags type size font window linear buffer ------------------------------------------------------------------------------ 258 (0x102) 0x0000000b G 800x600x4 4 8x16 0xa0000 64k 64k 0x00000000 2048k 259 (0x103) 0x0000000f G 800x600x8 1 8x16 0xa0000 64k 64k 0xfe000000 2048k 275 (0x113) 0x0000000f G 800x600x15 1 8x16 0xa0000 64k 64k 0xfe000000 2048k 276 (0x114) 0x0000000f G 800x600x16 1 8x16 0xa0000 64k 64k 0xfe000000 2048k 277 (0x115) 0x0000000f G 800x600x24 1 8x16 0xa0000 64k 64k 0xfe000000 2048k Output of dmesg: VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 40 00 00 01 20 00 00 01 16 01 00 01 31 01 00 01 4a 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 20 mode(s) found VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc0265fa0 (1000040) VESA: CHIPS 6x554 Super VGA VESA: Chips & Technologies, Inc. 6x554 Display Controller 2 vga-pci0: at device 4.0 on pci0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-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 0d 0e 00 00 06 40 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 Output of vidcontrol VESA_800x600: vidcontrol: cannot activate raster display: Inappropriate ioctl for device Kernel debug msgs when doing vidcontrol VESA_800x600 VESA: set_mode(): 24(18) -> 258(102) VESA: about to set a VESA mode... VESA: mode set! vesa_set_mode(): vi_width:800, len:100, line_width:100 VESA: set_mode(): 258(102) -> 24(18) Trace of syscalls (truss vidcontrol VESA_800x600): syscall ioctl(0,CONS_GETINFO,0x804bc1c) returns 0 (0x0) syscall ioctl(0,CONS_GET,0xbfbfd904) returns 0 (0x0) syscall ioctl(0,VSIOABORT,0x0) returns 0 (0x0) syscall ioctl(0,KDRASTER,0xbfbfd908) errno 25 'Inappropriate ioctl for device' syscall ioctl(0,SW_VGA_C80x25,0x0) returns 0 (0x0) syscall write(2,0xbfbfd1c4,12) returns 12 (0xc) syscall write(2,0xbfbfd1dc,30) returns 30 (0x1e) syscall write(2,0xbfbfd1bc,2) returns 2 (0x2) syscall write(2,0xbfbfd1c0,31) returns 31 (0x1f) syscall exit(0x0) process exit, rval = 0 -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 3:15:57 1999 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 ECD4314D59 for ; Fri, 27 Aug 1999 03:15:54 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:U3ORvcyWZTyKxdHUXAVQRfrIsEySX0uj@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id TAA04184; Fri, 27 Aug 1999 19:13:09 +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 TAA11192; Fri, 27 Aug 1999 19:17:27 +0900 (JST) Message-Id: <199908271017.TAA11192@zodiac.mech.utsunomiya-u.ac.jp> To: sobomax@altavista.net Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA_800x600 mode on CT65554 based videocard. In-reply-to: Your message of "Fri, 27 Aug 1999 12:44:36 +0300." <37C65E04.399159BF@altavista.net> References: <37C65E04.399159BF@altavista.net> Date: Fri, 27 Aug 1999 19:17:26 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm trying to get VESA_800x600 mode to work on my notebook (Toshiba >SatellitePro 445, CT65554 videocard, 2MB, 800x600 LCD), and >unfortunately found that it is impossible. Any ideas of what is wrong? You need to add options SC_PIXEL_MODE to your kernel configuration file. There is a note in http://www.freebsd.org/~yokota/sc_update-June.txt, which is referenced by /usr/src/UPDATING, about this option. ----------------------------------------------------------------- options SC_PIXEL_MODE Syscons has supported the raster console mode (VESA 800x600) by default. This is now an optional feature, and must be explicitly enabled by SC_PIXEL_MODE. If you have been using this mode, add the above option. ----------------------------------------------------------------- Please also refer to the man page syscons(4). Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 3:39:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from elch.de.uu.net (elch.de.uu.net [192.76.144.55]) by hub.freebsd.org (Postfix) with ESMTP id 194AC14C56 for ; Fri, 27 Aug 1999 03:39:05 -0700 (PDT) (envelope-from michaelc@tmbbwmc.bbn.hp.com) Received: from tmbbwmc.bbn.hp.com (pec-0-2.tnt1.s2.uunet.de [149.225.0.2]) by elch.de.uu.net (5.5.5/5.5.5) with ESMTP id MAA22543 for ; Fri, 27 Aug 1999 12:35:25 +0200 (MET DST) Received: from pc-micha.mc.hp.com (pc-micha.mc.hp.com [172.16.81.200]) by tmbbwmc.bbn.hp.com (Postfix) with ESMTP id 91C2A9B08 for ; Fri, 27 Aug 1999 10:32:37 +0000 (GMT) Received: from localhost (michaelc@localhost) by pc-micha.mc.hp.com (8.9.3/8.9.3) with ESMTP id MAA40676 for ; Fri, 27 Aug 1999 12:33:45 +0200 (MEST) (envelope-from michaelc@pc-micha.mc.hp.com) Date: Fri, 27 Aug 1999 12:33:45 +0200 (MEST) From: Michael Class Reply-To: michael_class@gmx.net To: current@freebsd.org Subject: current-APM causes panic on SMP-System Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-841842983-935750025=:40664" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-841842983-935750025=:40664 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, since the apm-code was changed to use the generic bios-call interface (dated around 1999/07/28) my FreeBSD-4.0-current system panics when I do an "apmconf -e". This has not changed since then. I reproduced it with a very current System (1999/08/25) today. The system is a Dual-Proc GigaByte 6BXDS-MB with 2x350Mhz PII and 256MB-RAM. For further information I have added the Config-File and dmesg-output. When calling apmconf -e i am getting the following panic: (written down by hand, so there might be some typos) ----------------------------------------------------------------------- Fatal trap 12: page fault while in kernel mode mp_lock=01000002; cpuid=1; lapic.id=01000000 fault virtual address = 0x8380 fault code = supervisor read, page not present ip = 0x50:0x8380 stack = 0x10:0xff80df24 frame = 0x10:0xc02bde80 code = base 0xc00f0000, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 1, gran 0 proc flags = intr enabled, resume, iopl=0 current proc = idle interrupt mask = <-- SMP: XXX ----------------------------------------------------------------------- The Adress 0x8380 seems to be the one from the APM-BIOS-Call. What can I do to track this further down? Michael ------------------------------------------------------------------------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: michael_class@gmx.net Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) ------------------------------------------------------------------------- --0-841842983-935750025=:40664 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=MCSMP Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: kernel-configuration Content-Disposition: attachment; filename=MCSMP Iw0KIyBTTVAtR0VORVJJQyAtLSBTbXAgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu DQojDQojCSRJZDogU01QLUdFTkVSSUMsdiAxLjIwIDE5OTgvMTAvMjIgMTM6 NDk6NTEgYmRlIEV4cCAkDQoNCm1hY2hpbmUJCWkzODYNCmNwdQkJSTY4Nl9D UFUNCmlkZW50CQlNQ1NNUA0KbWF4dXNlcnMJNjQNCg0KI21ha2VvcHRpb25z ICAgIERFQlVHPS1nICAgICAgICAgICAgICAgICNCdWlsZCBrZXJuZWwgd2l0 aCBnZGIoMSkgZGVidWcgc3ltYm9scw0KDQojIENyZWF0ZSBhIFNNUCBjYXBh YmxlIGtlcm5lbCAobWFuZGF0b3J5IG9wdGlvbnMpOg0Kb3B0aW9ucwkJU01Q CQkJIyBTeW1tZXRyaWMgTXVsdGlQcm9jZXNzb3IgS2VybmVsDQpvcHRpb25z CQlBUElDX0lPCQkJIyBTeW1tZXRyaWMgKEFQSUMpIEkvTw0KDQojIE9wdGlv bmFsLCB0aGVzZSBhcmUgdGhlIGRlZmF1bHRzOg0KI29wdGlvbnMJCU5DUFU9 MgkJCSMgbnVtYmVyIG9mIENQVXMNCiNvcHRpb25zCQlOQlVTPTQJCQkjIG51 bWJlciBvZiBidXNzZXMNCiNvcHRpb25zCQlOQVBJQz0xCQkJIyBudW1iZXIg b2YgSU8gQVBJQ3MNCiNvcHRpb25zCQlOSU5UUj0yNAkJIyBudW1iZXIgb2Yg SU5Ucw0KDQojIExldHMgYWx3YXlzIGVuYWJsZSB0aGUga2VybmVsIGRlYnVn Z2VyIGZvciBTTVAuDQpvcHRpb25zCQlEREINCg0KIyBTTVAgc2hvdWxkbid0 IG5lZWQgeDg3IGVtdWxhdGlvbiwgZGlzYWJsZSBieSBkZWZhdWx0Lg0KI29w dGlvbnMJCU1BVEhfRU1VTEFURQkJI1N1cHBvcnQgZm9yIHg4NyBlbXVsYXRp b24NCg0Kb3B0aW9ucwkJSU5FVAkJCSNJbnRlck5FVHdvcmtpbmcNCm9wdGlv bnMJCUZGUwkJCSNCZXJrZWxleSBGYXN0IEZpbGVzeXN0ZW0NCm9wdGlvbnMJ CUZGU19ST09UCQkjRkZTIHVzYWJsZSBhcyByb290IGRldmljZSBba2VlcCB0 aGlzIV0NCm9wdGlvbnMJCU1GUwkJCSNNZW1vcnkgRmlsZXN5c3RlbQ0Kb3B0 aW9ucwkJTUZTX1JPT1QJCSNNRlMgdXNhYmxlIGFzIHJvb3QgZGV2aWNlLCAi TUZTIiByZXEnZWQNCm9wdGlvbnMJCU5GUwkJCSNOZXR3b3JrIEZpbGVzeXN0 ZW0NCm9wdGlvbnMJCU5GU19ST09UCQkjTkZTIHVzYWJsZSBhcyByb290IGRl dmljZSwgIk5GUyIgcmVxJ2VkDQpvcHRpb25zCQlNU0RPU0ZTCQkJI01TRE9T IEZpbGVzeXN0ZW0NCm9wdGlvbnMJCUNEOTY2MAkJCSNJU08gOTY2MCBGaWxl c3lzdGVtDQpvcHRpb25zCQlDRDk2NjBfUk9PVAkJI0NELVJPTSB1c2FibGUg YXMgcm9vdC4gIkNEOTY2MCIgcmVxJ2VkDQpvcHRpb25zCQlQUk9DRlMJCQkj UHJvY2VzcyBmaWxlc3lzdGVtDQpvcHRpb25zCQlLRVJORlMJCQkNCm9wdGlv bnMgICAgICAgICBDT01QQVRfTElOVVgNCm9wdGlvbnMJCUNPTVBBVF80MwkJ I0NvbXBhdGlibGUgd2l0aCBCU0QgNC4zIFtLRUVQIFRISVMhXQ0Kb3B0aW9u cwkJU0NTSV9ERUxBWT0xMDAwMAkjQmUgcGVzc2ltaXN0aWMgYWJvdXQgSm9l IFNDU0kgZGV2aWNlDQpvcHRpb25zCQlVQ09OU09MRQkJI0FsbG93IHVzZXJz IHRvIGdyYWIgdGhlIGNvbnNvbGUNCiNvcHRpb25zCUZBSUxTQUZFCQkjQmUg Y29uc2VydmF0aXZlDQpvcHRpb25zCQlVU0VSQ09ORklHCQkjYm9vdCAtYyBl ZGl0b3INCm9wdGlvbnMJCVZJU1VBTF9VU0VSQ09ORklHCSN2aXN1YWwgYm9v dCAtYyBlZGl0b3INCg0KIyBFbmFibGUgdGhlIGZvbGxvd2luZyAoSVBGSVJF V0FMTF9WRVJCT1NFIG9wdGlvbmFsKSB0byBlbmFibGUgdGhlIElQIGZpcmV3 YWxsDQojIGNvZGUuICBUaGlzIGlzIHVzZWQgaW4gY29uanVuY3Rpb24gd2l0 aCB0aGUgaXBmdygxKSBjb21tYW5kLiAgU2VlIHRoZQ0KIyBtYW4gcGFnZSBm b3IgbW9yZSBkZXRhaWxzLg0Kb3B0aW9ucyAgICAgICAgIElQRklSRVdBTEwg ICAgICAgICAgICAgICNmaXJld2FsbA0Kb3B0aW9ucyAgICAgICAgIElQRklS RVdBTExfVkVSQk9TRSAgICAgICNwcmludCBpbmZvcm1hdGlvbiBhYm91dCAN CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAjIGRy b3BwZWQgcGFja2V0cw0Kb3B0aW9ucyAgICAgICAgIElQRklSRVdBTExfRk9S V0FSRCAgICAgICNlbmFibGUgeHBhcmVudCBwcm94eSBzdXBwb3J0DQojb3B0 aW9ucyAgICAgICAgIElQRklSRVdBTExfVkVSQk9TRV9MSU1JVD0xMDAgI2xp bWl0IHZlcmJvc2l0eQ0Kb3B0aW9ucyAgICAgICAgIElQRklSRVdBTExfREVG QVVMVF9UT19BQ0NFUFQgI2FsbG93IGV2ZXJ5dGhpbmcgYnkgZGVmYXVsdA0K b3B0aW9ucyAgICAgICAgIElQRElWRVJUICAgICAgICAgICAgICAgICNkaXZl cnQgc29ja2V0cw0KI29wdGlvbnMgICAgICAgICBJUEZJTFRFUiAgICAgICAg ICAgICAgICAja2VybmVsIGlwZmlsdGVyIHN1cHBvcnQNCiNvcHRpb25zICAg ICAgICAgSVBGSUxURVJfTE9HICAgICAgICAgICAgI2lwZmlsdGVyIGxvZ2dp bmcNCiNvcHRpb25zICAgICAgICBJUEZJTFRFUl9MS00gICAgICAgICAgICAj a2VybmVsIHN1cHBvcnQgZm9yIGlwX2ZpbC5vIExLTQ0KI29wdGlvbnMgICAg ICAgICBUQ1BERUJVRw0KDQojIElDTVBfQkFORExJTSBlbmFibGVzIGljbXAg ZXJyb3IgcmVzcG9uc2UgYmFuZHdpZHRoIGxpbWl0aW5nLiAgIFlvdQ0KIyB0 eXBpY2FsbHkgd2FudCB0aGlzIG9wdGlvbiBhcyBpdCB3aWxsIGhlbHAgcHJv dGVjdCB0aGUgbWFjaGluZSBmcm9tDQojIEQuTy5TLiBwYWNrZXQgYXR0YWNr cy4NCiMNCm9wdGlvbnMgICAgICAgICBJQ01QX0JBTkRMSU0NCg0KIyBEVU1N WU5FVCBlbmFibGVzIHRoZSAiZHVtbXluZXQiIGJhbmR3aWR0aCBsaW1pdGVy LiBZb3UgbmVlZA0KIyBJUEZJUkVXQUxMIGFzIHdlbGwuIFNlZSB0aGUgZHVt bXluZXQoNCkgbWFucGFnZSBmb3IgbW9yZSBpbmZvLg0KIyBCUklER0UgZW5h YmxlcyBicmlkZ2luZyBiZXR3ZWVuIGV0aGVybmV0IGNhcmRzIC0tIHNlZSBi cmlkZ2UoNCkuDQojIFlvdSBjYW4gdXNlIElQRklSRVdBTEwgYW5kIGR1bW15 bmV0IHRvZ2V0aGVyIHdpdGggYnJpZGdpbmcuDQojb3B0aW9ucyAgICAgICAg RFVNTVlORVQNCiNvcHRpb25zICAgICAgICBCUklER0UNCg0KDQojIEFsbG93 IHRoZSBGRlMgdG8gdXNlIFNvZnR1cGRhdGVzIHRlY2hub2xvZ3kuDQojIFRv IGRvIHRoaXMgeW91IG5lZWQgdG8gZmV0Y2ggdGhlIHR3byBmaWxlcw0KIyAv c3lzL3Vmcy9mZnMvc29mdGRlcC5oIGFuZCAvc3lzL3Vmcy9mZnMvZmZzX3Nv ZnRkZXAuYw0KIyBmcm9tIGZyZWVic2Qub3JnIGFuZCB1bmRlcnN0YW5kIHRo ZSBsaWNlbnNpbmcgcmVzdHJpY3Rpb25zLg0Kb3B0aW9ucyAgICAgICAgICAg ICAgICBTT0ZUVVBEQVRFUw0KDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMN CiMgUE9TSVggUDEwMDMuMUINCg0KIyBSZWFsIHRpbWUgZXh0ZW5zaW9ucyBh ZGRlZCBpbnQgdGhlIDE5OTMgUG9zaXgNCiMgUDEwMDNfMUI6IEluZnJhc3Ry dWN0dXJlDQojIF9LUE9TSVhfUFJJT1JJVFlfU0NIRURVTElORzogQnVpbGQg aW4gX1BPU0lYX1BSSU9SSVRZX1NDSEVEVUxJTkcNCiMgX0tQT1NJWF9WRVJT SU9OOiAgICAgICAgICAgICBWZXJzaW9uIGtlcm5lbCBpcyBidWlsdCBmb3IN Cg0Kb3B0aW9ucyAgICAgICAgIFAxMDAzXzFCDQpvcHRpb25zICAgICAgICAg X0tQT1NJWF9QUklPUklUWV9TQ0hFRFVMSU5HDQpvcHRpb25zICAgICAgICAg X0tQT1NJWF9WRVJTSU9OPTE5OTMwOUwNCiMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIw0KY29udHJvbGxlcglpc2EwCWF0IG5leHVzPwkNCmNvbnRyb2xsZXIJ cGNpMAlhdCBuZXh1cz8NCiNjb250cm9sbGVyICAgICAgcG5wMA0KDQoNCmNv bnRyb2xsZXIJZmRjMAlhdCBpc2E/IHBvcnQgIklPX0ZEMSIgaXJxIDYgZHJx IDINCmRpc2sJCWZkMAlhdCBmZGMwIGRyaXZlIDANCiNkaXNrCQlmZDEJYXQg ZmRjMCBkcml2ZSAxDQoNCiMNCiMgQVRBIGFuZCBBVEFQSSBkZXZpY2VzIA0K IyBUaGlzIGlzIHdvcmsgaW4gcHJvZ3Jlc3MsIHVzZSBhdCB5b3VyIG93biBy aXNrLiANCiMgSXQgY3VycmVudGx5IHJldXNlcyB0aGUgbWFqb3JzIG9mIHdk LmMgYW5kIGZyZWluZHMuDQojIEl0IGNhbm5vdCBjby1leGlzdCB3aXRoIHRo ZSBvbGQgc3lzdGVtIGluIG9uZSBrZXJuZWwuDQojIFlvdSBvbmx5IG5lZWQg b25lICJjb250cm9sbGVyIGF0YTAiIGZvciBpdCB0byBmaW5kIGFsbA0KIyBQ Q0kgZGV2aWNlcyBvbiBtb2Rlcm4gbWFjaGluZXMuDQojY29udHJvbGxlciAg ICAgYXRhMA0KI2RldmljZSAgICAgICAgIGF0YWRpc2swICAgICAgICAjIEFU QSBkaXNrIGRyaXZlcw0KI2RldmljZSAgICAgICAgIGF0YXBpY2QwICAgICAg ICAjIEFUQVBJIENEUk9NIGRyaXZlcw0KI2RldmljZSAgICAgICAgIGF0YXBp c3QwICAgICAgICAjIEFUQVBJIHRhcGUgZHJpdmVzDQojZGV2aWNlICAgICAg ICAgYXRhcGlmZDAgICAgICAgICMgQVRBUEkgZmxvcHB5IGRyaXZlcw0KDQoj IHRoZXNlIGFyZSB0aGUgb2xkIHdkLWRyaXZlcnM6DQojY29udHJvbGxlcgl3 ZGMwCWF0IGlzYT8gcG9ydCAiSU9fV0QxIiBpcnEgMTQNCiNkaXNrCQl3ZDAJ YXQgd2RjMCBkcml2ZSAwDQojZGlzawkJd2QxCWF0IHdkYzAgZHJpdmUgMQ0K DQojY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9fV0QyIiBpcnEg MTUNCiNkaXNrCQl3ZDIJYXQgd2RjMSBkcml2ZSAwDQojZGlzawkJd2QzCWF0 IHdkYzEgZHJpdmUgMQ0KDQojb3B0aW9ucyAgICAgICAgIEFUQVBJICAgICAg ICAgICAjRW5hYmxlIEFUQVBJIHN1cHBvcnQgZm9yIElERSBidXMNCiNvcHRp b25zICAgICAgICAgQVRBUElfU1RBVElDICAgICNEb24ndCBkbyBpdCBhcyBh biBMS00NCiNkZXZpY2UgICAgICAgICAgYWNkMCAgICAgICAgICAgICNJREUg Q0QtUk9NDQojZGV2aWNlICAgICAgICAgIHdmZDAgICAgICAgICAgICAjSURF IEZsb3BweSAoZS5nLiBMUy0xMjApDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjDQoN CmRldmljZSAgICAgICAgICBia3RyMA0KIyBvcHRpb25zIE9WRVJSSURFX0NB UkQ9eHh4DQojIG9wdGlvbnMgT1ZFUlJJREVfVFVORVI9eHh4DQojIG9wdGlv bnMgT1ZFUlJJREVfTVNQPTENCiMgb3B0aW9ucyBPVkVSUklERV9EQlg9MQ0K IyBUaGVzZSBvcHRpb25zIGNhbiBiZSB1c2VkIHRvIG92ZXJyaWRlIHRoZSBh dXRvIGRldGVjdGlvbg0KIyBUaGUgY3VycmVudCB2YWx1ZXMgZm9yIHh4eCBh cmUgZm91bmQgaW4gL3Vzci9zcmMvc3lzL3BjaS9icm9va3RyZWU4NDguYw0K IyBVc2luZyBzeXNjdGwoOCkgcnVuLXRpbWUgb3ZlcnJpZGVzIG9uIGEgcGVy LWNhcmQgYmFzaXMgY2FuIGJlIG1hZGUNCiMgDQpvcHRpb25zIEJST09LVFJF RV9TWVNURU1fREVGQVVMVD1CUk9PS1RSRUVfUEFMDQojIG9yDQojIG9wdGlv bnMgQlJPT0tUUkVFX1NZU1RFTV9ERUZBVUxUPUJST09LVFJFRV9OVFNDIA0K IyBTcGVjaWZlcyB0aGUgZGVmYXVsdCB2aWRlbyBjYXB0dXJlIG1vZGUuDQoj IFRoaXMgaXMgcmVxdWlyZWQgZm9yIER1YWwgQ3J5c3RhbCAoMjgmMzVNaHop IGJvYXJkcyB3aGVyZSBQQUwgaXMgdXNlZA0KIyB0byBwcmV2ZW50IGhhbmdz IGR1cmluZyBpbml0aWFsaXNhdGlvbi4gIGVnIFZpZGVvTG9naWMgQ2FwdGl2 YXRvciBQQ0kuDQojDQpvcHRpb25zIEJLVFJfVVNFX1BMTA0KIyBQQUwgb3Ig U0VDQU0gdXNlcnMgd2hvIGhhdmUgYSAyOE1oeiBjcnlzdGFsIChhbmQgbm8g MzVNaHogY3J5c3RhbCkNCiMgbXVzdCBlbmFibGUgUExMIG1vZGUgd2l0aCB0 aGlzIG9wdGlvbi4gZWcgc29tZSBuZXcgQnQ4NzggY2FyZHMuDQoNCg0KDQoj IEEgc2luZ2xlIGVudHJ5IGZvciBhbnkgb2YgdGhlc2UgY29udHJvbGxlcnMg KG5jciwgYWhiLCBhaGMsIGFtZCkgaXMNCiMgc3VmZmljaWVudCBmb3IgYW55 IG51bWJlciBvZiBpbnN0YWxsZWQgZGV2aWNlcy4NCmNvbnRyb2xsZXIJYWhj MA0KY29udHJvbGxlcglhaGMxDQoNCmNvbnRyb2xsZXIJc2NidXMwCWF0IGFo YzANCmNvbnRyb2xsZXIJc2NidXMxCWF0IGFoYzENCg0KZGV2aWNlICAgICAg ICAgIGRhMCAgICAgI2F0IHNjYnVzMSB0YXJnZXQgMA0KZGV2aWNlICAgICAg ICAgIGRhMSAgICAgI2F0IHNjYnVzMSB0YXJnZXQgMQ0KZGV2aWNlICAgICAg ICAgIHNhMCAgICAgI2F0IHNjYnVzMCB0YXJnZXQgNA0KZGV2aWNlICAgICAg ICAgIGNkMCAgICAgYXQgc2NidXMwIHRhcmdldCAzDQpkZXZpY2UgICAgICAg ICAgY2QxICAgICBhdCBzY2J1czAgdGFyZ2V0IDUNCmRldmljZSAgICAgICAg ICBwYXNzMCAgIGF0IHNjYnVzMCB0YXJnZXQgMiAgICAgICMgc2Nhbm5lcg0K ZGV2aWNlICAgICAgICAgIHBhc3MxICAgYXQgc2NidXMwIHRhcmdldCAzICAg ICAgIyBjZC1ydw0KZGV2aWNlICAgICAgICAgIHBhc3MyICAgYXQgc2NidXMw IHRhcmdldCA1ICAgICAgIyBjZA0KDQpvcHRpb25zICAgICAgICAgU0NTSV9S RVBPUlRfR0VPTUVUUlkNCg0KDQojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQg Y29uc29sZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUNCmNv bnRyb2xsZXIJYXRrYmRjMCBhdCBpc2E/IHBvcnQgSU9fS0JEDQpkZXZpY2UJ CWF0a2JkMCAgYXQgYXRrYmRjPyBpcnEgMSBmbGFncyAweDAxDQpkZXZpY2Ug CQlwc20wICAgIGF0IGF0a2JkYz8gaXJxIDEyDQoNCmRldmljZSAJCXZnYTAg ICAgYXQgaXNhPyBwb3J0ID8gY29uZmxpY3RzDQpkZXZpY2UJCXNjMCAgICAg YXQgaXNhPw0KIyBzcGxhc2ggc2NyZWVuL3NjcmVlbiBzYXZlciAgICANCnBz ZXVkby1kZXZpY2UgICBzcGxhc2gNCg0KZGV2aWNlCQlucHgwCWF0IG5leHVz PyBwb3J0IElPX05QWCBpcnEgMTMNCg0KIw0KIyBMYXB0b3Agc3VwcG9ydCAo c2VlIExJTlQgZm9yIG1vcmUgb3B0aW9ucykNCiMNCmRldmljZQkJYXBtMCAg ICBhdCBuZXh1cz8JIyBBZHZhbmNlZCBQb3dlciBNYW5hZ2VtZW50DQoNCmRl dmljZSAgICAgICAgICBzaW8wICAgIGF0IGlzYT8gcG9ydCBJT19DT00xIGZs YWdzIDB4MTAgaXJxIDQgDQpkZXZpY2UgICAgICAgICAgc2lvMSAgICBhdCBp c2E/IHBvcnQgSU9fQ09NMiBpcnEgMyANCiNkZXZpY2UgICAgICAgICAgc2lv MiAgICBhdCBpc2E/IHBvcnQgSU9fQ09NMyBpcnEgOSANCg0KZGV2aWNlICAg ICAgICAgIHBwYzAgICAgYXQgaXNhPyBwb3J0ID8gaXJxIDcgDQpjb250cm9s bGVyICAgICAgcHBidXMwDQpkZXZpY2UgICAgICAgICAgbHB0MCAgIGF0IHBw YnVzPw0KDQpkZXZpY2UgeGwwDQojZGV2aWNlIGVkMCBhdCBpc2E/IHBvcnQg MHgyODAgbmV0IGlycSAxMCBpb21lbSAweGQ4MDAwDQoNCg0KIyBDb250cm9s cyBhbGwgc291bmQgZGV2aWNlcw0KZGV2aWNlIHBjbTAgDQoNCg0KcHNldWRv LWRldmljZQlsb29wDQpwc2V1ZG8tZGV2aWNlCWV0aGVyDQpwc2V1ZG8tZGV2 aWNlCXR1bg0KcHNldWRvLWRldmljZQlwdHkJDQpwc2V1ZG8tZGV2aWNlCWd6 aXAJCSMgRXhlYyBnemlwcGVkIGEub3V0J3MNCnBzZXVkby1kZXZpY2UgICBz cGVha2VyDQpwc2V1ZG8tZGV2aWNlICAgdm4gICAgICAgICAgICAgICNWbm9k ZSBkcml2ZXIgKHR1cm5zIGEgZmlsZSBpbnRvIGEgZGV2aWNlKQ0KcHNldWRv LWRldmljZQlzdHJlYW1zCQkjU1ZSNCBzdXBwb3J0DQoNCg0KIyBLVFJBQ0Ug ZW5hYmxlcyB0aGUgc3lzdGVtLWNhbGwgdHJhY2luZyBmYWNpbGl0eSBrdHJh Y2UoMikuDQojIFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRvIHlvdXIga2VybmVs LCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzDQojIHRoZSBjb3N0cyBvZiBlYWNo IHN5c2NhbGwuDQojb3B0aW9ucwlLVFJBQ0UJCSNrZXJuZWwgdHJhY2luZw0K DQojIFRoaXMgcHJvdmlkZXMgc3VwcG9ydCBmb3IgU3lzdGVtIFYgc2hhcmVk IG1lbW9yeS4NCiMNCm9wdGlvbnMJCVNZU1ZTSE0NCm9wdGlvbnMgICAgICAg ICBTWVNWU0VNDQpvcHRpb25zICAgICAgICAgU1lTVk1TRw0KI29wdGlvbnMg ICAgICAgICBTSE1NQVhQR1M9ODE5MiAgIyBtb3JlIHNoYXJlZC1tZW1vcnkg Zm9yIHNhbWJhIGFuZCBwb3N0Z3Jlc3FsDQpvcHRpb25zICAgICAgICAgU0hN TUFYUEdTPTEwMDAwDQpvcHRpb25zCQlTSE1NTkk9MTAwDQpvcHRpb25zCQlT SE1TRUc9MTANCm9wdGlvbnMJCVNFTU1OUz0yMDANCm9wdGlvbnMJCVNFTU1O ST03MA0Kb3B0aW9ucwkJU0VNTVNMPTYxDQoNCg0KIyAgVGhlIGBicGYnIHBz ZXVkby1kZXZpY2UgZW5hYmxlcyB0aGUgQmVya2VsZXkgUGFja2V0IEZpbHRl ci4gIEJlDQojICBhd2FyZSBvZiB0aGUgbGVnYWwgYW5kIGFkbWluaXN0cmF0 aXZlIGNvbnNlcXVlbmNlcyBvZiBlbmFibGluZyB0aGlzDQojICBvcHRpb24u ICBUaGUgbnVtYmVyIG9mIGRldmljZXMgZGV0ZXJtaW5lcyB0aGUgbWF4aW11 bSBudW1iZXIgb2YNCiMgIHNpbXVsdGFuZW91cyBCUEYgY2xpZW50cyBwcm9n cmFtcyBydW5uYWJsZS4NCnBzZXVkby1kZXZpY2UJYnBmCQkjQmVya2VsZXkg cGFja2V0IGZpbHRlcg0KDQojIFVTQiBzdXBwb3J0ICAgDQojY29udHJvbGxl ciAgICB1aGNpMA0KI2NvbnRyb2xsZXIgICAgb2hjaTANCiNjb250cm9sbGVy ICAgIHVzYjANCiMNCiMgZm9yIHRoZSBtb21lbnQgd2UgaGF2ZSB0byBzcGVj aWZ5IHRoZSBwcmlvcml0aWVzIG9mIHRoZSBkZXZpY2UNCiMgZHJpdmVycyBl eHBsaWNpdGx5IGJ5IHRoZSBvcmRlcmluZyBpbiB0aGUgbGlzdCBiZWxvdy4g VGhpcyB3aWxsDQojIGJlIGNoYW5nZWQgaW4gdGhlIGZ1dHVyZS4NCiMNCiNk ZXZpY2UgICAgICAgIHVtczANCiNkZXZpY2UgICAgICAgIHVrYmQwDQojZGV2 aWNlICAgICAgICB1bHB0MA0KI2RldmljZSAgICAgICAgdWh1YjANCiNkZXZp Y2UgICAgICAgIHVjb20wDQojZGV2aWNlICAgICAgICB1bW9kZW0wICANCiNk ZXZpY2UgICAgICAgIGhpZDANCiNkZXZpY2UgICAgICAgIHVnZW4wDQoNCiMN CiNvcHRpb25zICAgICAgIFVTQl9ERUJVRw0KI29wdGlvbnMgICAgICAgVVNC VkVSQk9TRQ0KDQojDQojIFNNQiBidXMNCiMNCiMgU3lzdGVtIE1hbmFnZW1l bnQgQnVzIHN1cHBvcnQgcHJvdmlkZWQgYnkgdGhlICdzbWJ1cycgZGV2aWNl Lg0KIw0KIyBTdXBwb3J0ZWQgZGV2aWNlczoNCiMgc21iICAgc3RhbmRhcmQg aW8NCiMNCiMgU3VwcG9ydGVkIGludGVyZmFjZXM6DQojIGlpY3NtYiBJMkMg dG8gU01CIGJyaWRnZSB3aXRoIGFueSBpaWNidXMgaW50ZXJmYWNlDQojIGJr dHIgIGJyb29rdHJlZTg0OCBJMkMgaGFyZHdhcmUgaW50ZXJmYWNlDQojIGlu dHBtIEludGVsIFBJSVg0IFBvd2VyIE1hbmFnZW1lbnQgVW5pdA0KIyANCmNv bnRyb2xsZXIgc21idXMwDQpjb250cm9sbGVyIGlpY2J1czANCmNvbnRyb2xs ZXIgaWljYmIwDQpjb250cm9sbGVyIGludHBtMA0KZGV2aWNlIHNtYjAgICAg IGF0IHNtYnVzPw0K --0-841842983-935750025=:40664 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: dmesg output Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk4MiwgMTk4NiwgMTk4OSwgMTk5MSwgMTk5Mw0K CVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEu IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMC1DVVJSRU5UICMw OiBXZWQgQXVnIDI1IDE5OjEwOjEyIE1FU1QgMTk5OQ0KICAgIG1pY2hhZWxj QHBjLW1pY2hhLm1jLmhwLmNvbTovdXNyL3NyYy9zeXMvY29tcGlsZS9NQ1NN UA0KVGltZWNvdW50ZXIgImk4MjU0IiAgZnJlcXVlbmN5IDExOTMxODIgSHoN CkNQVTogUGVudGl1bSBJSS9YZW9uL0NlbGVyb24gKDY4Ni1jbGFzcyBDUFUp DQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4NjUyICBTdGVw cGluZyA9IDINCiAgRmVhdHVyZXM9MHgxODNmYmZmPEZQVSxWTUUsREUsUFNF LFRTQyxNU1IsUEFFLE1DRSxDWDgsQVBJQyxTRVAsTVRSUixQR0UsTUNBLENN T1YsUEFULFBTRTM2LE1NWCxGWFNSPg0KcmVhbCBtZW1vcnkgID0gMjY4MzY5 OTIwICgyNjIwODBLIGJ5dGVzKQ0KYXZhaWwgbWVtb3J5ID0gMjU3MTEwMDE2 ICgyNTEwODRLIGJ5dGVzKQ0KUHJvZ3JhbW1pbmcgMjQgcGlucyBpbiBJT0FQ SUMgIzANCkZyZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBtb3RoZXJib2Fy ZA0KIGNwdTAgKEJTUCk6IGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQw MDExLCBhdCAweGZlZTAwMDAwDQogY3B1MSAoQVApOiAgYXBpYyBpZDogIDEs IHZlcnNpb246IDB4MDAwNDAwMTEsIGF0IDB4ZmVlMDAwMDANCiBpbzAgKEFQ SUMpOiBhcGljIGlkOiAgMiwgdmVyc2lvbjogMHgwMDE3MDAxMSwgYXQgMHhm ZWMwMDAwMA0KUHJlbG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhj MDMxYjAwMC4NClBlbnRpdW0gUHJvIE1UUlIgc3VwcG9ydCBlbmFibGVkDQpu cHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9uIG1vdGhlcmJvYXJkDQpucHgwOiBJ TlQgMTYgaW50ZXJmYWNlDQphcG0wOiA8QVBNIEJJT1M+IG9uIG1vdGhlcmJv YXJkDQphcG06IEFQTSBCSU9TIHZlcnNpb24gMDEwMg0KYXBtOiBDb2RlMTYg MHhjMDBmMDAwMCwgRGF0YSAweGMwMGZkZjgwDQphcG06IENvZGUgZW50cnkg MHgwMDAwODM4MCwgSWRsaW5nIENQVSBlbmFibGVkLCBNYW5hZ2VtZW50IGVu YWJsZWQNCmFwbTogQ1NfbGltaXQ9MHhmZmZmLCBEU19saW1pdD0weGZmZmYN CmFwbTogRW5nYWdlZCBjb250cm9sIGVuYWJsZWQNCmFwbTogZm91bmQgQVBN IEJJT1MgdjEuMiwgY29ubmVjdGVkIGF0IHYxLjINCmFwbTogU2xvdyBJZGxp bmcgQ1BVIGVuYWJsZWQNCkFkZCBob29rICJkZWZhdWx0IHN1c3BlbmQiDQpB ZGQgaG9vayAiZGVmYXVsdCByZXN1bWUiDQpwY2liMDogPEludGVsIDgyNDQz QlggKDQ0MCBCWCkgaG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2Fy ZA0KcGNpMDogPFBDSSBidXM+IG9uIHBjaWIwDQpXQVJOSU5HOiAiYmt0ciIg aXMgdXN1cnBpbmcgImJrdHIiJ3MgY2RldnN3W10NCnBjaWIxOiA8SW50ZWwg ODI0NDNCWCAoNDQwIEJYKSBQQ0ktUENJIChBR1ApIGJyaWRnZT4gYXQgZGV2 aWNlIDEuMCBvbiBwY2kwDQpwY2kxOiA8UENJIGJ1cz4gb24gcGNpYjENCmlz YWIwOiA8SW50ZWwgODIzNzFBQiBQQ0kgdG8gSVNBIGJyaWRnZT4gYXQgZGV2 aWNlIDcuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCmNo aXAxOiA8SW50ZWwgUElJWDQgSURFIGNvbnRyb2xsZXI+IGF0IGRldmljZSA3 LjEgb24gcGNpMA0KY2hpcDI6IDxVSENJIFVTQiBjb250cm9sbGVyPiBpcnEg MTUgYXQgZGV2aWNlIDcuMiBvbiBwY2kwDQppbnRwbTA6IDxJbnRlbCA4MjM3 MUFCIFBvd2VyIG1hbmFnZW1lbnQgY29udHJvbGxlcj4gYXQgZGV2aWNlIDcu MyBvbiBwY2kwDQppbnRwbTA6IEkvTyBtYXBwZWQgNTAwMA0KaW50cG0wOiBp bnRyIElSUSA5IGVuYWJsZWQgcmV2aXNpb24gMA0Kc21idXMwOiA8U3lzdGVt IE1hbmFnZW1lbnQgQnVzPiBvbiBpbnRzbWIwDQpzbWIwOiA8U01CdXMgZ2Vu ZXJhbCBwdXJwb3NlIEkvTz4gb24gc21idXMwDQppbnRwbTA6IFBNIEkvTyBt YXBwZWQgNDAwMCANCnZnYS1wY2kwOiA8TWF0cm94IE1HQSAyMTY0VyBncmFw aGljcyBhY2NlbGVyYXRvcj4gaXJxIDE2IGF0IGRldmljZSA4LjAgb24gcGNp MA0KYmt0cjA6IDxCcm9va1RyZWUgODc4PiBpcnEgMTcgYXQgZGV2aWNlIDku MCBvbiBwY2kwDQppaWNiYjA6IDxJMkMgZ2VuZXJpYyBiaXQtYmFuZ2luZyBk cml2ZXI+IG9uIGJ0aTJjMA0KaWljYnVzMDogPFBoaWxpcHMgSTJDIGJ1cz4g b24gaWljYmIwIG1hc3Rlci1vbmx5DQpzbWJ1czE6IDxTeXN0ZW0gTWFuYWdl bWVudCBCdXM+IG9uIGJ0aTJjMA0Kc21iMTogPFNNQnVzIGdlbmVyYWwgcHVy cG9zZSBJL08+IG9uIHNtYnVzMQ0KSGF1cHBhdWdlIE1vZGVsIDYxMzQ0IEQx MjENCkhhdXBwYXVnZSBXaW5DYXN0L1RWLCBQaGlsaXBzIEZSMTIxNiBQQUwg dHVuZXIsIG1zcDM0MDBjIHN0ZXJlbywgcmVtb3RlIGNvbnRyb2wuDQpEZXRl Y3RlZCBhIE1TUDM0MTBELUI0DQpwY2kwOiB1bmtub3duIGNhcmQgREReMDg3 OCAodmVuZG9yPTB4MTA5ZSwgZGV2PTB4MDg3OCkgYXQgOS4xIGlycSAxNw0K eGwwOiA8M0NvbSAzYzkwNUItVFggRmFzdCBFdGhlcmxpbmsgWEw+IGlycSAx OCBhdCBkZXZpY2UgMTAuMCBvbiBwY2kwDQp4bDA6IEV0aGVybmV0IGFkZHJl c3M6IDAwOjEwOjVhOmQ3OmRkOjljDQp4bDA6IGF1dG9uZWcgY29tcGxldGUs IGxpbmsgc3RhdHVzIGdvb2QgKGhhbGYtZHVwbGV4LCAxMDBNYnBzKQ0KcGNt MDogPEF1ZGlvUENJIEVTMTM3MD4gaXJxIDE5IGF0IGRldmljZSAxMS4wIG9u IHBjaTANCnBjbTA6IHVzaW5nIEkvTyBzcGFjZSByZWdpc3RlciBtYXBwaW5n IGF0IDB4ZDgwMA0KQWRkIGhvb2sgInBjbSByZXN1bWUgaGFuZGxlciINCkFk ZCBob29rICJwY20gc3VzcGVuZCBoYW5kbGVyIg0KYWhjMDogPEFkYXB0ZWMg YWljNzg5NSBVbHRyYSBTQ1NJIGFkYXB0ZXI+IGlycSAxNiBhdCBkZXZpY2Ug MTIuMCBvbiBwY2kwDQphaGMwOiBhaWM3ODk1IFdpZGUgQ2hhbm5lbCBBLCBT Q1NJIElkPTcsIDE2LzI1NSBTQ0JzDQphaGMxOiA8QWRhcHRlYyBhaWM3ODk1 IFVsdHJhIFNDU0kgYWRhcHRlcj4gaXJxIDE2IGF0IGRldmljZSAxMi4xIG9u IHBjaTANCmFoYzE6IFVzaW5nIGxlZnQgb3ZlciBCSU9TIHNldHRpbmdzDQph aGMxOiBhaWM3ODk1IFdpZGUgQ2hhbm5lbCBCLCBTQ1NJIElkPTcsIDE2LzI1 NSBTQ0JzDQpmZGMwOiA8TkVDIDcyMDY1QiBvciBjbG9uZT4gYXQgcG9ydCAw eDNmMC0weDNmNyBpcnEgNiBkcnEgMiBvbiBpc2EwDQpmZGMwOiBGSUZPIGVu YWJsZWQsIDggYnl0ZXMgdGhyZXNob2xkDQpmZDA6IDwxNDQwLUtCIDMuNSIg ZHJpdmU+IG9uIGZkYzAgZHJpdmUgMA0KYXRrYmRjMDogPGtleWJvYXJkIGNv bnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwLTB4NmYgb24gaXNhMA0K YXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGZsYWdzIDB4MSBpcnEgMSBvbiBhdGti ZGMwDQpwc20wOiA8UFMvMiBNb3VzZT4gaXJxIDEyIG9uIGF0a2JkYzANCnBz bTA6IG1vZGVsIEdlbmVyaWMgUFMvMiBtb3VzZSwgZGV2aWNlIElEIDANCnZn YTA6IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYjAtMHgzZGYgaW9t ZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCnNjMDogPFN5c3RlbSBjb25z b2xlPiBvbiBpc2EwDQpzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywg ZmxhZ3M9MHgyMDA+DQpzaW8wIGF0IHBvcnQgMHgzZjgtMHgzZmYgaXJxIDQg ZmxhZ3MgMHgxMCBvbiBpc2EwDQpzaW8wOiB0eXBlIDE2NTUwQQ0Kc2lvMSBh dCBwb3J0IDB4MmY4LTB4MmZmIGlycSAzIG9uIGlzYTANCnNpbzE6IHR5cGUg MTY1NTBBDQpwcGMwIGF0IHBvcnQgMHgzNzgtMHgzN2YgaXJxIDcgb24gaXNh MA0KcHBjMDogR2VuZXJpYyBjaGlwc2V0IChOSUJCTEUtb25seSkgaW4gQ09N UEFUSUJMRSBtb2RlDQpscHQwOiA8Z2VuZXJpYyBwcmludGVyPiBvbiBwcGJ1 cyAwDQpscHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCkFQSUNfSU86IFRl c3RpbmcgODI1NCBpbnRlcnJ1cHQgZGVsaXZlcnkNCkFQSUNfSU86IHJvdXRp bmcgODI1NCB2aWEgcGluIDINCklQIHBhY2tldCBmaWx0ZXJpbmcgaW5pdGlh bGl6ZWQsIGRpdmVydCBlbmFibGVkLCBydWxlLWJhc2VkIGZvcndhcmRpbmcg ZW5hYmxlZCwgZGVmYXVsdCB0byBhY2NlcHQsIHVubGltaXRlZCBsb2dnaW5n DQpXYWl0aW5nIDEwIHNlY29uZHMgZm9yIFNDU0kgZGV2aWNlcyB0byBzZXR0 bGUNClNNUDogQVAgQ1BVICMxIExhdW5jaGVkIQ0KY2hhbmdpbmcgcm9vdCBk ZXZpY2UgdG8gZGEwczJhDQpkYTEgYXQgYWhjMSBidXMgMCB0YXJnZXQgMSBs dW4gMA0KZGExOiA8UXVhbnR1bSBYUDM0MzAwVyBMOTE1PiBGaXhlZCBEaXJl Y3QgQWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpkYTE6IDIwLjAwME1CL3MgdHJh bnNmZXJzICgxMC4wMDBNSHosIG9mZnNldCA4LCAxNmJpdCksIFRhZ2dlZCBR dWV1ZWluZyBFbmFibGVkDQpkYTE6IDQxMDFNQiAoODM5OTUyMCA1MTIgYnl0 ZSBzZWN0b3JzOiA2NEggMzJTL1QgNDEwMUMpDQpkYTAgYXQgYWhjMSBidXMg MCB0YXJnZXQgMCBsdW4gMA0KZGEwOiA8TUlDUk9QIDMzOTFXUyBYNTAyPiBG aXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpkYTA6IDQwLjAw ME1CL3MgdHJhbnNmZXJzICgyMC4wMDBNSHosIG9mZnNldCA4LCAxNmJpdCks IFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpkYTA6IDg2ODFNQiAoMTc3ODAw NTggNTEyIGJ5dGUgc2VjdG9yczogNjRIIDMyUy9UIDg2ODFDKQ0KY2QxIGF0 IGFoYzAgYnVzIDAgdGFyZ2V0IDUgbHVuIDANCmNkMTogPFRPU0hJQkEgQ0Qt Uk9NIFhNLTM3MDFUQSAzNjE1PiBSZW1vdmFibGUgQ0QtUk9NIFNDU0ktMiBk ZXZpY2UgDQpjZDE6IDQuOTAxTUIvcyB0cmFuc2ZlcnMgKDQuOTAxTUh6LCBv ZmZzZXQgMTUpDQpjZDE6IEF0dGVtcHQgdG8gcXVlcnkgZGV2aWNlIHNpemUg ZmFpbGVkOiBOT1QgUkVBRFksIE1lZGl1bSBub3QgcHJlc2VudA0KY2QwIGF0 IGFoYzAgYnVzIDAgdGFyZ2V0IDMgbHVuIDANCmNkMDogPFlBTUFIQSBDUlc0 NDE2UyAxLjBlPiBSZW1vdmFibGUgQ0QtUk9NIFNDU0ktMiBkZXZpY2UgDQpj ZDA6IDguMzMzTUIvcyB0cmFuc2ZlcnMgKDguMzMzTUh6LCBvZmZzZXQgMTUp DQpjZDA6IGNkIHByZXNlbnQgWzE3NzA4MCB4IDIwNDggYnl0ZSByZWNvcmRz XQ0K --0-841842983-935750025=:40664-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 3:46:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id EA77815DE5 for ; Fri, 27 Aug 1999 03:46:27 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id NAA63649; Fri, 27 Aug 1999 13:44:47 +0300 (EEST) (envelope-from will) To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: "The Matrix" screensaver, v.0.2 References: <4520.935745765@critter.freebsd.dk.newsgate.clinet.fi> From: Ville-Pertti Keinonen Date: 27 Aug 1999 13:44:46 +0300 In-Reply-To: Poul-Henning Kamp's message of "27 Aug 1999 12:24:52 +0300" Message-ID: <86pv09wli9.fsf@not.demophon.com> Lines: 15 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > The third difference is that we only use jurys in murder cases, > we fully realize the ability of a showman-laywer to sway a jury, > therefore we don't use them, unless the issue is the gravest > crime we know off. That doesn't seem quite valid, it shouldn't be considered a good thing if a "showman-lawyer" (on either side) is permitted to sway a jury for a murder-trial. Of course this is getting off topic, or have there been any FreeBSD-current related homicides that I haven't heard about? ;--) Have there even been any actual trials directly related to FreeBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 3:51:37 1999 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 8ED6F14DA9 for ; Fri, 27 Aug 1999 03:51:36 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-63.ucdavis.edu [169.237.16.191]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id DAA93622; Fri, 27 Aug 1999 03:49:00 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id DAA49085; Fri, 27 Aug 1999 03:49:01 -0700 (PDT) (envelope-from obrien) Date: Fri, 27 Aug 1999 03:49:00 -0700 From: "David O'Brien" To: Alex Zepeda Cc: Wilko Bulte , freebsd-current@FreeBSD.ORG Subject: Re: Softupdates reliability? Message-ID: <19990827034900.A49059@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199908251808.UAA00709@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 4.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 > Doesn't Asus make an AT formfactor Super 7 motherboard w/ a 100mhz bus? Yes, but it is shy on card slots. The Tyan s1590 Trinity-AT100 is the has the most card slots of any of today's AT formfactor Super7 boards I am aware of. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 3:53:25 1999 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 3223D14DA9 for ; Fri, 27 Aug 1999 03:53:22 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id MAA04973; Fri, 27 Aug 1999 12:52:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ville-Pertti Keinonen Cc: current@freebsd.org Subject: Re: "The Matrix" screensaver, v.0.2 In-reply-to: Your message of "27 Aug 1999 13:44:46 +0300." <86pv09wli9.fsf@not.demophon.com> Date: Fri, 27 Aug 1999 12:52:46 +0200 Message-ID: <4971.935751166@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <86pv09wli9.fsf@not.demophon.com>, Ville-Pertti Keinonen writes: > >Poul-Henning Kamp writes: > >> The third difference is that we only use jurys in murder cases, >> we fully realize the ability of a showman-laywer to sway a jury, >> therefore we don't use them, unless the issue is the gravest >> crime we know off. > >That doesn't seem quite valid, it shouldn't be considered a good thing >if a "showman-lawyer" (on either side) is permitted to sway a jury for >a murder-trial. I didn't say I agreed, I merely pointed out that we had limited the problem significantly. In Denmark a couple of interesting cases over the last five years have putj the use of a jury for even murder cases in the limelight. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 4:42:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id AA90B14E38 for ; Fri, 27 Aug 1999 04:42:24 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id OAA01658; Fri, 27 Aug 1999 14:40:23 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Fri, 27 Aug 1999 14:40:23 +0300 (EEST) From: Adrian Penisoara To: Peter Wemm Cc: Chuck Robey , Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <19990822213441.EB76D1C1F@overcee.netplex.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 Hi, On Mon, 23 Aug 1999, Peter Wemm wrote: > > Maybe we *should* go approach the producers? I have gone to that movie > > several times, and I keep on enjoying it, so this is GOOD PR for them. > > Tell them there will be a reference to the movie web site or something. ;-) Actually the FreeBSD site already has a reference to them (they used an CG Render Farm of 32 Dual processor FreeBSD systems): http://www.freebsd.ady.ro/news/press-rel-1.html Read all about it ! ;-) > > > Cheers, > -Peter > Take care, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 4:42:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id DED8415596 for ; Fri, 27 Aug 1999 04:42:39 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id OAA01707; Fri, 27 Aug 1999 14:42:56 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Fri, 27 Aug 1999 14:42:56 +0300 (EEST) From: Adrian Penisoara To: Peter Wemm Cc: Chuck Robey , Ollivier Robert , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, > > http://www.freebsd.ady.ro/news/press-rel-1.html Whoops, that should have been http://www.freebsd.org/news/press-rel-1.html for all you fellows out there (the former is my local mirror)... Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 9: 8: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 9AA0C15E01 for ; Fri, 27 Aug 1999 09:07:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA31629; Fri, 27 Aug 1999 09:05:08 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Aug 1999 09:05:08 -0700 (PDT) From: Matthew Dillon Message-Id: <199908271605.JAA31629@apollo.backplane.com> To: Poul-Henning Kamp Cc: Greg Lehey , Christopher Masto , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) References: <3839.935736904@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Greg, : :4K is probably too conservative, it only applies if you have a :swap-backed vn device at the bottom, which would be a truly :weird thing to do with vinum. : :Don't spend too much time on tracking the sector size yet. I think :the si_bsize stuff needs some thinking before we do more with it. : :Poul-Henning There's nothing wrong with the si_bsize stuff, but it got broken temporarily with all the dev_t work. All that really needs to be done is to reset the block sizes to their defaults when the last reference to the device goes away. This way reconfigurable devices do not have to reload the defaults prior to making adjustments based on the actual sector size of the device. There is no better way to do it. specfs and physio need to know how to realign byte-aligned I/O requests for physical devices. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 9:52:10 1999 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 E04D414C11 for ; Fri, 27 Aug 1999 09:52:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA06125; Fri, 27 Aug 1999 18:47:50 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Greg Lehey , Christopher Masto , "John W. DeBoskey" , julian@whistle.com, freebsd-current@FreeBSD.ORG Subject: Re: -current kernel problems (spec_getpages & vm_fault) In-reply-to: Your message of "Fri, 27 Aug 1999 09:05:08 PDT." <199908271605.JAA31629@apollo.backplane.com> Date: Fri, 27 Aug 1999 18:47:50 +0200 Message-ID: <6123.935772470@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908271605.JAA31629@apollo.backplane.com>, Matthew Dillon writes: >:Greg, >: >:4K is probably too conservative, it only applies if you have a >:swap-backed vn device at the bottom, which would be a truly >:weird thing to do with vinum. >: >:Don't spend too much time on tracking the sector size yet. I think >:the si_bsize stuff needs some thinking before we do more with it. >: >:Poul-Henning > > There's nothing wrong with the si_bsize stuff, but it got > broken temporarily with all the dev_t work. Well, it was obviously broken both in ccd and vinum before too, just not the same way. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 10:52:37 1999 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 7E5F2154C1 for ; Fri, 27 Aug 1999 10:52:36 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 0AB571C40; Fri, 27 Aug 1999 12:55:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 07956382F; Fri, 27 Aug 1999 12:55:39 -0400 (EDT) Date: Fri, 27 Aug 1999 12:55:39 -0400 (EDT) From: Bill Fumerola To: Ville-Pertti Keinonen Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <86pv09wli9.fsf@not.demophon.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 27 Aug 1999, Ville-Pertti Keinonen wrote: > Of course this is getting off topic, or have there been any > FreeBSD-current related homicides that I haven't heard about? ;--) > Have there even been any actual trials directly related to FreeBSD? There was a signup sheet going around at the last 'Brucified Anonymous' meeting, but I guess that never materialized. :-> -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 11: 6:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id CDD3F15516 for ; Fri, 27 Aug 1999 11:06:45 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 69F581912; Fri, 27 Aug 1999 20:07:02 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 66F3F49D3; Fri, 27 Aug 1999 20:07:02 +0200 (CEST) Date: Fri, 27 Aug 1999 20:07:02 +0200 (CEST) From: Andrzej Bialecki To: "Jordan K. Hubbard" Cc: Mike Smith , "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: "The Matrix" screensaver, v.0.2 In-Reply-To: <953.935636594@localhost> 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, 25 Aug 1999, Jordan K. Hubbard wrote: > I'm sorry you got so beaten up over this one. All due respect to the > contributors aside, I think we have too many old women around here, > all shrieking and holding up their skirts at the rumor of a mouse > somewhere in the building. :) As I said, I'm done with the subject. it's on my web page on freefall. Anyone wishing to do something with it can grab it and do whatever he wants (within terms of BSD license). 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 Fri Aug 27 11:26:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.psa.at (darkstar.psa.at [194.152.163.137]) by hub.freebsd.org (Postfix) with ESMTP id 0ED2C15547 for ; Fri, 27 Aug 1999 11:26:21 -0700 (PDT) (envelope-from entropy@compufit.at) Received: from uvo-124.univie.ac.at ([131.130.230.124]) by darkstar.psa.at with esmtp (Exim 3.02 #3) id 11KQhP-0008s8-00 for freebsd-current@freebsd.org; Fri, 27 Aug 1999 20:26:03 +0200 Date: Fri, 27 Aug 1999 14:56:24 +0200 From: Alexander Sanda X-Mailer: Brieftaube V 2.666 Organization: Nicht die Geringste X-Priority: 3 Message-ID: To: freebsd-current@freebsd.org Subject: Re[2]: "The Matrix" screensaver, v.0.2 In-reply-To: <8062.935743977@localhost> References: <8062.935743977@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27.08.1999, 10:52, Jordan K. Hubbard wrote: > Sorry, I've lived in Europe, you can't pull that one on me. :) > In Germany, for example, it's possible to sue someone simply for > sticking their finger against their forehead. The myth that only the > U.S. is litigious is just that, a myth. Europeans sue the crap out of > one another all the time, and for issues just as silly. :) True. A well known german lawyer is currently about to sue a few webhosters for using the name "Webspace" in their ads. (Yes, some silly - or maybe not-so-silly - dude has registered the word "Webspace" as a trademark). In this case, the problem are not the lawyers, but the fact that you can actually register trademarks like this one. Others have been threatened with lawsuits for using the word "Triton" in mainboard advertisments a few years ago, because "Triton" sounds very similar to the registered trademark "Tricon". -- # My PGP public key (ID=7A2AFB8F): http://darkstar.psa.at/aspgp.txt # # According to rumours, MS finally decided to delay the release of the # # long-awaited Windows 2000 until the first quarter of 1901. # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 14:52: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.etrust.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id A07B31564D for ; Fri, 27 Aug 1999 14:51:58 -0700 (PDT) (envelope-from osa@ozz.etrust.ru) Received: by ozz.etrust.ru (Postfix, from userid 1000) id 461BB139; Sat, 28 Aug 1999 01:50:24 +0400 (MSD) Date: Sat, 28 Aug 1999 01:50:24 +0400 From: "Sergey A. Osokin" To: freebsd-current@FreeBSD.org Subject: make buildworld failed... Message-ID: <19990828015024.A28817@ozz.etrust.ru> Reply-To: osa@etrust.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsup my -current sources, i try to make build world... ld -N -e start -Ttext 0x100000 -o btxldr.out btxldr.o objcopy -S -O binary btxldr.out btxldr ===> sys/boot/i386/btx/lib as -elf -o btxcsu.o /usr/src/sys/boot/i386/btx/lib/btxcsu.s as -elf -o btxsys.o /usr/src/sys/boot/i386/btx/lib/btxsys.s as -elf -o btxv86.o /usr/src/sys/boot/i386/btx/lib/btxv86.s ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o ===> sys/boot/i386/boot2 (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o objcopy -S -O binary boot1.out boot1 dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- What can i do? Rgdz, Osokin Sergey aka oZZ, osa@FreeBSD.org.ru osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 16: 2:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id CC34B14E0C for ; Fri, 27 Aug 1999 16:02:14 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id BAA17824 for freebsd-current@FreeBSD.org; Sat, 28 Aug 1999 01:01:03 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id CFAE0870A; Sat, 28 Aug 1999 00:29:58 +0200 (CEST) Date: Sat, 28 Aug 1999 00:29:58 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.org Subject: Re: make buildworld failed... Message-ID: <19990828002958.A68885@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.org References: <19990828015024.A28817@ozz.etrust.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <19990828015024.A28817@ozz.etrust.ru>; from Sergey A. Osokin on Sat, Aug 28, 1999 at 01:50:24AM +0400 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5543 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Sergey A. Osokin: > After cvsup my -current sources, i try to make build world... > ===> sys/boot/i386/boot2 > (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o I get a different error: dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null (cd /src/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o *** Error code 1 cc -elf -I/src/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -Os -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -I/usr/obj/src/src/tmp/usr/include -c /src/src/sys/boot/i386/boot2/boot2.c (cd /src/src/sys/boot/i386/boot2; m4 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 sio.s) | as -o sio.o 1 error *** Error code 2 CVSup from two hours ago. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 16:15:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F11114EDB for ; Fri, 27 Aug 1999 16:15:24 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-14.iptelecom.net.ua [212.42.74.142]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA19751; Sat, 28 Aug 1999 02:14:40 +0300 (EEST) Message-ID: <37C71CBE.17B3EF72@altavista.net> Date: Sat, 28 Aug 1999 02:18:22 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: osa@etrust.ru Cc: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld failed... References: <19990828015024.A28817@ozz.etrust.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Sergey A. Osokin" wrote: > After cvsup my -current sources, i try to make build world... > > ld -elf -i -o crt0.o btxcsu.o btxsys.o btxv86.o > ===> sys/boot/i386/boot2 > (cd /usr/src/sys/boot/i386/boot2; m4 -DFLAGS=0 boot1.m4 boot1.s) | as -o boot1.o > ld -nostdlib -static -N -e start -Ttext 0x7c00 -o boot1.out boot1.o > objcopy -S -O binary boot1.out boot1 > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > *** Error code 1 > > Stop in /usr/src/sys/boot/i386/boot2.-- > > What can i do? Probably it consequences of recent dd changes... -Max To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 16:47:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (zen.holonet.net [198.207.169.5]) by hub.freebsd.org (Postfix) with ESMTP id D889D15652 for ; Fri, 27 Aug 1999 16:46:39 -0700 (PDT) (envelope-from adamw@holonet.net) Received: from (adamw@localhost) by holonet.net (Adam Wight) id QAA15816; Fri, 27 Aug 1999 16:42:00 -0700 Message-Id: <199908272342.QAA15816@holonet.net> Subject: Re: make buildworld failed... To: freebsd-current@freebsd.org Date: Fri, 27 Aug 99 16:41:59 PDT From: Adam Wight In-Reply-To: <37C71CBE.17B3EF72@altavista.net>; from "Maxim Sobolev" at Aug 28, 99 2:18 am Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > > *** Error code 1 > Probably it consequences of recent dd changes... So I'm not entirely alone, then. I actually kernel panic quite reliably every time I try to dd onto a floppy. I can dd from one file to another without a problem, and floppy access in general works as always. What debugging information would be relevant? -adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 21:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id AF96F15512 for ; Fri, 27 Aug 1999 21:50:56 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id VAA95500 for ; Fri, 27 Aug 1999 21:49:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908280449.VAA95500@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Mucho Bandwith Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Aug 1999 21:49:01 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The claim of this arcticle is that the researchers are at a lost of what to do with their CA*Net3 network (80 giga bits /second ). http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) I am sure that some on the list can figure out other creative uses like clustering. Enjoy -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 27 23: 5:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (Postfix) with ESMTP id AF46F14F8F for ; Fri, 27 Aug 1999 23:05:33 -0700 (PDT) (envelope-from josh@zipperup.org) Received: from asherah.dyndns.org (HSE-Toronto-ppp52150.sympatico.ca [209.226.241.231]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id CAA06737; Sat, 28 Aug 1999 02:06:05 -0400 (EDT) Received: by asherah.dyndns.org (Postfix, from userid 701954) id 2ABC432602; Sat, 28 Aug 1999 02:04:11 -0400 (EDT) Date: Sat, 28 Aug 1999 02:04:11 -0400 From: Josh Tiefenbach To: Amancio Hasty Cc: current@freebsd.org Subject: Re: Mucho Bandwith Message-ID: <19990828020410.A87850@zipperup.org> References: <199908280449.VAA95500@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908280449.VAA95500@rah.star-gate.com>; from Amancio Hasty on Fri, Aug 27, 1999 at 09:49:01PM -0700 Organization: What Organization? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html > > Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) Significantly less than what its doing now. What the article fails to mention, is that (last I heard) CA*Net3 is *not* connected to the Internet at large. Currently, it only connects universities and research institutions within Canada. AFAIK, there aren't any real plans to patch it into the global 'net. josh -- C'est-ci n'est pas un .sig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 0:14:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1F05614DAA for ; Sat, 28 Aug 1999 00:14:08 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id AAA96350; Sat, 28 Aug 1999 00:10:43 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908280710.AAA96350@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Josh Tiefenbach Cc: current@freebsd.org Subject: Re: Mucho Bandwith In-reply-to: Your message of "Sat, 28 Aug 1999 02:04:11 EDT." <19990828020410.A87850@zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Aug 1999 00:10:43 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, is up to you guys to decide or create a useful use for the network . My take from the article is that the researchers were open to suggestions and I bet that the researcher wil be willing to show the results of large scale distributed network processing and even brag of why it can not be easily reproduce in other semi-public or public networks 8) Cheers > > http://abcnews.go.com/sections/tech/CuttingEdge/canadanet990827.html > > > > Hmmm... I wonder what would happen if ftp.freebsd.org was moved to CA*Net3 8) > > Significantly less than what its doing now. > > What the article fails to mention, is that (last I heard) CA*Net3 is *not* > connected to the Internet at large. > > Currently, it only connects universities and research institutions within > Canada. AFAIK, there aren't any real plans to patch it into the global 'net. > > josh > > -- > C'est-ci n'est pas un .sig -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 0:45:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 39E9714F0D for ; Sat, 28 Aug 1999 00:45:18 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA01775; Sat, 28 Aug 1999 00:39:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908280739.AAA01775@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: michael_class@gmx.net Cc: current@freebsd.org Subject: Re: current-APM causes panic on SMP-System In-reply-to: Your message of "Fri, 27 Aug 1999 12:33:45 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Aug 1999 00:39:27 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > since the apm-code was changed to use the generic bios-call interface > (dated around 1999/07/28) my FreeBSD-4.0-current system panics when I do > an "apmconf -e". This has not changed since then. I reproduced it with > a very current System (1999/08/25) today. > > The system is a Dual-Proc GigaByte 6BXDS-MB with 2x350Mhz PII and 256MB-RAM. > For further information I have added the Config-File and dmesg-output. This is a known bug in the generic BIOS code on SMP systems; I have a patch in hand and will be committing it soon. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 1: 0:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id EED5814F0D for ; Sat, 28 Aug 1999 01:00:50 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-152.skylink.it [194.185.55.152]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id JAA13385; Sat, 28 Aug 1999 09:59:20 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id HAA04125; Sat, 28 Aug 1999 07:59:50 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sat, 28 Aug 1999 07:59:50 GMT Date: Sat, 28 Aug 1999 09:59:49 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Adam Wight Cc: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld failed... In-Reply-To: <199908272342.QAA15816@holonet.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 Let me guess, the kernel panic ends up in a division by zero error when writing to floppy in _qdivrem. Haven't had time to script that panic, but will do next week. Nick On Fri, 27 Aug 1999, Adam Wight wrote: > > > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > > > *** Error code 1 > > > Probably it consequences of recent dd changes... > > So I'm not entirely alone, then. I actually kernel panic quite reliably every > time I try to dd onto a floppy. I can dd from one file to another without > a problem, and floppy access in general works as always. > > What debugging information would be relevant? > > -adam > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 1:40:34 1999 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 3163014DA7; Sat, 28 Aug 1999 01:40:31 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA30780; Sat, 28 Aug 1999 01:39:17 -0700 (PDT) (envelope-from green@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: green owned process doing -bs Date: Sat, 28 Aug 1999 01:39:17 -0700 (PDT) From: "Brian F. Feldman" To: Adam Wight Cc: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld failed... In-Reply-To: <199908272342.QAA15816@holonet.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, 27 Aug 1999, Adam Wight wrote: > > > dd if=/dev/zero of=boot2.ldr bs=512 count=1 2>/dev/null > > > *** Error code 1 > > > Probably it consequences of recent dd changes... Sorry about that! Instead of relying on the kernel being newer than the world and haveing the new ioctl FIODTYPE, dd now only warns if the ioctl doesn't work. > > So I'm not entirely alone, then. I actually kernel panic quite reliably every > time I try to dd onto a floppy. I can dd from one file to another without > a problem, and floppy access in general works as always. > > What debugging information would be relevant? That sounds like it could have just been fixed by phk. If it's not that and is the writing past the end of a block device issue, use the character device instead. > > -adam > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian Fundakowski Feldman / "Any sufficiently advanced bug is \ green@FreeBSD.org | indistinguishable from a feature." | FreeBSD: The Power to Serve! \ -- Rich Kulawiec / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 2:30: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 45FAD15397 for ; Sat, 28 Aug 1999 02:29:30 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id LAA16602 for ; Sat, 28 Aug 1999 11:28:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908280928.LAA16602@gratis.grondar.za> To: current@freebsd.org Subject: Crypto updates coming! Date: Sat, 28 Aug 1999 11:28:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All! I have got a $#|7load of crypto updates that I'd like to commit; they are all over my tree, so let me describe what they do, and anyone who wishes to review any part of them can get the appropriate bits. 1) Revisit the way libscrypt/libdescript get built. This is partially based on Brandon Gillespie's work, and is also inspired by what Kris Kennaway is trying to do, although it contains very little of their work. It is more a framework change to ease future expansion and to clean up the area. I am trying to reduce the size of the unexportable areas as well. 2) Upgrade compile_et to the latest offering from KTH in Sweden. This is needed for the new KerberosIV/eBones and Kerberos5/Heimdal. This will go into src/contrib. This code is radically different from MIT compile_et, but compatible with it. 3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does not hurt anything else. This will go into src/crypto. 4) Upgrade our KerberosIV to KTH's latest offering (1.0pre5). 5) Various fixes to ease the import of Kerberos5/Heimdal when the compatible version is released. Kerberos5 will be in a directory structure analagous to the current kerberosIV. Producing complete diffs may be a bit of a pain, but I can come up with any part of the above without too much of a hassle. M To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 2:44:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 7DB7415E0A; Sat, 28 Aug 1999 02:44:01 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id KAA71898; Sat, 28 Aug 1999 10:27:42 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id LAA18231; Fri, 27 Aug 1999 11:07:16 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Fri, 27 Aug 1999 11:07:16 +0100 From: Nik Clayton To: Satoshi - Ports Wraith - Asami Cc: "Jordan K. Hubbard" , Nik Clayton , jack , current@freebsd.org, doc@freebsd.org Subject: Re: Docs blows up make release Message-ID: <19990827110716.B15526@kilt.nothing-going-on.org> References: <16783.935616425@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Satoshi - Ports Wraith - Asami on Thu, Aug 26, 1999 at 06:46:38PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, Satoshi, Just a reminder: I have *no* objection to the ports tree being used to build packages of the documentation, as long as the maintenance of those ports is assigned to individuals, and not the FDP (and, more specifically, me). However, I think that another mechanism, one that's wholly within doc/, will be useful, for the reasons I've already outlined. On Thu, Aug 26, 1999 at 06:46:38PM -0700, Satoshi - Ports Wraith - Asami wrote: > Another advantage of having them in the ports tree is the build > checking done at regular intervals. OK. But since the doc/ packages will also be being built daily (first on freefall, and then, when I get the time, on the docs.freebsd.org machine (usw1?) that jkh has been talking about, the same comment applies. > All the japanese/handbook stuff > that's going on right now, these are the problems of the > textproc/docbook* ports (missing files from PLIST, missing > dependencies). People installing these from packages will see the > exact same problem when they try to build the handbook (with or > without the japanese/handbook port). Hang on a second. Are we talking about different things here? I want the formatted documentation available as packages so that those people that want formatted docs, but who have neither the time, the inclination, or the machine horsepower to download the textproc/docproj port have a very easy way of installing and managing formatted documentation -- specifically, pkg_add(1). If people want to go and build the documentation from scratch themselves, they should do so by downloading the doc/ repository, and running make(1) in there, not by going through the ports system. That just adds an additional layer of complexity. [ Obviously, people will have to go through the ports system to download the applications they are using to build the docs, or go through the hassle of configuring and installing them themselves ] > * > Putting the package building rules in the doc/ Makefiles also (and this > * > is just my personal opinion) makes it easier for people to see how the > * > documentation packages are built. The ports Makefile structure is a > * > marvel, but it contains a lot of code that's not necessary for building > * > documentation packages (the "automagically add man pages to the PLIST > * > i" code, for example) that makes it more difficult for the interested > * > learner to browse and understand what's going on. > * > * Now this is a point which is more germin. So, you figure on making a > * similar sort of "package" target under doc? I guess it really doesn't > * matter where these things live, as long as it's still automated.. > > The chief concern I have is that this might result in yet another > place you (Jordan) have to pick up stuff from before the release. This shouldn't matter, should it? As long as the automated doc package building puts the files somewhere sensible (in distfiles/ on wcarchive?) it'll get picked up. Remember that the long term plan is to migrate the docs out of the release as a separate distribution, and in to their own packages, so that at sysinstall time the user can pick and choose which docs to install at the level of the individual packages (presumably, with some additional 'meta' choices, that let them say things like "All the English docs, in HTML and PDF, and the Spanish docs in HTML"). Since this (the package building, and sysinstall changes) are not going to be ready for 3.3-RELEASE, I think we should concentrate on ensuring that "make release" works with the new doc/ structure, and that sysinstall knows about the correct locations of the FAQ and Handbook in the new structure. In the meantime, I can continue adding and tweaking (with input from anybody else that's interested) the package building rules under doc/, and then set up a system that automatic builds formatted versions of the latest documentation daily (or weekly, depending on how rapidly the documentation is changing, and how badly people want it). We can then run with this for a bit, see how it works out, and that gives us plenty of time to consider removing the doc distribution (in favour of the packages) in time for 4.0-RELEASE. The ports tree can continue having a japanese/handbook entry for as long as they want. As long as I don't have to support it, I don't care :-) N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 7:13:44 1999 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 AA51A14D87 for ; Sat, 28 Aug 1999 07:13:41 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA12959 for ; Sat, 28 Aug 1999 16:12:27 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: PC98/GENERIC98 compile problem From: Poul-Henning Kamp Date: Sat, 28 Aug 1999 16:12:27 +0200 Message-ID: <12957.935849547@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG schizo# make cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h -elf ../../pci/if_tl.c ../../pci/if_tl.c:226: miibus_if.h: No such file or directory *** Error code 1 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 8: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id E7C571565C; Sat, 28 Aug 1999 08:05:24 -0700 (PDT) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id AAA25949; Sun, 29 Aug 1999 00:05:23 +0900 (JST) To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: PC98/GENERIC98 compile problem From: KATO Takenori In-Reply-To: Your message of "Sat, 28 Aug 1999 16:12:27 +0200" <12957.935849547@critter.freebsd.dk> References: <12957.935849547@critter.freebsd.dk> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990829000452N.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 29 Aug 1999 00:04:52 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > schizo# make > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h -elf ../../pci/if_tl.c > ../../pci/if_tl.c:226: miibus_if.h: No such file or directory > *** Error code 1 Fixed. Thanks! -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | ++++ FreeBSD(98) 3.2: Rev. 01 available! |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 2.2.8: Rev. 02 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 10:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 094D2155EE; Sat, 28 Aug 1999 10:34:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EE3B51CD8D3; Sat, 28 Aug 1999 10:34:40 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Sat, 28 Aug 1999 10:34:40 -0700 (PDT) From: Kris Kennaway To: Mark Murray Cc: current@freebsd.org Subject: Re: Crypto updates coming! In-Reply-To: <199908280928.LAA16602@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Aug 1999, Mark Murray wrote: > 3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does > not hurt anything else. This will go into src/crypto. You might also like to turn on the x86 assembler code (it's only for pentiums, I think, so would have to be a non-default option :-(. It gives a performance increase of a factor of 3 or so, ISTR. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 10:38:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 80D71155EE; Sat, 28 Aug 1999 10:38:21 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id TAA18595; Sat, 28 Aug 1999 19:38:13 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908281738.TAA18595@gratis.grondar.za> To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Crypto updates coming! Date: Sat, 28 Aug 1999 19:38:12 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 28 Aug 1999, Mark Murray wrote: > > > 3) Upgade libdes. This is mainly for KerberosIV and Kerberos5. It does > > not hurt anything else. This will go into src/crypto. > > You might also like to turn on the x86 assembler code (it's only for > pentiums, I think, so would have to be a non-default option :-(. It gives > a performance increase of a factor of 3 or so, ISTR. I'll bring in that code, but only enable it later. 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 Aug 28 11:18:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 8030B14CFC for ; Sat, 28 Aug 1999 11:18:43 -0700 (PDT) (envelope-from rock@dead-end.net) Received: from dead-end.net (p3E9C367E.dip.t-dialin.net [62.156.54.126]) by dead-end.net (8.9.3/DEAD-END/1999022000) with ESMTP id UAA91228 for ; Sat, 28 Aug 1999 20:17:56 +0200 (CEST) (envelope-from rock@dead-end.net) Message-ID: <37C827ED.2CD4CE5@dead-end.net> Date: Sat, 28 Aug 1999 20:18:21 +0200 From: "D. Rock" X-Mailer: Mozilla 4.6 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: current@freebsd.org Subject: RealTek 8139 problems 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 get some strange networking results with my RealTek 8139 card. I don't know how long these problems exist in the kernel, because they only showed up after some change in my network setup. I got a third PC for testing and now needed a hub to connect all my PCs together. I used to have an UTP x-over cable and this setup worked Ok. Now I hooked the 3 PCs together with an 10/100 MBit Hub. This is now my configuration: PC 1: RealTek 8139 PC 2: Intel EtherEpress Pro 100B PC 3: RealTek 8029 (the new machine) PC 1 and PC 3 are running FreeBSD, PC 2 usually runs Windows 98, but I could also boot Solaris for testing. Under normal Circumstances, the communication is Ok between all three machines, but sometimes the ethernet interface in the main machine (the 8139) wedges up. I cannot ping any other host. The only solution is taking the interface down and up again: ifconfig rl0 down; ifconfig rl0 up Enabling/disabling promiscuous mode also seems to help. I first thought it was a faulty hub, so I hooked up two PCs (RealTek 8139 + RealTek 8029) with the Xover cable again. But the problem persists. So the Hub seems to be Ok. There seem also to be plenty of mbufs available. netstat -m: 64/3808 mbufs in use: 56 mbufs allocated to data 8 mbufs allocated to packet headers 1/48/512 mbuf clusters in use (current/peak/max) 572 Kbytes allocated to network (1% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines I finally managed to easily reproduce the behaviour. Just run two flood pings to the same machine at once. Interesting, that I have to flood ping PC 3 (10BaseT) to wedge up the machine. If I ping PC 2, nothing spectacular happens. The Driver does proper autonegotiation, but also changing the media manually to the correct values (media 100baseTX mediaopt half-duplex) doesn't help. Thanks for any hints. Daniel Some comments to the dmesg output below: I have disabled the secondary serial port, so every device should get its own IRQ. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #316: Tue Aug 24 23:58:54 CEST 1999 root@server:/usr/src/sys/compile/ROCK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 126906368 (123932K bytes) Preloaded elf kernel "kernel" at 0xc0316000. VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc02bed22 (1000022) VESA: Matrox Graphics Inc. npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ncr0: irq 11 at device 8.0 on pci0 pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 9.0 rl0: irq 3 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:02:8b:39 rl0: autoneg complete, link status good (half-duplex, 100Mbps) ata-pci0: irq 0 at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 Probing for PnP devices: atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sbxvi0 at port 0xffffffff drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] sbmidi0 at port 0x330 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] awe0 at port 0x620 on isa0 awe0: WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] isic0 at port 0x340 irq 10 flags 0x4 on isa0 isic0: AVM A1 or AVM Fritz!Card isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x1720) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x720, AddrB=0xf20) ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, unlimited logging DUMMYNET initialized (990811) i4b: ISDN call control device attached i4bisppp: 1 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4btel: 1 ISDN telephony interface device(s) attached i4brbch: 1 raw B channel access device(s) attached i4btrc: 1 ISDN trace device(s) attached ata0: master: setting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up UDMA2 mode on Aladdin chip OK ad1: ATA-4 disk at ata1 as master ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 31 depth queue, DMA mode Waiting 2 seconds for SCSI devices to settle sa0 at ncr0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers changing root device to wd0s1a cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da5 at ncr0 bus 0 target 5 lun 0 da5: Removable Direct Access SCSI-2 device da5: 3.300MB/s transfers da5: Attempt to query device size failed: NOT READY, Medium not present i4b: unit 0, assigned TEI = 111 = 0x6f To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 12:25:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (giskard.holonet.net [198.207.169.7]) by hub.freebsd.org (Postfix) with ESMTP id CD243150B3; Sat, 28 Aug 1999 12:25:52 -0700 (PDT) (envelope-from adamw@holonet.net) Received: from DialupEudora (adamw@localhost) by holonet.net (Adam Wight) with SMTP id MAA24729; Sat, 28 Aug 1999 12:24:30 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 28 Aug 1999 11:24:50 -0800 To: Nick Hibma , "Brian F. Feldman" From: adamw@holonet.net (Adam Wight) Subject: Re: make buildworld failed... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 27 Aug 1999, Nick Hibma wrote: >Let me guess, the kernel panic ends up in a division by zero error when >writing to floppy in _qdivrem. Yep, this would be it. On Sat, 28 Aug 1999, Brian F. Feldman wrote: >That sounds like it could have just been fixed by phk. If it's not that and >is the writing past the end of a block device issue, use the character >device instead. I'm afraid it's the latter problem. It crashes at line 414 of dd/conv.c, but I really don't see why. The arguments all look decent--it's only trying to write 512 bytes at a time, and everything looks just like it does during a character device write. I don't understand this area of the system well enough to do much useful debugging, but if anyone wants the particulars, this is 120% repeatable. -Adam Wight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 13:44:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id C503214CD5 for ; Sat, 28 Aug 1999 13:44:45 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id NAA86457; Sat, 28 Aug 1999 13:44:19 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37C84A26.4FC7EF7E@gorean.org> Date: Sat, 28 Aug 1999 13:44:22 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0826 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: current@freebsd.org Subject: Re: Crypto updates coming! References: <199908280928.LAA16602@gratis.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > Hello All! > > I have got a $#|7load of crypto updates that I'd like to commit; they > are all over my tree, so let me describe what they do, and anyone who > wishes to review any part of them can get the appropriate bits. Something that came up recently, both for me and someone else on the list is the ability to have DES libs in the system and still use MD5 passwords as the default. I have no idea how difficult this would be to do, but if someone has it in mind here's another vote in favor. Meanwhile the upgrades sound good to me, for what that's worth. :) Thanks, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 13:58:39 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id BC5BA14CBF; Sat, 28 Aug 1999 13:58:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 931C61CD8C8; Sat, 28 Aug 1999 13:58:38 -0700 (PDT) (envelope-from kris@hub.freebsd.org) Date: Sat, 28 Aug 1999 13:58:38 -0700 (PDT) From: Kris Kennaway To: Doug Cc: Mark Murray , current@freebsd.org Subject: Re: Crypto updates coming! In-Reply-To: <37C84A26.4FC7EF7E@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 Sat, 28 Aug 1999, Doug wrote: > Something that came up recently, both for me and someone else on the list > is the ability to have DES libs in the system and still use MD5 passwords > as the default. I have no idea how difficult this would be to do, but if > someone has it in mind here's another vote in favor. The replacement libcrypt code at http://www.physics.adelaide.edu.au/~kkennawa/crypt-990725.tar.gz allows this (and more), the only major downside is that it doesn't allow statically-linked binaries to use external crypt() modules (blowfish, etc). Traditional-format MD5 and DES are built-in so should work fine when statically-linked. I haven't had much feedback on this code so would like to hear how well it works for people. Unfortunately I can't correct any bugs at the moment until I get my computer (which is at this moment being unloaded from a plane at the airport :-) set up and back on the net, but I tested it a fair bit myself back in Australia. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 14:28:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 64C9C14E68; Sat, 28 Aug 1999 14:28:42 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id XAA19510; Sat, 28 Aug 1999 23:28:02 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908282128.XAA19510@gratis.grondar.za> To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Crypto updates coming! Date: Sat, 28 Aug 1999 23:28:01 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I haven't had much feedback on this code so would like to hear how well it > works for people. Unfortunately I can't correct any bugs at the moment > until I get my computer (which is at this moment being unloaded from a > plane at the airport :-) set up and back on the net, but I tested it a > fair bit myself back in Australia. It didn't work very well for me, because what I had had missing bits; also it did not fit into the framework I had already constructed. What will be there after the commit is IMVHO a good starting point for your code :-). 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 Aug 28 15:29: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.twcny.rr.com (mail1-1.nyroc.rr.com [24.92.226.139]) by hub.freebsd.org (Postfix) with ESMTP id A473314E4F for ; Sat, 28 Aug 1999 15:29:05 -0700 (PDT) (envelope-from reichman@twcny.rr.com) Received: from twcny.rr.com ([24.95.188.113]) by mail1.twcny.rr.com (Post.Office MTA v3.5.2 release 221 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Sat, 28 Aug 1999 18:28:54 -0400 Message-ID: <37C864FE.BD2DDB0E@twcny.rr.com> Date: Sat, 28 Aug 1999 18:38:54 -0400 From: "Mark S. Reichman" X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: "The Matrix" screensaver, v.0.2 References: <4520.935745765@critter.freebsd.dk> <37C8647E.DA8231B6@twcny.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Mark S. Reichman" wrote: > > Another reason less lawsuits of this type are tried in Europe > is because the loser pays all court costs. > In the US a person will name everyone and anyone > remotely associated with the supposed wrong doing in hopes of a > big payoff. Each person must then hire a lawyer and defend > themselves against the compaint. In the states if you do > this and lose the court > case then usally no big deal. You are out your own attorney fees. > In europe if you lose you must pay everyones legal fees.. > This is known as "loser pays". This > tends to lessen the number of frivilous court cases, named > litigants, and lowers the burden on the european legal system. > Am I a lawyer? NO. I only saw a documentary on TV about this. > So take it for what its worth. > > Poul-Henning Kamp wrote: > > > > In message <8062.935743977@localhost>, "Jordan K. Hubbard" writes: > > >> > I seriously doubt they'll win this lawsuit. You can sue someone for > > >> > anything and everything, including having a hair color which > > >> > > >> ^ in the States > > > > > >Sorry, I've lived in Europe, you can't pull that one on me. :) > > > > > >In Germany, for example, it's possible to sue someone simply for > > >sticking their finger against their forehead. The myth that only the > > >U.S. is litigious is just that, a myth. Europeans sue the crap out of > > >one another all the time, and for issues just as silly. :) > > > > Jordan, I've lived in the US, Luxembourg, Italy and Denmark. > > > > While it is true that anyone can sue anybody else for anything they > > feel like all over the planet, the likely (lack of) outcome in > > europe makes it far less likely that they will do so in the first > > place. > > > > The main difference as far as I can tell, is that European courts > > apply some kind of "common sense" criteria before they award huge > > compensations to people who burn themselves on coffee, cut their > > fingers off with chain saws and so on: "Should this person not > > be realizing that coffee could be hot ? She has been drinking > > coffee for the last 50+ years ?" "If you use a chainsaw, shouldn't > > you be smart enough to realize that you cannot stop the chain > > with your hand ?" etc etc. > > > > The secondary difference is that in all the countries I know, > > they lawyer has to state his fee before the verdict, and it > > may not depend on the outcome of the verdict. > > > > The third difference is that we only use jurys in murder cases, > > we fully realize the ability of a showman-laywer to sway a jury, > > therefore we don't use them, unless the issue is the gravest > > crime we know off. > > > > Fourth, "puntative damages" fall to the state over here, so the > > potential for getting rich that way is simply not present. > > > > So while you're technically correct reality looks far different. > > > > -- > > 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 > > -- > \|/ > (@ @) > +-----------oOO----(_)-------------------+ > | Mark S. Reichman | > | reichman@twcny.rr.com | > | Radar Tech/Oracle Developer/Programmer | > +-------------------------oOO------------+ > |__|__| > || || > ooO Ooo -- \|/ (@ @) +-----------oOO----(_)-------------------+ | Mark S. Reichman | | reichman@twcny.rr.com | | Radar Tech/Oracle Developer/Programmer | +-------------------------oOO------------+ |__|__| || || ooO Ooo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 15:37: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B9B6F14F3D; Sat, 28 Aug 1999 15:37:03 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-176.skylink.it [194.185.55.176]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA24266; Sun, 29 Aug 1999 00:36:38 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id WAA00838; Sat, 28 Aug 1999 22:06:33 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sat, 28 Aug 1999 22:06:33 GMT Date: Sun, 29 Aug 1999 00:06:33 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: phk@freebsd.org Cc: FreeBSD CURRENT Mailing list Subject: rev 1.156 - fixes _qdivrem: division by zero panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning fixed (without knowing) a bug in the fd driver (that must have sneaked in when changing something to do with dev_t's. revision 1.156 date: 1999/08/28 08:10:13; author: phk; state: Exp; lines: +4 -1 Initialize dev->si_bsize*, the floppy driver doesn't use dsopen(). The panic is _qdivrem: division by zero Hope this info is of use to anyone. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 16:30:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 5A30D14D42 for ; Sat, 28 Aug 1999 16:30:05 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA25887; Sun, 29 Aug 1999 09:28:45 +1000 Date: Sun, 29 Aug 1999 09:28:45 +1000 From: Bruce Evans Message-Id: <199908282328.JAA25887@godzilla.zeta.org.au> To: current@FreeBSD.ORG, rock@dead-end.net Subject: Re: RealTek 8139 problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Under normal Circumstances, the communication is Ok between all three >machines, but sometimes the ethernet interface in the main machine >(the 8139) wedges up. I cannot ping any other host. The only solution >is taking the interface down and up again: It hangs when it gets an rx fifo overrun. The chance of an overrun can be modified by tweaking the fifo threshold and rx maxdma as in if_rlreg.h rev.1.9. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 18:31:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id 1278614D3C for ; Sat, 28 Aug 1999 18:31:04 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id SAA88603 for ; Sat, 28 Aug 1999 18:29:53 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37C88D14.1463436B@gorean.org> Date: Sat, 28 Aug 1999 18:29:56 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0826 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: $FreeBSD-knowledgable mergemaster available 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 some other changes planned so I'm not going to re-roll the port yet, but between now and then I've put up a version of mergemaster that knows about the $FreeBSD tags at http://freebsd.simplenet.com/mergemaster-1.25. Enjoy, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 28 22:38:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BD5D414DEA for ; Sat, 28 Aug 1999 22:38:44 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA02319; Sat, 28 Aug 1999 22:37:29 -0700 (PDT) (envelope-from dillon) Date: Sat, 28 Aug 1999 22:37:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199908290537.WAA02319@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: multipatch #6 available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've resynced the source tree and updated my big-fat patch again. http://www.backplane.com/FreeBSD4/ This patch is the same as the last one, but: * should patch clean to the tree as of tonight * fixes an additional bug in swapblock management. Certain management functions were being run at splbio() that had to be run at splvm(). * Adds a new feature to VN - swap space pre-reservation, in addition to the two features already added (zeroing and file creation/truncation). The swap space prereservation option may be used when configuring VN with swap backing store. Swap will be preallocated for all blocks in the device and no on-the-fly reallocation will occur. This avoids swap fragmentation and even allows you to 'recover' swap-backed VN-based filesystems across reboots provided that you create them with the same sizes and order as before and swap has not been allocated for anything else prior to the vnconfigs. A full description is available on my site. This patch has been extensively tested, especially the VN device when used in swap-backed mode. -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 Aug 29 0: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id 9127E14BEA for ; Sat, 28 Aug 1999 23:59:57 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p16-max1.dun.ihug.co.nz [209.76.100.16]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA00531; Sun, 29 Aug 1999 18:58:25 +1200 Message-ID: <37C8DA0F.2F8A9D7A@es.co.nz> Date: Sun, 29 Aug 1999 18:58:23 +1200 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG Subject: Re: followup to apm problems. References: <37C3C2F4.DE91BB21@es.co.nz> <199908270647.PAA08317@tasogare.imasy.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mitsuru IWASAKI wrote: > OK. Probably `slept 00:00:00 - 00:00:40' problem was caused by PS/2 > mouse, I think. Do we need something to do with psm on suspending as > well as resuming? Im not sure anything needs to be done for PS/2.. check out these results.. > > > > ed1: irq 3 at device 9.0 on pci0 > Ahh, I meant just unplug cable tentatively to confirm. > # and uninstall NIC if possible :) > After the problem analyzed, we just try to fix it in proper place. Unplugged NIC, not diabled: Standby: Aug 29 18:33:44 pyros /kernel.old: APM ioctl: cmd = 0x2000500c Aug 29 18:36:28 pyros /kernel.old: Received APM Event: PMEV_STANDBYRESUME Aug 29 18:36:28 pyros /kernel.old: Execute APM hook "default resume." Aug 29 18:36:28 pyros /kernel.old: resumed from suspended mode (slept 00:02:42) Aug 29 18:36:28 pyros /kernel.old: Execute APM hook "PS/2 mouse." Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:36:28 pyros apmd[355]: apmevent 000b index 3 Aug 29 18:36:28 pyros apmd: resumed at 19990829 18:36:28 Aug 29 18:36:28 pyros /kernel.old: APM ioctl: cmd = 0x40284164 And i pressed a key because i couldnt be biffed waiting any longer :) So it seems to be working properly! (Yes i am running apmd as well) Suspend: Aug 29 18:41:17 pyros /kernel.old: APM ioctl: cmd = 0x20005001 Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "default suspend." Aug 29 18:42:33 pyros /kernel.old: Received APM Event: PMEV_NORMRESUME Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "default resume." Aug 29 18:42:33 pyros /kernel.old: resumed from suspended mode (slept 00:01:15) Aug 29 18:42:33 pyros /kernel.old: Execute APM hook "PS/2 mouse." Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Aug 29 18:42:33 pyros apmd[355]: apmevent 0003 index 5 Aug 29 18:42:33 pyros apmd: resumed at 19990829 18:42:33 Aug 29 18:42:33 pyros /kernel.old: APM ioctl: cmd = 0x40284164 Same deal, I resumed it manually - so it seems to be working also. > At least, apm is in /usr/sbin/, apm -z touches /dev/apm and apmd > writes log on /var/log/ via syslog :) > Using `sysctl -w machdep.apm_suspend_delay=30 (or enough time for > spinning down)' and moving `camcontrol stop' to the end of command > list would be success. Otherwise, please forgive me. :) I tried that and the drive spins down, and right about 5 seconds before the 30 seconds is up, it spins back up again by itself, then it goes into suspend, but then comes right back out (presumably because of the disk activity). P.S plugging it back in, i do notice it resumes whenever there is activity on the hub :D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message