From owner-freebsd-current Sun Mar 14 0:19:18 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 B44BD14F3C for ; Sun, 14 Mar 1999 00:19:15 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA02066; Sun, 14 Mar 1999 17:19:06 +0900 (JST) Message-ID: <36EB70AB.2E1078F8@newsguy.com> Date: Sun, 14 Mar 1999 17:17:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > > If you are running -stable > > This is the -current list, and I'm running current. I don't have the > file "userconfig_script" nor /kernel.config. Just to be on the safe side... :-) > > OTOH, you might solve your problem just by adding the following two > > lines to /boot/loader.rc > > > > load kernel > > load -t userconfig_script /kernel.config > > > > and then putting your pnp configuration line on /kernel.config (if > > it is not there already). > > This is good info for current, right? And I don't need to worry about > "userconfig_script"? What's load -t do (I don't need a man page, but at > least a few words on the -t, please). That's correct. This is good for current. The command "load" loads things into memory. Usually the kernel or kld modules. But you can make it load other type of data, which will just be read and kept in memory for use by kernel/modules. This other type of data gets tagged with a "type". load -t , thus, loads of type . The type userconfig_script stores kernel's userconfig settings. > The pnp line will be the only thing in /kernel.config, that's normal? Yes. Well, I'm not really well versed on the secrets of userconfig_script stuff. In one example I have, a line with "quit" has been appended to the end. I think it is not needed, though. > I am not running stable, it doesn't track all the new config stuff, but > I have all the files listed below, it seems. Well, then I'd like to know what error message is showing up... :-) > > /boot/loader.4th > > /boot/support.4th > > /boot/defaults/loader.conf > > > > The last file is all you really need as example. > > I was asking about where to stick in the pnp line, and an example of > that. I guess it's not loader.conf (I just tested that, it didn't work > there). I'm a little leery yet of the load -t because I don't have that > userconfig_script file, and I don't know what the load -t does. "help load" on the loader helps here. The man page is coming out today, though. As for the pnp line, that just happens not to be loader's stuff... :-( I'll have to figure out how to best make this information locatable... :-( The pnp line is a "userconfig" type of information. It must, then, be put on a file to be loaded with "-t userconfig_script" flag. But, as I said, I have little familiarity with userconfig stuff. I think it is the commands you would type if you booted -c and entered the commands manually instead of using the visual config. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 0:22:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 41F4F14FEA for ; Sun, 14 Mar 1999 00:22:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id AAA09886; Sun, 14 Mar 1999 00:14:46 -0800 (PST) (envelope-from obrien) Date: Sun, 14 Mar 1999 00:14:46 -0800 From: "David O'Brien" To: Vladimir Kushnir Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs Message-ID: <19990314001446.D8213@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990313200255.C8213@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Vladimir Kushnir on Sun, Mar 14, 1999 at 07:30:59AM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW, do you plan to include egcs' g77 as well? Current, the g77 driver is built. But the f771 isn't. From previous talk, I've gotten the impression g77 should be a port vs. in the base system. I'm Ok either way -- I leave the decision to the lists and Core. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 0:27: 9 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 A11C21508A for ; Sun, 14 Mar 1999 00:26:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA48589; Sun, 14 Mar 1999 00:26:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Daniel C. Sobral" Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff In-reply-to: Your message of "Sun, 14 Mar 1999 17:17:47 +0900." <36EB70AB.2E1078F8@newsguy.com> Date: Sun, 14 Mar 1999 00:26:30 -0800 Message-ID: <48583.921399990@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The pnp line is a "userconfig" type of information. It must, then, > be put on a file to be loaded with "-t userconfig_script" flag. But, > as I said, I have little familiarity with userconfig stuff. I think > it is the commands you would type if you booted -c and entered the > commands manually instead of using the visual config. That is correct. You can boot -c and type "help" for a command list or, perhaps a bit more simply, see line 3030 in /sys/i386/i386/userconfig.c. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 0:33:20 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 DA79E153F3 for ; Sun, 14 Mar 1999 00:33:17 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA03416; Sun, 14 Mar 1999 17:33:05 +0900 (JST) Message-ID: <36EB73F2.CE9BC166@newsguy.com> Date: Sun, 14 Mar 1999 17:31:46 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Chuck Robey , current@FreeBSD.ORG Subject: Re: HEADS UP: new loader.rc stuff References: <48583.921399990@zippy.cdrom.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 "Jordan K. Hubbard" wrote: > > > The pnp line is a "userconfig" type of information. It must, then, > > be put on a file to be loaded with "-t userconfig_script" flag. But, > > as I said, I have little familiarity with userconfig stuff. I think > > it is the commands you would type if you booted -c and entered the > > commands manually instead of using the visual config. > > That is correct. You can boot -c and type "help" for a command list or, > perhaps a bit more simply, see line 3030 in /sys/i386/i386/userconfig.c. :) You keep that, and I'll start refering people to /sys/boot/common/interp_forth.c... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 1:44:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id CCE9014EF2 for ; Sun, 14 Mar 1999 01:44:42 -0800 (PST) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id KAA16813 for ; Sun, 14 Mar 1999 10:44:20 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id KAA19151 for ; Sun, 14 Mar 1999 10:44:19 +0100 (CET) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id KAA28120 for freebsd-current@freebsd.org; Sun, 14 Mar 1999 10:44:21 +0100 (CET) From: Thomas Schuerger Message-Id: <199903140944.KAA28120@wurzelausix.cs.uni-sb.de> Subject: gcc28 To: freebsd-current@freebsd.org Date: Sun, 14 Mar 1999 10:44:20 +0100 (CET) X-Mailer: ELM [version 2.4 PL24] 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 was wondering why 4.0-Current still uses gcc 2.7.x instead of gcc 2.8.1, which is available in the ports. gcc 2.8.x supports 586/686 optimization and much more, whereas 2.7.x will compile for 486 processors. Are there any compatibility problems involved when replacing 2.7.x by 2.8.x? If not, why isn't 2.8.1 the standard compiler included in FreeBSD? Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 2:22: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 473B314F22 for ; Sun, 14 Mar 1999 02:21:57 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id CAA11375; Sun, 14 Mar 1999 02:21:26 -0800 (PST) (envelope-from obrien) Date: Sun, 14 Mar 1999 02:21:26 -0800 From: "David O'Brien" To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc28 Message-ID: <19990314022126.B10050@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903140944.KAA28120@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903140944.KAA28120@wurzelausix.cs.uni-sb.de>; from Thomas Schuerger on Sun, Mar 14, 1999 at 10:44:20AM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was wondering why 4.0-Current still uses gcc 2.7.x instead of gcc 2.8.1, Review the freebsd-current mail archives (http://www.freebsd.org/ -> support). Short answer -- it is being worked on. We don't jump into the newest fad technology. gcc281 and egcs needed to be proven to be stable and usable before we will move to it. Other Unixes have a tendency to jump to new technology before it is ready. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 6:34:22 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 7661614DA4 for ; Sun, 14 Mar 1999 06:33:48 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10MBxK-000Gz9-00 for current@freebsd.org; Sun, 14 Mar 1999 16:33:30 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Proposal: Drop OBJLINK option Date: Sun, 14 Mar 1999 16:33:29 +0200 Message-ID: <65294.921422009@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I have a proposal regarding the OBJLINK option; let's drop it. Currently, OBJLINK breaks world when NOAOUT is undefined -- that is, for the legacy build. This is because making the objlink target for aout libraries blows away the existing objlinks that have already been created for building ELF libraries. The result is that a.out libraries are installed where ELF libraries should be, and their ELF counterparts aren't installed at all. I've spoken to some folks who've been around a while (my FreeBSD mentor and a colleague who's into NetBSD) and have an understanding of why the objlink functionality exists... hysterical raisins only. It was once useful, since there was a time when the only way to have make build on some filesystem other than the one containing the source was to use cross-device symlinks. Those days are long gone. The ports mechanism has its own way of handling this (WRKDIRPREFIX) and so does the base source tree (MAKEOBJDIRPREFIX). So OBJLINK is simply tautologous. If it were simply tautologous, there'd be no reason to remove it. But since it's blowing up in people's faces (two PR's at least) and since we have "a better way" that _doesn't_ blow up, I vote to retire the beast. Diffs to do just this are attached to PR misc/8071. I've tested the diffs through a buildworld+installworld, but would appreciated feedback on a release build. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 6:39: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 32A83150EF for ; Sun, 14 Mar 1999 06:39:16 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10MC2b-000Gzz-00 for current@freebsd.org; Sun, 14 Mar 1999 16:38:57 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Re: Proposal: Drop OBJLINK option In-reply-to: Your message of "Sun, 14 Mar 1999 16:33:29 +0200." <65294.921422009@axl.noc.iafrica.com> Date: Sun, 14 Mar 1999 16:38:57 +0200 Message-ID: <65346.921422337@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999 16:33:29 +0200, Sheldon Hearn wrote: > I have a proposal regarding the OBJLINK option; let's drop it. Perhaps I should have fleshed out the "how" more. I focused mostly on the "why". I'm suggesting that: 1) PR misc/8071 be examined. 2) People acknowledge that this isn't heresy. 3) The diffs are applied to CURRENT. 4) A "HEADS UP!" message is posted to this mailing list. 5) A note about OBJLINK breaking the legacy build is added to the ERRATA for 3.1-RELEASE. 6) The diffs are backported before the next STABLE release. 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 Mar 14 6:42:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 9763B152DD for ; Sun, 14 Mar 1999 06:42:32 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.1) id GAA46768; Sun, 14 Mar 1999 06:41:13 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199903141441.GAA46768@troutmask.apl.washington.edu> Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990314001446.D8213@relay.nuxi.com> from "David O'Brien" at "Mar 14, 1999 0:14:46 am" To: obrien@NUXI.com Date: Sun, 14 Mar 1999 06:41:13 -0800 (PST) Cc: kushn@mail.kar.net, 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 David O'Brien wrote: > > BTW, do you plan to include egcs' g77 as well? > > Current, the g77 driver is built. But the f771 isn't. From previous > talk, I've gotten the impression g77 should be a port vs. in the base > system. I'm Ok either way -- I leave the decision to the lists and Core. > At the risk of starting another pointless Fortran thread, I have ports of f2c and a new f77 driver for f2c sitting on my machine. If you decide to include g77 (which would be a Good Thing, IMHO), then I'll submit and maintain the f2c port. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 6:48:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9CA3514BFF for ; Sun, 14 Mar 1999 06:48:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id PAA24852; Sun, 14 Mar 1999 15:48:20 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id PAA12836; Sun, 14 Mar 1999 15:48:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: Proposal: Drop OBJLINK option In-reply-to: Your message of "Sun, 14 Mar 1999 16:33:29 +0200." <65294.921422009@axl.noc.iafrica.com> Date: Sun, 14 Mar 1999 15:48:14 +0100 Message-ID: <12834.921422894@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <65294.921422009@axl.noc.iafrica.com>, Sheldon Hearn writes: > >Hi folks, > >I have a proposal regarding the OBJLINK option; let's drop it. I concur. Lets try to reduce the amount of Makefile-hair for once. -- 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 Mar 14 6:48:48 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 9BC9515012 for ; Sun, 14 Mar 1999 06:48:43 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10MCBj-000H1M-00 for current@freebsd.org; Sun, 14 Mar 1999 16:48:23 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Proposal: Populate share/examples/etc Date: Sun, 14 Mar 1999 16:48:23 +0200 Message-ID: <65431.921422903@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, As mentioned in PR misc/5207, /usr/share/examples/etc/README says that the directory contains virgin copies of the files installed into /etc . This isn't true, of course. I've attached to the PR diffs that would cause /usr/share/examples/etc to be populated correctly. I've tested the changes through a buildworld+installworld. I'd appreciated a review. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 7: 0: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 7F0C214EFF for ; Sun, 14 Mar 1999 06:59:56 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id QAA15742; Sun, 14 Mar 1999 16:59:33 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id QAA30063; Sun, 14 Mar 1999 16:59:32 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903141459.QAA30063@greenpeace.grondar.za> To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: Proposal: Drop OBJLINK option In-Reply-To: Your message of " Sun, 14 Mar 1999 16:33:29 +0200." <65294.921422009@axl.noc.iafrica.com> References: <65294.921422009@axl.noc.iafrica.com> Date: Sun, 14 Mar 1999 16:59:31 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > Diffs to do just this are attached to PR misc/8071. I've tested the > diffs through a buildworld+installworld, but would appreciated feedback > on a release build. Nuke the festering slag :-) (Or gimme fresh patches and I'll do it!) 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 Mar 14 8:25:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id F168614F14 for ; Sun, 14 Mar 1999 08:25:15 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id RAA02700 for freebsd-current@freebsd.org; Sun, 14 Mar 1999 17:25:51 +0100 (CET) Received: (qmail 323 invoked by uid 1000); 14 Mar 1999 16:22:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Mar 1999 16:22:42 -0000 Date: Sun, 14 Mar 1999 17:22:42 +0100 (CET) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: Postfix 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 hate to roll up old threads, but it seems like nothing has come out of the Postfix vs. sendmail debate on this list. We don't even have a Postfix port. Has anybody created a port or should I go ahead and have a look at it? Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 9:21:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (Postfix) with ESMTP id 4202715443 for ; Sun, 14 Mar 1999 09:20:31 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:32264 "EHLO mediaport.org" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with ESMTP id <7950-17325>; Sun, 14 Mar 1999 18:19:59 +0100 Message-ID: <36EBEFA1.B81823D1@mediaport.org> Date: Sun, 14 Mar 1999 18:19:29 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan wrote: > I hate to roll up old threads, but it seems like nothing has come out of > the Postfix vs. sendmail debate on this list. > > We don't even have a Postfix port. Has anybody created a port or should I > go ahead and have a look at it? I would be very pleased to see a Postfix port. Not having to deal with Sendmail would render FreeBSD more usable for non-die-hard users. Cheers, Jeroen -- Jeroen C. van Gelderen - gelderen@mediaport.org - 0xC33EDFDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 9:32: 7 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 6C47A1544C for ; Sun, 14 Mar 1999 09:32:00 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA22311; Sun, 14 Mar 1999 12:29:44 -0500 (EST) Date: Sun, 14 Mar 1999 12:29:44 -0500 (EST) From: Chuck Robey To: "Jeroen C. van Gelderen" Cc: Blaz Zupan , freebsd-current@FreeBSD.ORG Subject: Re: Postfix In-Reply-To: <36EBEFA1.B81823D1@mediaport.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Mar 1999, Jeroen C. van Gelderen wrote: > Blaz Zupan wrote: > > I hate to roll up old threads, but it seems like nothing has come out of > > the Postfix vs. sendmail debate on this list. > > > > We don't even have a Postfix port. Has anybody created a port or should I > > go ahead and have a look at it? > > I would be very pleased to see a Postfix port. Not having to deal with > Sendmail would render FreeBSD more usable for non-die-hard users. Please take this off current, now. It's been discussed to death, and while I'd love to get it in, I don't want to see another flamewar over this. If you want to carry it on, do it on FreeBSD-chat, NOT current. If you want to discuss the port, do it on FreeBSD-ports. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 11: 4:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id C47FB14CB2 for ; Sun, 14 Mar 1999 11:04:06 -0800 (PST) (envelope-from jrs@enteract.com) Received: (qmail 29090 invoked from network); 14 Mar 1999 19:03:46 -0000 Received: from adam.enteract.com (jrs@206.54.252.1) by thor.enteract.com with SMTP; 14 Mar 1999 19:03:46 -0000 Date: Sun, 14 Mar 1999 13:03:46 -0600 (CST) From: John Sconiers To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hate to roll up old threads, but it seems like nothing has come out of > the Postfix vs. sendmail debate on this list. > We don't even have a Postfix port. Has anybody created a port or should I > go ahead and have a look at it? Postfix is working great for me. I replaced sendmail on a "lightly used" (5000+ messages a week) mail server at a small office. It installed flawlessly....and has been working great for the past month. Extremely impressed. There was a some noise on tone of the list about not using it on a shell machine but since the mail servers I've put postfix on are not shell machines I never looked into it. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 11:23:32 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 44FC814E6B; Sun, 14 Mar 1999 11:23:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93438; Sun, 14 Mar 1999 11:22:54 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:22:54 -0800 (PST) From: Matthew Dillon Message-Id: <199903141922.LAA93438@apollo.backplane.com> To: Nicholas Esborn Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Diskless boot stopping at "NFS ROOT:..." References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a very weird problem with the new parallel port device that caused this to occur. It turned out to be speculative probing by the parallel device causing the system to go unstable. Try disabling the new parallel port device(s)/controllers and see if you can boot again. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 11:29: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 22DC214F0A for ; Sun, 14 Mar 1999 11:29:45 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93484; Sun, 14 Mar 1999 11:29:26 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:29:26 -0800 (PST) From: Matthew Dillon Message-Id: <199903141929.LAA93484@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: HEADS UP! New VN device committed - loadable module disabled temporarily Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you using the VN device as a loadable module, please be aware that the new VN device has been committed to -4.x and cannot yet be used as a loadable module. Be sure that you are not improperly using the stale loadable module for VN under -4.x that might still reside in your /modules directory. We hope to get a working loadable module for vn soon. The problem is due to options dependancies which do not exist for loadable modules. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 11:55: 5 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 E775F1502F for ; Sun, 14 Mar 1999 11:54:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA93753; Sun, 14 Mar 1999 11:54:08 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 11:54:08 -0800 (PST) From: Matthew Dillon Message-Id: <199903141954.LAA93753@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Checklist for testing new -4.x kernels ( -current ). Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Exceptions are made for people who really know what they are doing, verses only think that they know what they are doing :-) * Do not use any loadable modules, compile the needed modules into the kernel directly. To double check, run 'kldstat' after booting the system and make sure that only the kernel is listed. * Make sure to install the new boot blocks and new /boot directory from the latest source. * Large 'maxusers' kernel configurations ( > 128 ), or kernels with >= 512MB of ram have experienced instability in the past, be sure you are using the latest kernel and try lowering the maxusers paramater to 64 first, before reporting the crash. * If weird crashes occur with the splash screen, try disabling it. * If weird crashes occur during boot, try diasbling the parallel port stuff and see if that fixes the problem. * When reporting crashes, please include information on the machine's configuration including any special devices ( such as VN ) that you may be using, and your disk configuration ( df ), and the memory & device configuration ( dmesg ). * When reporting crashes that occur from testing -- for example, you are testing the system by running buildworlds, please include the exact test script / make / whatever that you are doing along with the system configuration info. * Make sure your systems are backed up. --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 12:52:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp-out2.bellatlantic.net (smtp-out2.bellatlantic.net [199.45.39.157]) by hub.freebsd.org (Postfix) with ESMTP id 61BCD1522A for ; Sun, 14 Mar 1999 12:52:04 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from client201-122-41.bellatlantic.net (client201-122-41.bellatlantic.net [151.201.122.41]) by smtp-out2.bellatlantic.net (8.9.1/8.9.1) with ESMTP id PAA27544 for ; Sun, 14 Mar 1999 15:53:56 -0500 (EST) Date: Sun, 14 Mar 1999 15:51:24 +0000 (GMT) From: Donn Miller X-Sender: dmm125@localhost To: current@freebsd.org Subject: boot -c not saving changes 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 When I boot up my -current box, I hit 'c' to get to the boot prompt. Then I do "boot -c", and then "vi" to configure my kernel. But any changes I make via userconfig aren't saved for when the next time I boot. Is it a problem with the boot loader, or do I have to type some commands to save my config in /boot.config? I have a zero-length /boot.config right now. I would think this involves invoking load -t /boot.config at the boot prompt to load /boot.config the next time I boot, but I don't know the exact sequence. Thanks . Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 13: 0:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id A461D14E6B for ; Sun, 14 Mar 1999 13:00:53 -0800 (PST) (envelope-from myself@conterra.com) Received: from dmaddox.conterra.com (myself@dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id QAA09393; Sun, 14 Mar 1999 16:00:34 -0500 (EST) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.1) id QAA05930; Sun, 14 Mar 1999 16:00:35 -0500 (EST) (envelope-from myself) Date: Sun, 14 Mar 1999 16:00:34 -0500 From: "Donald J . Maddox" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: boot -c not saving changes Message-ID: <19990314160034.A5912@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Donn Miller on Sun, Mar 14, 1999 at 03:51:24PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The answer depends on exactly how current you are... With -current from a few days ago, I would have said: Make sure you have a /boot/loader.rc file that contains at least these lines: load /kernel load -t /boot.config Then, make sure /boot.config contains all the stuff that you would normally type at the config> prompt when you Boot: -c. If you are *really* -current, /boot/loader.rc should probably just contain something like: include /boot/loader.4th start Then, you should copy /boot/defaults/loader.conf to /boot/loader.conf and edit it to match what you want to happen at boot. On Sun, Mar 14, 1999 at 03:51:24PM +0000, Donn Miller wrote: > When I boot up my -current box, I hit 'c' to get to the boot prompt. Then > I do "boot -c", and then "vi" to configure my kernel. But any changes I > make via userconfig aren't saved for when the next time I boot. > > Is it a problem with the boot loader, or do I have to type some commands > to save my config in /boot.config? I have a zero-length /boot.config > right now. I would think this involves invoking load -t /boot.config at > the boot prompt to load /boot.config the next time I boot, but I don't > know the exact sequence. > > Thanks > . > > Donn > > > > 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 Mar 14 13:12: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8498E1506A for ; Sun, 14 Mar 1999 13:11:47 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA04101; Sun, 14 Mar 1999 13:11:16 -0800 Date: Sun, 14 Mar 1999 13:11:15 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.org Subject: Re: Checklist for testing new -4.x kernels ( -current ). In-Reply-To: <199903141954.LAA93753@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 And to supplement this- please try and isolate problems to areas of likely failure. In particular, SCSI driver related problems go to freebsd-scsi@freebsd.org- they're read and responded to quicker there than freebsd-hackers or freebsd-current. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 13:18:38 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 7AC3615757 for ; Sun, 14 Mar 1999 13:18:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA03022; Sun, 14 Mar 1999 13:12:16 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdKi3019; Sun Mar 14 21:12:07 1999 Date: Sun, 14 Mar 1999 13:12:04 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: freebsd-current@FreeBSD.org Subject: Re: Checklist for testing new -4.x kernels ( -current ). In-Reply-To: <199903141954.LAA93753@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 Sun, 14 Mar 1999, Matthew Dillon wrote: > Exceptions are made for people who really know what they are doing, verses > only think that they know what they are doing :-) > > * Do not use any loadable modules, compile the needed modules into the > kernel directly. To double check, run 'kldstat' after booting the > system and make sure that only the kernel is listed. This does not mean that modules are thought to be broken, just that it obscures debugging > > * Make sure to install the new boot blocks and new /boot directory from > the latest source. The 3rd stage bootloader one presumes as the 2nd doesn't look at the kernel. > > * Large 'maxusers' kernel configurations ( > 128 ), or kernels > with >= 512MB of ram have experienced instability in the past, be sure > you are using the latest kernel and try lowering the maxusers > paramater to 64 first, before reporting the crash. > > * If weird crashes occur with the splash screen, try disabling it. > > * If weird crashes occur during boot, try diasbling the parallel port > stuff and see if that fixes the problem. > > * When reporting crashes, please include information on the machine's > configuration including any special devices ( such as VN ) that you > may be using, and your disk configuration ( df ), and the memory & > device configuration ( dmesg ). > > * When reporting crashes that occur from testing -- for example, you > are testing the system by running buildworlds, please include the > exact test script / make / whatever that you are doing along with the > system configuration info. > > * Make sure your systems are backed up. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 13:42: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kar.net (n190.cdialup.kar.net [195.178.130.190]) by hub.freebsd.org (Postfix) with ESMTP id 5B16D15798 for ; Sun, 14 Mar 1999 13:40:25 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.3/8.8.8) with ESMTP id XAA01543; Sun, 14 Mar 1999 23:39:40 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Sun, 14 Mar 1999 23:39:39 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: bmake/contrib framework for egcs In-Reply-To: <19990314001446.D8213@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A pity. This would mean g77 gets a fair chance to once again become quite obsolete. Of course, it's not all that important 'far as servers are concerned, but as I'm in high energy physics - I should say so far all my colegues I know used FORTRAN rather than C/C++. Well, that still doesn't make us a majority here, does it? On Sun, 14 Mar 1999, David O'Brien wrote: > > BTW, do you plan to include egcs' g77 as well? > > Current, the g77 driver is built. But the f771 isn't. From previous > talk, I've gotten the impression g77 should be a port vs. in the base > system. I'm Ok either way -- I leave the decision to the lists and Core. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > Oh, BTW, just today went through 'make -j16 buildworld' with your bmaked egcs' compiled kernel (j16 is not very impressive, but computer is a poor old P5-100 with only 32 Mb RAM). Kernel looked fairly stable, at least in single user mode. Regards, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 13:47:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id CB959157B4 for ; Sun, 14 Mar 1999 13:47:22 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA18464; Mon, 15 Mar 1999 08:47:02 +1100 Date: Mon, 15 Mar 1999 08:47:02 +1100 From: Bruce Evans Message-Id: <199903142147.IAA18464@godzilla.zeta.org.au> To: current@FreeBSD.ORG, sheldonh@iafrica.com Subject: Re: Proposal: Drop OBJLINK option Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have a proposal regarding the OBJLINK option; let's drop it. No, it is quite useful for actually working with the objects (it saves some `make whereobj's...). >Currently, OBJLINK breaks world when NOAOUT is undefined -- that is, for >the legacy build. This is because making the objlink target for aout >libraries blows away the existing objlinks that have already been >created for building ELF libraries. OBJLINK is not useful for `make world' or `make aout-to-elf' so don't use it for them. In particular, don't put it in sys.mk, /etc/make.conf or /etc/make.conf.local so that it gets used for all invocations of `make'. >The result is that a.out libraries are installed where ELF libraries >should be, and their ELF counterparts aren't installed at all. This is unfortunate, but it's a deficiency of the legacy build, not of OBJLINK. The build can't be expected to handle all types of junk that may be in the source directories. obj subdirectories may also break it. Some of these problems can be solved by running `make cleandir' once or twice as mentioned in your followup to the PR. `make world' doesn't do this automatically because it would usually just double the amount of time required for cleaning. >I've spoken to some folks who've been around a while (my FreeBSD mentor >and a colleague who's into NetBSD) and have an understanding of why the >objlink functionality exists... hysterical raisins only. Not quite. obj links were originally used to permit building objects in a separate tree. `make' only supported building in the current directory, or in the obj subdirectory (which may be a symlink to to the actual directory), or in a machine-dependent subdirectory. The obj symlink case was used (unconditionally for `make world') to build the objects in /usr/obj. This was bad because it required writing to the source tree, and for other reasons. Then when `make' was changed to support building objects in a separate obj directly, the OBJLINK macro was added to support building the links anyway, since they are useful for working with the objects. >If it were simply tautologous, there'd be no reason to remove it. But >since it's blowing up in people's faces (two PR's at least) and since we >have "a better way" that _doesn't_ blow up, I vote to retire the beast. People shouldn't use it if they don't know what it is for. The links should be named differently so that they aren't treated specially by `make'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 14:13:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 65C8115421 for ; Sun, 14 Mar 1999 14:13:20 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id BAA20206; Mon, 15 Mar 1999 01:01:08 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id BAA03697; Mon, 15 Mar 1999 01:04:31 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199903142204.BAA03697@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid In-reply-to: Your message of "Thu, 04 Mar 1999 23:06:28 PST." <199903050706.XAA38141@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 01:04:30 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > - error = acquire(lkp, extflags, > - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE); > + if (p->p_flag & P_DEADLKTREAT) { > + error = acquire( This is broken: p may be NULL, it is checked several lines before. My kernel just paniced for this reason. Well, sorry for late response, but: what was wrong with Tor Egge's "workaround" from kern/8416? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 14:51:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-5-dbn.dial-up.net [196.34.155.69]) by hub.freebsd.org (Postfix) with ESMTP id B518314C28 for ; Sun, 14 Mar 1999 14:51:40 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id AAA11015; Mon, 15 Mar 1999 00:48:00 +0200 (SAT) From: Robert Nordier Message-Id: <199903142248.AAA11015@ceia.nordier.com> Subject: Re: boot -c not saving changes In-Reply-To: <19990314160034.A5912@dmaddox.conterra.com> from "Donald J . Maddox" at "Mar 14, 99 04:00:34 pm" To: dmaddox@conterra.com Date: Mon, 15 Mar 1999 00:47:57 +0200 (SAT) Cc: dmm125@bellatlantic.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donald J . Maddox wrote: > The answer depends on exactly how current you are... > > With -current from a few days ago, I would have said: > > Make sure you have a /boot/loader.rc file that contains at least > these lines: > > load /kernel > load -t /boot.config > > Then, make sure /boot.config contains all the stuff that you would > normally type at the config> prompt when you Boot: -c. Rather load -t userconfig_script /kernel.config In particular, not "/boot.config" which is a file with a different purpose used by the bootblocks (boot stages 1 & 2). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 14:57:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id 27F7414DB7 for ; Sun, 14 Mar 1999 14:57:15 -0800 (PST) (envelope-from dmaddox@conterra.com) Received: from conterra.com (dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id RAA12826; Sun, 14 Mar 1999 17:55:24 -0500 (EST) Message-ID: <36EC84AF.D4643CEB@conterra.com> Date: Sun, 14 Mar 1999 22:55:27 -0500 From: "Donald J. Maddox" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Robert Nordier Cc: dmm125@bellatlantic.net, current@FreeBSD.ORG Subject: Re: boot -c not saving changes References: <199903142248.AAA11015@ceia.nordier.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, you're right on all counts, of course... I've answered this question so many times in the last 10 days that I'm starting to go on autopilot :-/ Robert Nordier wrote: > > Donald J . Maddox wrote: > > > The answer depends on exactly how current you are... > > > > With -current from a few days ago, I would have said: > > > > Make sure you have a /boot/loader.rc file that contains at least > > these lines: > > > > load /kernel > > load -t /boot.config > > > > Then, make sure /boot.config contains all the stuff that you would > > normally type at the config> prompt when you Boot: -c. > > Rather > > load -t userconfig_script /kernel.config > > In particular, not "/boot.config" which is a file with a different > purpose used by the bootblocks (boot stages 1 & 2). > > -- > Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 14:58: 3 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 3168914F34 for ; Sun, 14 Mar 1999 14:57:54 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id WAA03847; Sun, 14 Mar 1999 22:56:42 GMT (envelope-from nik) Date: Sun, 14 Mar 1999 22:56:41 +0000 From: Nik Clayton To: "Jordan K. Hubbard" Cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: "make release" testers wanted for Doc. Proj. Message-ID: <19990314225641.A3152@catkin.nothing-going-on.org> References: <19990312221640.J1309@catkin.nothing-going-on.org> <25038.921280630@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <25038.921280630@zippy.cdrom.com>; from Jordan K. Hubbard on Fri, Mar 12, 1999 at 03:17:10PM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 12, 1999 at 03:17:10PM -0800, Jordan K. Hubbard wrote: > This is done by make release in the chroot area. Ah. So it is. > > 2. Make sure /usr/doc/ is up to date (or wherever you store a > > This will have no effect on the chroot area - it's checked out > by make release. :) > > > 3. Edit doc/Makefile, and change the SUBDIR line from > > Ditto. I've got to stop sending these things late at night (glances at clock. Er, OK). What I actually did when I was testing this was to create a staging area (/usr/local/tmp/release in my case), and then run; # cd /usr/src/release # make RD=/usr/local/tmp/release release.1 release.2 doc.1 which seemed to put the files in the right place. If it puts them in the right place for other people (or this deafening silence continues) then I'll assume it's working properly (everyone else has been on the sharp end of "Hey, you broke 'make release'!" messages, now I want a piece of the action. . .) N -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 15:37: 0 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 3EE9514C3D for ; Sun, 14 Mar 1999 15:36:57 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA22812 for freebsd-current@FreeBSD.ORG; Mon, 15 Mar 1999 00:36:38 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 7616C8848; Mon, 15 Mar 1999 00:10:39 +0100 (CET) Date: Mon, 15 Mar 1999 00:10:39 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Postfix Message-ID: <19990315001039.A1477@keltia.freenix.fr> Reply-To: "FreeBSD's ports list" Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Blaz Zupan on Sun, Mar 14, 1999 at 05:22:42PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ redirected to ports ] According to Blaz Zupan: > We don't even have a Postfix port. Has anybody created a port or should I > go ahead and have a look at it? Please wait a few days if you insist on a port, Wietse will release a new version with quite a number of new features. In any case, a Postfix port will not be very difficult to do. There is no "make install" target in the main Makefile so you'll have to roll your own. Put all the post* commands in /usr/sbin along with the sendmail binary (to replace the real Sendmail), don't forget the mailq & newaliases links, put the other binaries in /usr/libexec/postfix and install a sample /etc/postfix/main.cf with the proper paths. It would be nice to put the HTML documentation in "share/postfix" and to make a nice set of main.cf's defaults with anti-spam and no relaying. Ask Jonathan Bresler (our postmaster, jmb@freebsd.org), he started patching Postfix to add a "make install" target. You could patch it to install in ${PREFIX}/etc/postfix but I really think that /etc/postfix is better (it is standard). I still think it should be in /usr/src/contrib and replace sendmail. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 17:20:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 748791589D for ; Sun, 14 Mar 1999 17:19:42 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.2/8.8.8) with SMTP id JAA12955; Mon, 15 Mar 1999 09:19:21 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA15199; Mon, 15 Mar 1999 09:19:20 +0800 Message-Id: <199903150119.JAA15199@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: shocking@bandicoot.prth.tensor.pgs.com Subject: Re: bmake/contrib framework for egcs In-reply-to: Your message of "Sun, 14 Mar 1999 06:34:24 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 09:19:20 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> BTW, do you plan to include egcs' g77 as well? >Current, the g77 driver is built. But the f771 isn't. From previous >talk, I've gotten the impression g77 should be a port vs. in the base >system. I'm Ok either way -- I leave the decision to the lists and Core. >- -- >- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) I think the building of the fortran compiler should be controlled through some variable in /etc/make.conf - BUILD_G77 or something like that, the same way you can elect to build profiled libs et cetera. It'd be a pain in the rear artificially ripping out source and including it in another tarball. Stephen -- The views expressed above are not those of PGS Tensor. "People often think of research as a form of development -- that it's about doing exactly what you planned, doing it on time, and doing it with resources that you said you'd use. But if you're going to do that, you have to know what you are doing, and if you know what you are doing, it isn't really research." --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 20:49:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 551691502E for ; Sun, 14 Mar 1999 20:49:19 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id XAA22951; Sun, 14 Mar 1999 23:48:53 -0500 (EST) Date: Sun, 14 Mar 1999 23:48:53 -0500 (EST) From: To: Blaz Zupan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix 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, 14 Mar 1999, Blaz Zupan wrote: > We don't even have a Postfix port. Has anybody created a port or should I > go ahead and have a look at it? FWIW, I installed Postfix on an experimental box here (since it's still in 'Beta'). I've been happy with its performance, although I've not really stressed it. Following the information found at www.postfix.org, I had no problems installing it under FreeBSD 3.0-REL. Later, -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 23:33:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.amis.net (server.amis.net [212.18.32.10]) by hub.freebsd.org (Postfix) with ESMTP id 666D91506A; Sun, 14 Mar 1999 23:33:36 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id IAA13127; Mon, 15 Mar 1999 08:34:15 +0100 (CET) Received: by gold.amis.net (Postfix, from userid 1000) id 0EA2812; Mon, 15 Mar 1999 08:33:15 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by gold.amis.net (Postfix) with ESMTP id E21FC1E0A; Mon, 15 Mar 1999 08:33:15 +0100 (CET) Date: Mon, 15 Mar 1999 08:33:15 +0100 (CET) From: Blaz Zupan To: "FreeBSD's ports list" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Postfix In-Reply-To: <19990315001039.A1477@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 > Please wait a few days if you insist on a port, Wietse will release a new > version with quite a number of new features. In any case, a Postfix port > will not be very difficult to do. Actually, I already had a go at it. A first version of the port can be downloaded from ftp://ftp.si.freebsd.org/pub/FreeBSD/local/postfix.tar > There is no "make install" target in the main Makefile so you'll have to > roll your own. Put all the post* commands in /usr/sbin along with the This is exactly what I did. > sendmail binary (to replace the real Sendmail), don't forget the mailq & > newaliases links, put the other binaries in /usr/libexec/postfix and > install a sample /etc/postfix/main.cf with the proper paths. I don't believe this is ok. No port should mess with anything with /usr/sbin or /usr/libexec. The port installs in /usr/local/sbin and /usr/local/libexec and the configuration is put into /usr/local/etc/postfix. I have included a script, which moves aside sendmail and replaced it with links to Postfix, the script can also be used to again activate sendmail. But the script is not called by default. > It would be nice to put the HTML documentation in "share/postfix" and to > make a nice set of main.cf's defaults with anti-spam and no relaying. The documentation is not yet being installed and I don't touch the main.cf (yet). Comments appreciated. Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 23:41:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C27C14FF7 for ; Sun, 14 Mar 1999 23:41:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA96226; Sun, 14 Mar 1999 23:41:12 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 23:41:12 -0800 (PST) From: Matthew Dillon Message-Id: <199903150741.XAA96226@apollo.backplane.com> To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Re: Checklist for testing new -4.x kernels ( -current ). References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> * Do not use any loadable modules, compile the needed modules into the :> kernel directly. To double check, run 'kldstat' after booting the :> system and make sure that only the kernel is listed. : :This does not mean that modules are thought to be broken, just that it :obscures debugging What it means is that one of the most common problems developers have is that they compile and install a new kernel and forget to recompile the loadable modules... which may no longer be compatible with the newly installed kernel. For most developers, it is easier to simply not use loadable modules at all. Loadable modules are useful for releases and such, but not so useful for ongoing development work. :> * Make sure to install the new boot blocks and new /boot directory from :> the latest source. : :The 3rd stage bootloader one presumes as the 2nd doesn't look at the :kernel. It's less confusing to simply tell people to reinstall the entirety of the boot subsystem: boot blocks and /boot/ files. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 14 23:51:13 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 4B5D8151D3 for ; Sun, 14 Mar 1999 23:50:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA96296; Sun, 14 Mar 1999 23:47:54 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Mar 1999 23:47:54 -0800 (PST) From: Matthew Dillon Message-Id: <199903150747.XAA96296@apollo.backplane.com> To: Dmitrij Tejblum Cc: current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: <199903142204.BAA03697@tejblum.dnttm.rssi.ru> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon wrote: :> - error = acquire(lkp, extflags, :> - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE); :> + if (p->p_flag & P_DEADLKTREAT) { :> + error = acquire( : :This is broken: p may be NULL, it is checked several lines before. :My kernel just paniced for this reason. : :Well, sorry for late response, but: what was wrong with Tor Egge's :"workaround" from kern/8416? : :Dima We'll get a quick fix committed but the lockmgr stuff needs a real going-over... having interrupts using the general lockmgr call is a disaster waiting to happen. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 0:11:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id EEA521544C for ; Mon, 15 Mar 1999 00:11:49 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA49614; Mon, 15 Mar 1999 08:13:15 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 15 Mar 1999 08:13:15 +0000 (GMT) From: Doug Rabson To: Dmitrij Tejblum Cc: Matthew Dillon , current@freebsd.org Subject: Re: Simple DOS against 3.x locks box solid In-Reply-To: <199903142204.BAA03697@tejblum.dnttm.rssi.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 Mon, 15 Mar 1999, Dmitrij Tejblum wrote: > Matthew Dillon wrote: > > - error = acquire(lkp, extflags, > > - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE); > > + if (p->p_flag & P_DEADLKTREAT) { > > + error = acquire( > > This is broken: p may be NULL, it is checked several lines before. > My kernel just paniced for this reason. > > Well, sorry for late response, but: what was wrong with Tor Egge's > "workaround" from kern/8416? I'm almost relieved. I had a report of this on the alpha and I thought it might be alpha-specific. -- 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 Mar 15 2:56: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from creator.gu.net (creator-eth0.gu.net [194.93.191.130]) by hub.freebsd.org (Postfix) with ESMTP id B021514D74 for ; Mon, 15 Mar 1999 02:55:40 -0800 (PST) (envelope-from srd@umc.com.ua) Received: (from uucp@localhost) by creator.gu.net (8.8.8/8.8.8) with UUCP id MAA21855 for current@freebsd.org; Mon, 15 Mar 1999 12:44:58 +0200 Received: from umc.com.ua (localhost [127.0.0.1]) by mh.umc.com.ua (8.7.5/8.7.3) with ESMTP id MAA05762 for ; Mon, 15 Mar 1999 12:37:20 +0200 (EET) Message-ID: <36ECE139.87945589@umc.com.ua> Date: Mon, 15 Mar 1999 12:30:17 +0200 From: "Roman D. Sinyuk" Organization: UMC X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: current@freebsd.org Subject: unsubscribe Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 2:59:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (Postfix) with ESMTP id A9DE6152F3 for ; Mon, 15 Mar 1999 02:51:47 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id NAA29215; Mon, 15 Mar 1999 13:23:17 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.3/8.9.1) with ESMTP id NAA00520; Mon, 15 Mar 1999 13:24:07 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199903151024.NAA00520@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Matthew Dillon Cc: current@FreeBSD.org Subject: Re: Simple DOS against 3.x locks box solid In-reply-to: Your message of "Sun, 14 Mar 1999 23:47:54 PST." <199903150747.XAA96296@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Date: Mon, 15 Mar 1999 13:24:06 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > We'll get a quick fix committed but the lockmgr stuff needs a real > going-over... having interrupts using the general lockmgr call is > a disaster waiting to happen. Hmmm. After I looked a bit further, it looks like a bug in the scheduler (?). Here is the stack trace: #9 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 16777216, tf_ebp = -999002708, tf_isp = -999002744, tf_ebx = -1071228500, tf_edx = -2, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072584332, tf_cs = 8, tf_eflags = 66050, tf_esp = -999002524, tf_ss = -1071228500}) at ../../i386/i386/trap.c:438 #10 0xc011a974 in lockmgr (lkp=0xc02659ac, flags=1, interlkp=0x0, p=0x0) at ../../kern/kern_lock.c:217 #11 0xc01d8c5b in vm_map_lookup (var_map=0xc4746e64, vaddr=3294351360, fault_typea=1 '\001', out_entry=0xc4746e68, object=0xc4746e5c, pindex=0xc4746e60, out_prot=0xc4746e4b "À\a", wired=0xc4746e44) at ../../vm/vm_map.c:2463 #12 0xc01d4153 in vm_fault (map=0xc02659ac, vaddr=3294351360, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:197 #13 0xc01ff9ac in trap_pfault (frame=0xc4746f18, usermode=0, eva=3294351360) at ../../i386/i386/trap.c:825 #14 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 46137344, tf_esi = -1071149988, tf_ebp = -999002244, tf_isp = -999002304, tf_ebx = 18341888, tf_edx = -1000615936, tf_ecx = -1005747008, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071650796, tf_cs = 8, tf_eflags = 65606, tf_esp = -1072552121, tf_ss = -999654400}) at ../../i386/i386/trap.c:438 #15 0xc01fe814 in swtch_com () #16 0xc01ff859 in trap (frame={tf_es = 47, tf_ds = 47, tf_edi = 20, tf_esi = 136019608, tf_ebp = -1077948228, tf_isp = -999002156, tf_ebx = 307, tf_edx = 136220264, tf_ecx = 136630944, tf_eax = 135716928, tf_trapno = 7, tf_err = 0, tf_eip = 134536416, tf_cs = 31, tf_eflags = 514, tf_esp = -1077948244, tf_ss = 47}) at ../../i386/i386/trap.c:195 #17 0xc01f5aa3 in swi_ast_user () the trap in swtch_com() (frame #15) is here: /* switch address space */ <----- line 622 movl %cr3,%ebx cmpl PCB_CR3(%edx),%ebx <----- trap je 4f I don't think this line is supposed to cause a trap... Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 3:59:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CC85A14FA9 for ; Mon, 15 Mar 1999 03:59:31 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id GAA20944; Mon, 15 Mar 1999 06:56:51 -0500 (EST) Date: Mon, 15 Mar 1999 06:56:51 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dmitrij Tejblum Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid In-Reply-To: <199903151024.NAA00520@tejblum.dnttm.rssi.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Mar 1999, Dmitrij Tejblum wrote: > Matthew Dillon wrote: > >=20 > > We'll get a quick fix committed but the lockmgr stuff needs a real > > going-over... having interrupts using the general lockmgr call is > > a disaster waiting to happen. >=20 > Hmmm. After I looked a bit further, it looks like a bug in the=20 > scheduler (?). Here is the stack trace: >=20 > #9 0xc01ff64e in trap (frame=3D{tf_es =3D 16, tf_ds =3D 16, tf_edi =3D 0= ,=20 > tf_esi =3D 16777216, tf_ebp =3D -999002708, tf_isp =3D -999002744,= =20 > tf_ebx =3D -1071228500, tf_edx =3D -2, tf_ecx =3D 0, tf_eax =3D 0,= =20 > tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -1072584332, tf_cs =3D 8= ,=20 > tf_eflags =3D 66050, tf_esp =3D -999002524, tf_ss =3D -1071228500}) > at ../../i386/i386/trap.c:438 > #10 0xc011a974 in lockmgr (lkp=3D0xc02659ac, flags=3D1, interlkp=3D0x0, p= =3D0x0) > at ../../kern/kern_lock.c:217 > #11 0xc01d8c5b in vm_map_lookup (var_map=3D0xc4746e64, vaddr=3D3294351360= ,=20 > fault_typea=3D1 '\001', out_entry=3D0xc4746e68, object=3D0xc4746e5c,= =20 > pindex=3D0xc4746e60, out_prot=3D0xc4746e4b "=C0\a", wired=3D0xc4746e4= 4) > at ../../vm/vm_map.c:2463 > #12 0xc01d4153 in vm_fault (map=3D0xc02659ac, vaddr=3D3294351360,=20 > fault_type=3D1 '\001', fault_flags=3D0) at ../../vm/vm_fault.c:197 > #13 0xc01ff9ac in trap_pfault (frame=3D0xc4746f18, usermode=3D0, eva=3D32= 94351360) > at ../../i386/i386/trap.c:825 > #14 0xc01ff64e in trap (frame=3D{tf_es =3D 16, tf_ds =3D 16, tf_edi =3D 4= 6137344,=20 > tf_esi =3D -1071149988, tf_ebp =3D -999002244, tf_isp =3D -99900230= 4,=20 > tf_ebx =3D 18341888, tf_edx =3D -1000615936, tf_ecx =3D -1005747008= ,=20 > tf_eax =3D 0, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -107165079= 6, tf_cs =3D 8,=20 > tf_eflags =3D 65606, tf_esp =3D -1072552121, tf_ss =3D -999654400}) > at ../../i386/i386/trap.c:438 > #15 0xc01fe814 in swtch_com () > #16 0xc01ff859 in trap (frame=3D{tf_es =3D 47, tf_ds =3D 47, tf_edi =3D 2= 0,=20 > tf_esi =3D 136019608, tf_ebp =3D -1077948228, tf_isp =3D -999002156= ,=20 > tf_ebx =3D 307, tf_edx =3D 136220264, tf_ecx =3D 136630944,=20 > tf_eax =3D 135716928, tf_trapno =3D 7, tf_err =3D 0, tf_eip =3D 134= 536416,=20 > tf_cs =3D 31, tf_eflags =3D 514, tf_esp =3D -1077948244, tf_ss =3D = 47}) > at ../../i386/i386/trap.c:195 > #17 0xc01f5aa3 in swi_ast_user () >=20 > the trap in swtch_com() (frame #15) is here: > /* switch address space */=09=09<----- line 622 > movl %cr3,%ebx > cmpl PCB_CR3(%edx),%ebx =09=09<----- trap > je 4f >=20 > I don't think this line is supposed to cause a trap... When it says "switch address space" What exactly do you think it's going to do? What I mean is, I'm pretty certain this is a good trap =3D) The real problem did seem to be the NULL p dereference, as it was obvious that it could happen in the code. >=20 > Dima >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman=09=09=09=09=09 _ __ ___ ___ ___ =20 green@unixhelp.org=09=09=09 _ __ ___ | _ ) __| \=20 =09 http://www.freebsd.org/=09 _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve!=09 _ __ ___ ____ _____ |___/___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 4: 4:48 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 689AF14F74 for ; Mon, 15 Mar 1999 04:04:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA10749; Mon, 15 Mar 1999 21:03:15 +0900 (JST) Message-ID: <36ECDDF8.1CCF419@newsguy.com> Date: Mon, 15 Mar 1999 19:16:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: dmaddox@conterra.com Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: boot -c not saving changes References: <19990314160034.A5912@dmaddox.conterra.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 "Donald J . Maddox" wrote: > > If you are *really* -current, /boot/loader.rc should probably > just contain something like: > > include /boot/loader.4th > start > > Then, you should copy /boot/defaults/loader.conf to /boot/loader.conf > and edit it to match what you want to happen at boot. Copying is dangerous. If you do not remove the loader_conf_files line, it will enter an infinite recursion. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 7:48:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id B6900150C0 for ; Mon, 15 Mar 1999 07:48:43 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id KAA16326; Mon, 15 Mar 1999 10:47:43 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903151547.KAA16326@misha.cisco.com> Subject: Re: cryptfs and friends In-Reply-To: <19990314142904.A4676@best.com> from "Jan B. Koum " at "Mar 14, 1999 02:29:04 pm" To: jkb@best.com (Jan B. Koum ) Date: Mon, 15 Mar 1999 10:47:42 -0500 (EST) Cc: current@freebsd.org Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > > => and on bringing the other goodies from > > => http://www.cs.columbia.edu/~ezk/research/index.html > Source for the cryptfs for FreeBSD. Do you have it? Nope... I thought, it would be in the same place as the am-utils source. And that is, indeed, so: ftp://shekel.mcl.cs.columbia.edu/pub/fist/ The cryptfs part itself is not there (the other parts are), for the US export restrictions, but the directory's .message directs you to http://www.cs.columbia.edu/~ezk/research/software/cryptfs/index.html for that missing piece... The other part of the package is usenetfs -- file system to improve performance of large article directories. Could this raise some interest? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 8:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id A1F18150C7 for ; Mon, 15 Mar 1999 08:39:35 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id RAA17232 for ; Mon, 15 Mar 1999 17:39:16 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id RAA01616 for current@freebsd.org; Mon, 15 Mar 1999 17:39:16 +0100 (MET) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.2/8.8.8) with ESMTP id RAA00633 for ; Mon, 15 Mar 1999 17:15:48 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Mon, 15 Mar 1999 17:15:48 +0100 (CET) From: Michael Reifenberger To: FreeBSD-Current Subject: PCIC (at least) and KLD's misbehaves 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, the way KLD's are handled seems to be bogus. I have -current and build with PCCARD support into the kernel ( controller card0 & device pcic0 & device pcic1 ) if /etc/rc.pccard gets executed it does a: ... if [ "X$pccard_enable" = X"YES" ] ; then if kldload pcic; then ... This leads to a second load (and execution) of pcic.ko which is bogus because the driver is allready initialized. I think this is a general problem of not using semaphores for this kind of configuration. Shouldn't be the solution the usage of *.ko objects regardless if they are linked statically into the kernel or dynamically during startup or the definition of semaphores for each logical device which gets set if statically build. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 8:39:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.39.177.166]) by hub.freebsd.org (Postfix) with ESMTP id AA5ED150C8; Mon, 15 Mar 1999 08:39:35 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: from totum.plaut.de (totum.plaut.de [194.39.177.9]) by ns.plaut.de (8.8.8/8.8.7) with ESMTP id RAA17236; Mon, 15 Mar 1999 17:39:16 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by totum.plaut.de (8.8.7/8.7.3) with UUCP id RAA01617; Mon, 15 Mar 1999 17:39:16 +0100 (MET) Received: from localhost (root@localhost) by nihil.plaut.de (8.9.2/8.8.8) with ESMTP id RAA00662; Mon, 15 Mar 1999 17:25:38 +0100 (CET) (envelope-from root@nihil.plaut.de) Date: Mon, 15 Mar 1999 17:25:38 +0100 (CET) From: Michael Reifenberger To: FreeBSD-Current Cc: dirk@freebsd.org Subject: latest -current doesn't execute BSDI-binary bladeenc 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, just for the record (as it is allready documented ) the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc) an MPEG3 encoder. Former kernels did. So one should either fix the kernel or BROKEN=YES the bladeenc Port or use the linux executable (if it works at all) Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 8:48:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id E640D15123 for ; Mon, 15 Mar 1999 08:47:55 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id RAA13734; Mon, 15 Mar 1999 17:47:36 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id 0E0A3D21A; Mon, 15 Mar 1999 17:47:35 +0100 (CET) Message-ID: <19990315174734.A400@enst.fr> Date: Mon, 15 Mar 1999 17:47:34 +0100 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: panic: vfs_busy: unexpected lock failure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, My FreeBSD box keeps panicing when I'm trying to do a simple "cp -rp" from a local disk to a NFS-mounted disk. The NFS server is a Solaris 2.5 box; the NFS partition is mounted through amd. The files I try to copy are just sendmail's cf directory (lots of small files) and the panic happens every time I try (with cp -rp; not with piped tars). The kernel is today's, with NFS compiled-in (it's not a module). I'm having the following message: panic: vfs_busy: unexpected lock failure -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 10:59:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 45BBD14C98 for ; Mon, 15 Mar 1999 10:59:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA01757; Mon, 15 Mar 1999 10:59:25 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 10:59:25 -0800 (PST) From: Matthew Dillon Message-Id: <199903151859.KAA01757@apollo.backplane.com> To: Brian Feldman Cc: Dmitrij Tejblum , current@FreeBSD.ORG Subject: Re: Simple DOS against 3.x locks box solid References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Matthew Dillon wrote: :> > :> > We'll get a quick fix committed but the lockmgr stuff needs a real :> > going-over... having interrupts using the general lockmgr call is :> > a disaster waiting to happen. :> :> Hmmm. After I looked a bit further, it looks like a bug in the :> scheduler (?). Here is the stack trace: :> :> #9 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, :> tf_esi = 16777216, tf_ebp = -999002708, tf_isp = -999002744, :> tf_ebx = -1071228500, tf_edx = -2, tf_ecx = 0, tf_eax = 0, :> tf_trapno = 12, tf_err = 0, tf_eip = -1072584332, tf_cs = 8, :... :> at ../../i386/i386/trap.c:195 :> #17 0xc01f5aa3 in swi_ast_user () :> :> the trap in swtch_com() (frame #15) is here: :> /* switch address space */ <----- line 622 :> movl %cr3,%ebx :> cmpl PCB_CR3(%edx),%ebx <----- trap :> je 4f :> :> I don't think this line is supposed to cause a trap... : :When it says "switch address space" What exactly do you think it's going to :do? What I mean is, I'm pretty certain this is a good trap =) : :The real problem did seem to be the NULL p dereference, as it was obvious :that it could happen in the code. I don't think the system is supposed to trap there. -Matt : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 11:39:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 8598A15153 for ; Mon, 15 Mar 1999 11:39:41 -0800 (PST) (envelope-from schuerge@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id UAA21648 for ; Mon, 15 Mar 1999 20:39:19 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (wurzelausix.cs.uni-sb.de [134.96.247.1]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id UAA02471 for ; Mon, 15 Mar 1999 20:39:18 +0100 (CET) Received: (from schuerge@localhost) by wurzelausix.cs.uni-sb.de (8.9.1/wjp/19980821) id UAA26529 for freebsd-current@freebsd.org; Mon, 15 Mar 1999 20:39:17 +0100 (CET) From: Thomas Schuerger Message-Id: <199903151939.UAA26529@wurzelausix.cs.uni-sb.de> Subject: SMP To: freebsd-current@freebsd.org Date: Mon, 15 Mar 1999 20:39:17 +0100 (CET) X-Mailer: ELM [version 2.4 PL24] 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! Will an SMP Kernel of 4.0-Current for two processors also run on one processor? I'd like to check whether the SMP-kernel runs stable on my Asus P2B-DS with two processors, but I'd like to be able to switch back to the non-SMP kernel afterwards. Ciao, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 11:49:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from carbon.marathon.org (carbon.marathon.org [209.180.116.41]) by hub.freebsd.org (Postfix) with ESMTP id 8A4561512B; Mon, 15 Mar 1999 11:48:53 -0800 (PST) (envelope-from nje@carbon.marathon.org) Received: from localhost (nje@localhost) by carbon.marathon.org (8.9.2/8.9.2) with ESMTP id MAA17446; Mon, 15 Mar 1999 12:47:51 -0700 (MST) (envelope-from nje@carbon.marathon.org) Date: Mon, 15 Mar 1999 12:47:51 -0700 (MST) From: Nicholas Esborn To: Matthew Dillon Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Diskless boot stopping at "NFS ROOT:..." In-Reply-To: <199903141922.LAA93438@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 Thanks for the pointer. This seems to have been the problem and I have it booting now. As a followup, is it possible to specify boot parameters (i.e. splash screen, pnp config, etc) on a machine that is net booting? Thanks for the help. Nick On Sun, 14 Mar 1999, Matthew Dillon wrote: > I had a very weird problem with the new parallel port device that caused > this to occur. It turned out to be speculative probing by the parallel > device causing the system to go unstable. > > Try disabling the new parallel port device(s)/controllers and see if you > can boot again. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 12:37: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 8E1F614F90 for ; Mon, 15 Mar 1999 12:37:04 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id HAA08593; Tue, 16 Mar 1999 07:36:45 +1100 Date: Tue, 16 Mar 1999 07:36:45 +1100 From: Bruce Evans Message-Id: <199903152036.HAA08593@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, dima@tejblum.dnttm.rssi.ru Subject: Re: Simple DOS against 3.x locks box solid Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >#14 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 46137344, > tf_esi = -1071149988, tf_ebp = -999002244, tf_isp = -999002304, > tf_ebx = 18341888, tf_edx = -1000615936, tf_ecx = -1005747008, > tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071650796, tf_cs = 8, > tf_eflags = 65606, tf_esp = -1072552121, tf_ss = -999654400}) > at ../../i386/i386/trap.c:438 >#15 0xc01fe814 in swtch_com () >#16 0xc01ff859 in trap (frame={tf_es = 47, tf_ds = 47, tf_edi = 20, > tf_esi = 136019608, tf_ebp = -1077948228, tf_isp = -999002156, > tf_ebx = 307, tf_edx = 136220264, tf_ecx = 136630944, > tf_eax = 135716928, tf_trapno = 7, tf_err = 0, tf_eip = 134536416, > tf_cs = 31, tf_eflags = 514, tf_esp = -1077948244, tf_ss = 47}) > at ../../i386/i386/trap.c:195 >#17 0xc01f5aa3 in swi_ast_user () > >the trap in swtch_com() (frame #15) is here: > /* switch address space */ <----- line 622 > movl %cr3,%ebx > cmpl PCB_CR3(%edx),%ebx <----- trap > je 4f > >I don't think this line is supposed to cause a trap... I would expect a trap here if the pcb for the new process is swapped out. The code obviously doesn't expect it: 1) curproc is still 0. This is correct, since the process is not fully switched to. Apparently vm_fault isn't fully aware of this possibility. 2) CPU interrupts are disabled. Interrupts probably only need to be disabled while the runqueues are being tested and set, and splhigh() is sufficient. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 13:25:15 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 CBA4215322 for ; Mon, 15 Mar 1999 13:25:13 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA02779; Mon, 15 Mar 1999 13:24:46 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 13:24:46 -0800 (PST) From: Matthew Dillon Message-Id: <199903152124.NAA02779@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hello, : :My FreeBSD box keeps panicing when I'm trying to do a simple "cp :-rp" from a local disk to a NFS-mounted disk. The NFS server is a :Solaris 2.5 box; the NFS partition is mounted through amd. : :The files I try to copy are just sendmail's cf directory (lots of :small files) and the panic happens every time I try (with cp -rp; :not with piped tars). : :The kernel is today's, with NFS compiled-in (it's not a module). : :I'm having the following message: : panic: vfs_busy: unexpected lock failure :-- :Pierre Beyssac pb@enst.fr Compile up a kernel with 'options DDB' and get a backtrace when it panics next ( 'trace' command from DDB prompt ). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 13:34:51 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 4DEA914EE8; Mon, 15 Mar 1999 13:34:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA02842; Mon, 15 Mar 1999 13:34:22 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Mar 1999 13:34:22 -0800 (PST) From: Matthew Dillon Message-Id: <199903152134.NAA02842@apollo.backplane.com> To: Nicholas Esborn Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Diskless boot stopping at "NFS ROOT:..." References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Thanks for the pointer. This seems to have been the problem and I have it :booting now. As a followup, is it possible to specify boot parameters :(i.e. splash screen, pnp config, etc) on a machine that is net booting? : :Thanks for the help. : :Nick : :On Sun, 14 Mar 1999, Matthew Dillon wrote: : :> I had a very weird problem with the new parallel port device that caused Try this patch. This is what I had to do to make my machines work without crashing. If this solves your problem, I would really appreciate it if the people developing the new parallel port stuff would look into it further and perhaps make these probes optional rather then the default. This could become a disaster if it remains a problem through on the next release. -Matt Matthew Dillon Index: i386/isa/ppc.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/ppc.c,v retrieving revision 1.20 diff -u -r1.20 ppc.c --- ppc.c 1999/02/14 22:02:47 1.20 +++ ppc.c 1999/03/15 21:32:40 @@ -1066,9 +1066,11 @@ /* list of supported chipsets */ int (*chipset_detect[])(struct ppc_data *, int) = { +#if 0 ppc_pc873xx_detect, ppc_smc37c66xgt_detect, ppc_w83877f_detect, +#endif ppc_generic_detect, NULL }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 14: 8:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 89DED1502B; Mon, 15 Mar 1999 14:08:23 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id XAA12544; Mon, 15 Mar 1999 23:07:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id XAA22922; Mon, 15 Mar 1999 23:07:49 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Nicholas Esborn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Diskless boot stopping at "NFS ROOT:..." In-reply-to: Your message of "Mon, 15 Mar 1999 13:34:22 PST." <199903152134.NAA02842@apollo.backplane.com> Date: Mon, 15 Mar 1999 23:07:49 +0100 Message-ID: <22920.921535669@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903152134.NAA02842@apollo.backplane.com>, Matthew Dillon writes: Shouldn't this be detected by PCI-id rather than by brute force probing ? >:> I had a very weird problem with the new parallel port device that caused > > Try this patch. This is what I had to do to make my machines work > without crashing. > > If this solves your problem, I would really appreciate it if the > people developing the new parallel port stuff would look into it > further and perhaps make these probes optional rather then the > default. This could become a disaster if it remains a problem through > on the next release. > > -Matt > Matthew Dillon > > > >Index: i386/isa/ppc.c >=================================================================== >RCS file: /home/ncvs/src/sys/i386/isa/ppc.c,v >retrieving revision 1.20 >diff -u -r1.20 ppc.c >--- ppc.c 1999/02/14 22:02:47 1.20 >+++ ppc.c 1999/03/15 21:32:40 >@@ -1066,9 +1066,11 @@ > > /* list of supported chipsets */ > int (*chipset_detect[])(struct ppc_data *, int) = { >+#if 0 > ppc_pc873xx_detect, > ppc_smc37c66xgt_detect, > ppc_w83877f_detect, >+#endif > ppc_generic_detect, > NULL > }; > > >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 Mon Mar 15 14:17:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id BA5771588A; Mon, 15 Mar 1999 14:17:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA00926; Mon, 15 Mar 1999 14:06:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903152206.OAA00926@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Matthew Dillon , Nicholas Esborn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Diskless boot stopping at "NFS ROOT:..." In-reply-to: Your message of "Mon, 15 Mar 1999 23:07:49 +0100." <22920.921535669@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 14:06:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199903152134.NAA02842@apollo.backplane.com>, Matthew Dillon writes: > > Shouldn't this be detected by PCI-id rather than by brute force probing ? Since these are ISA chipsets, no. They're not (all) PnP devices either, unfortunately. > > >:> I had a very weird problem with the new parallel port device that caused > > > > Try this patch. This is what I had to do to make my machines work > > without crashing. > > > > If this solves your problem, I would really appreciate it if the > > people developing the new parallel port stuff would look into it > > further and perhaps make these probes optional rather then the > > default. This could become a disaster if it remains a problem through > > on the next release. > > > > -Matt > > Matthew Dillon > > > > > > > >Index: i386/isa/ppc.c > >=================================================================== > >RCS file: /home/ncvs/src/sys/i386/isa/ppc.c,v > >retrieving revision 1.20 > >diff -u -r1.20 ppc.c > >--- ppc.c 1999/02/14 22:02:47 1.20 > >+++ ppc.c 1999/03/15 21:32:40 > >@@ -1066,9 +1066,11 @@ > > > > /* list of supported chipsets */ > > int (*chipset_detect[])(struct ppc_data *, int) = { > >+#if 0 > > ppc_pc873xx_detect, > > ppc_smc37c66xgt_detect, > > ppc_w83877f_detect, > >+#endif > > ppc_generic_detect, > > NULL > > }; > > > > > >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-stable" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 14:39:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (Postfix) with ESMTP id BB83E14CC2 for ; Mon, 15 Mar 1999 14:39:34 -0800 (PST) (envelope-from myself@conterra.com) Received: from dmaddox.conterra.com (myself@dmaddox.conterra.com [209.12.169.48]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id RAA11021; Mon, 15 Mar 1999 17:39:09 -0500 (EST) Received: (from myself@localhost) by dmaddox.conterra.com (8.9.3/8.9.1) id RAA01031; Mon, 15 Mar 1999 17:39:13 -0500 (EST) (envelope-from myself) Date: Mon, 15 Mar 1999 17:39:13 -0500 From: "Donald J . Maddox" To: "Daniel C. Sobral" Cc: dmaddox@conterra.com, Donn Miller , current@FreeBSD.ORG Subject: Re: boot -c not saving changes Message-ID: <19990315173913.B971@dmaddox.conterra.com> Reply-To: dmaddox@conterra.com References: <19990314160034.A5912@dmaddox.conterra.com> <36ECDDF8.1CCF419@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <36ECDDF8.1CCF419@newsguy.com>; from Daniel C. Sobral on Mon, Mar 15, 1999 at 07:16:24PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 07:16:24PM +0900, Daniel C. Sobral wrote: > "Donald J . Maddox" wrote: > > > > If you are *really* -current, /boot/loader.rc should probably > > just contain something like: > > > > include /boot/loader.4th > > start > > > > Then, you should copy /boot/defaults/loader.conf to /boot/loader.conf > > and edit it to match what you want to happen at boot. > > Copying is dangerous. If you do not remove the loader_conf_files > line, it will enter an infinite recursion. Interestingly enough, I copied /boot/defaults/loader.conf to /boot/loader.conf, edited it, and rebooted (not removing the loader_conf_files line) and it boots just fine, with no recursion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 15:29:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id CF33914D1E for ; Mon, 15 Mar 1999 15:29:36 -0800 (PST) (envelope-from ibex@emmi.physik.TU-Berlin.DE) Received: (from ibex@localhost) by emmi.physik.TU-Berlin.DE (8.9.2/8.9.2) id AAA38889; Tue, 16 Mar 1999 00:29:15 +0100 (CET) (envelope-from ibex) Date: Tue, 16 Mar 1999 00:29:15 +0100 From: Dirk Froemberg To: Michael Reifenberger Cc: FreeBSD-Current Subject: Re: latest -current doesn't execute BSDI-binary bladeenc Message-ID: <19990316002915.A38782@physik.TU-Berlin.DE> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Michael Reifenberger on Mon, Mar 15, 1999 at 05:25:38PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Michael! On Mon, Mar 15, 1999 at 05:25:38PM +0100, Michael Reifenberger wrote: > just for the record (as it is allready documented ) > the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc) > an MPEG3 encoder. Former kernels did. Yes, this was discussed on freebsd-committers. > So one should either fix the kernel or BROKEN=YES the bladeenc Port or use the > linux executable (if it works at all) As a workaround I'll mark bladeenc as BROKEN for FreeBSD-current. As a better solution I'll ask the original author for a native FreeBSD version. Regards Dirk -- e-mail: dirk@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 16:24: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E759715168; Mon, 15 Mar 1999 16:23:39 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA02090; Tue, 16 Mar 1999 10:53:20 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990316002915.A38782@physik.TU-Berlin.DE> Date: Tue, 16 Mar 1999 10:53:20 +1030 (CST) From: "Daniel O'Connor" To: Dirk Froemberg Subject: Re: latest -current doesn't execute BSDI-binary bladeenc Cc: FreeBSD-Current Cc: FreeBSD-Current , Michael Reifenberger Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Mar-99 Dirk Froemberg wrote: > > So one should either fix the kernel or BROKEN=YES the bladeenc Port or use the > > linux executable (if it works at all) > > As a workaround I'll mark bladeenc as BROKEN for FreeBSD-current. > As a better solution I'll ask the original author for a native FreeBSD > version. Here is the URL for a statically linked Linux binary http://home8.swipnet.se/~w-82625/encoder/binaries/BladeEnc-076-i386-linux.tar.gz It seems to work fine except it core dumps on exit for some reason. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 16:29:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id A3386153D8; Mon, 15 Mar 1999 16:29:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01601; Mon, 15 Mar 1999 16:21:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903160021.QAA01601@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" Cc: Dirk Froemberg , FreeBSD-Current , Michael Reifenberger Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-reply-to: Your message of "Tue, 16 Mar 1999 10:53:20 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Mar 1999 16:21:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It seems to work fine except it core dumps on exit for some reason. > Marcel fixed that one a while back; update your system. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 15 16:40:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 62E6D15407 for ; Mon, 15 Mar 1999 16:39:50 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id TAA15366 for current@freebsd.org; Mon, 15 Mar 1999 19:38:30 -0500 (EST) From: Mikhail Teterin Message-Id: <199903160038.TAA15366@kot.ne.mediaone.net> Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-Reply-To: <19990316002915.A38782@physik.TU-Berlin.DE> from Dirk Froemberg at "Mar 16, 1999 00:29:15 am" To: current@freebsd.org Date: Mon, 15 Mar 1999 19:38:30 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Mon, 15 Mar 1999 23:30:56 -0800 (PST) (envelope-from s4362021@cc.ncu.edu.tw) Received: from NET.H2.NU ([140.115.81.98]) by mail.cc.ncu.edu.tw (8.9.1/8.9.1/SUN/Solaris) with SMTP id PAA08783 for ; Tue, 16 Mar 1999 15:28:08 +0800 (CST) From: "=?big5?B?rUqlv73l?=" To: Subject: About Compile with ELF... Date: Tue, 16 Mar 1999 15:30:53 +0800 Message-ID: <000001be6f7e$eca8cb00$6251738c@NET.H2.NU> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi...ALL...: Now my system had install FreeBSD 3.1 Release and cnet-1.4p3 with package (not porting). But when I run cnet It shows the following message: >cnet TICKTOCK Warning - DISPLAY variable not defined, using ASCI environment Linking ticktock.cnet cc : could not exec elf/cc in usr/libexec : No such file or directory What does it mean? I checked the dir in /usr/libexec/elf and I can't fine the file "cc" How should I install it?! Thanx for your help... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 2:11:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id C74B015205 for ; Tue, 16 Mar 1999 02:11:06 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from email.enst.fr (muse-2.enst.fr [137.194.2.33]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id LAA18990; Tue, 16 Mar 1999 11:10:43 +0100 (MET) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by email.enst.fr (8.9.3/8.9.3) with ESMTP id LAA07316; Tue, 16 Mar 1999 11:10:42 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id 0C101D21A; Tue, 16 Mar 1999 11:10:41 +0100 (CET) Message-ID: <19990316111040.A384@enst.fr> Date: Tue, 16 Mar 1999 11:10:40 +0100 From: Pierre Beyssac To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903152124.NAA02779@apollo.backplane.com>; from Matthew Dillon on Mon, Mar 15, 1999 at 01:24:46PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote: > Compile up a kernel with 'options DDB' and get a backtrace when > it panics next ( 'trace' command from DDB prompt ). Ok, here goes. The kernel is compiled without -g for the moment, but I've provided the function offsets if that may help. vfs_busy() at vfs_busy+0x6d lookup() +0x3b9 namei() +0x180 stat() +0x44 syscall() +0x187 I also get what seems to be spurious EPROTONOSUPPORT errors that show up in cp while copying files... -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 2:47:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id 987F31520F for ; Tue, 16 Mar 1999 02:47:20 -0800 (PST) (envelope-from ibex@emmi.physik.TU-Berlin.DE) Received: (from ibex@localhost) by emmi.physik.TU-Berlin.DE (8.9.2/8.9.2) id LAA51037; Tue, 16 Mar 1999 11:46:56 +0100 (CET) (envelope-from ibex) Date: Tue, 16 Mar 1999 11:46:56 +0100 From: Dirk Froemberg To: tord.jansson@swipnet.se Cc: current@freebsd.org Subject: bladeenc for FreeBSD Message-ID: <19990316114656.A50450@physik.TU-Berlin.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Tord! I maintain an port of bladeenc for FreeBSD (see http://www.se.freebsd.org/ports/audio.html#bladeenc-0.76 for details). Unfortunally the latest FreeBSD version isn't able to execute BSDI binaries, even not if they are statically linked. So it would be really be nice to have a native FreeBSD-i386 version of bladeenc. If you don't have access to a 3.1-FreeBSD-system or later yourself I can offer you an account on a machine in Germany. Best regards Dirk -- e-mail: dirk@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 3: 6:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (Postfix) with ESMTP id D7CA2150EE for ; Tue, 16 Mar 1999 03:06:51 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:32017 "EHLO mediaport.org" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with ESMTP id <8030-17327>; Tue, 16 Mar 1999 12:06:22 +0100 Message-ID: <36EE3AEF.97B1B155@mediaport.org> Date: Tue, 16 Mar 1999 12:05:19 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Current Subject: Cryptfs available outside US References: <19990316002915.A38782@physik.TU-Berlin.DE> 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 seem to remember someone requesting cryptfs. It's available outside the US on my webserver: http://wit395301.student.utwente.nl/~gelderen/fist/. It will go to replay soon. Cheers, Jeroen -- Jeroen C. van Gelderen - gelderen@mediaport.org - 0xC33EDFDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 5:37: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6526C15179 for ; Tue, 16 Mar 1999 05:36:57 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA23235 for current@freebsd.org; Tue, 16 Mar 1999 14:36:38 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903161336.OAA23235@freebsd.dk> Subject: HEADS UP!! atapi CDROM driver name change To: current@freebsd.org Date: Tue, 16 Mar 1999 14:36:38 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The name of the old wd.c and atapi.c based CDROM driver has been changed back to wcd. So update your config file to use "device wcd" instead of "device acd". This is to avoid confusion with the new ATA/ATAPI system. MAKEDEV has also been changed to reflect this, and to support the device nodes of the new system. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 6:23:27 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 E930D14EBE for ; Tue, 16 Mar 1999 06:23:23 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA04732; Tue, 16 Mar 1999 23:23:13 +0900 (JST) Message-ID: <36EE5180.D5B8C1F5@newsguy.com> Date: Tue, 16 Mar 1999 21:41:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: mi@aldan.algebra.com Cc: "Jan B. Koum" , current@FreeBSD.ORG Subject: Re: cryptfs and friends References: <199903151547.KAA16326@misha.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > for that missing piece... The other part of the package is usenetfs > -- file system to improve performance of large article directories. > Could this raise some interest? News servers are one of FreeBSD niches. I'd say this would definitely generate interest. Frankly, /usr/ports/fs generating kld's would be welcome in FreeBSD. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 7:31:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (Postfix) with ESMTP id 4391D15369 for ; Tue, 16 Mar 1999 07:30:56 -0800 (PST) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.9.1/8.8.8) id JAA27325 for current@FreeBSD.ORG; Tue, 16 Mar 1999 09:29:52 -0600 (CST) (envelope-from pmckenna) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 16 Mar 1999 09:29:52 -0600 (CST) From: Pete Mckenna To: current@FreeBSD.ORG Subject: IDE tape drive support Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do the AIWA bolt and Sony superstation tape drives work with the new ATA/ATAPI driver or the old drivers ? I've been following Soren's posting on the new driver but haven't seen mention of this, and saw on linux lists that they seemed to be writting specific drivers for these drives. Are they non-standard ? Can someone help me out with this ? Pete ---------------------------------- E-Mail: Pete Mckenna Date: 16-Mar-99 Time: 09:22:39 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 Tue Mar 16 8:46:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (Postfix) with ESMTP id D2E00152B3 for ; Tue, 16 Mar 1999 08:46:16 -0800 (PST) (envelope-from druber@mail.kersur.net) Received: from localhost (druber@localhost) by mail.kersur.net (8.9.1/8.9.1) with SMTP id LAA19131; Tue, 16 Mar 1999 11:50:53 -0500 (EST) Date: Tue, 16 Mar 1999 11:50:53 -0500 (EST) From: Dan Swartzendruber To: "Daniel C. Sobral" Cc: mi@aldan.algebra.com, "Jan B. Koum" , current@FreeBSD.ORG Subject: Re: cryptfs and friends In-Reply-To: <36EE5180.D5B8C1F5@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 Tue, 16 Mar 1999, Daniel C. Sobral wrote: > Mikhail Teterin wrote: > > > > for that missing piece... The other part of the package is usenetfs > > -- file system to improve performance of large article directories. > > Could this raise some interest? > > News servers are one of FreeBSD niches. I'd say this would > definitely generate interest. It sure would with me! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 9:58:17 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 6FFC01500C for ; Tue, 16 Mar 1999 09:56:59 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id SAA10909 for ; Tue, 16 Mar 1999 18:59:37 +0100 (MET) Date: Tue, 16 Mar 1999 18:56:34 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list Subject: panic occurred: vm_fault Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In case someone who is interested in the following panic: Occurred under a lightly loaded system that was not doing anything apart from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512). Kernel current as of yesterday. No core file is available unfortunately. panic: vm_fault: fault on nofault entry, addr: c35c6000 (blabla about debugger) > show registers cs 0x8 ds 0x10 es 0x10 ss 0x10 eax 0x12 ecx 0xc00b8f00 edx 0xc024d1a4 db_lengths+0x11c ebx 0xc0248255 __set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9 esp 0xc6f23ca8 ebp 0xc6f23cb0 esi 0x100 edi 0xc35c6000 eip 0xc020f993 Debugger+0x37 efl 0x256 > trace panic vm_fault trap_pfault trap calltrap() --- trap slow_copyout spec_read ufsspec_read ufs_vnoperatespec vn_read read syscall Xint0x80syscall -- 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 Tue Mar 16 10: 7: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 2B45D14FFC for ; Tue, 16 Mar 1999 10:07:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id TAA23665; Tue, 16 Mar 1999 19:07:07 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903161807.TAA23665@freebsd.dk> Subject: Re: IDE tape drive support In-Reply-To: from Pete Mckenna at "Mar 16, 1999 9:29:52 am" To: pmckenna@uswest.net (Pete Mckenna) Date: Tue, 16 Mar 1999 19:07:06 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Pete Mckenna wrote: > Do the AIWA bolt and Sony superstation tape drives work with the new > ATA/ATAPI driver or the old drivers ? > I've been following Soren's posting on the new driver but haven't seen mention > of this, and saw on linux lists that they seemed to be writting specific drivers > for these drives. Are they non-standard ? Can someone help me out with this ? No idea, but if they claim to be ATAPI compatible, they should work, but then again.... However if anybody has an urgent need for a special driver, let me now by sending me a drive :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 10:15:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id DB389150D3 for ; Tue, 16 Mar 1999 10:14:48 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id SAA41522 for ; Tue, 16 Mar 1999 18:14:26 GMT Message-ID: <36EE9F81.75B2D33F@tdx.co.uk> Date: Tue, 16 Mar 1999 18:14:25 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: FTP client dies when not in passive mode? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This may have been covered before (searching the archives for 'ftp' wasn't such a hot idea :) Is there any way to stop the FTP client from either taking _ages_, or just dying stone dead (i.e. CTRL-\ is the only way out - forcing a core dump) when connecting through Firewalls that only allow Passive FTP? The moment you do an 'ls' or 'get' after having forgotten to do a 'pas' (to switch to passive mode) you suddenly find yourself unable to CTRL-C out of the FTP client - admittedly it does quit after around 5 minutes with "425 Can't build data connection: Connection timeout" - Or should I just be grateful we have a passive mode, unlike some other Win/NT versions? :) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 10:51:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 3D41A15041 for ; Tue, 16 Mar 1999 10:51:16 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id MAA25341; Tue, 16 Mar 1999 12:50:39 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id MAA25337; Tue, 16 Mar 1999 12:50:38 -0600 (CST) Message-ID: <013001be6fdd$f3dff970$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Nick Hibma" , "FreeBSD current mailing list" Subject: Re: panic occurred: vm_fault Date: Tue, 16 Mar 1999 12:51:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have run into this in the past too, when a bad file was encountered on the CD (home burned CDR). The system did not shut down though, it just kept on working. Tom Veldhouse veldy@visi.com -----Original Message----- From: Nick Hibma To: FreeBSD current mailing list Date: Tuesday, March 16, 1999 12:40 PM Subject: panic occurred: vm_fault > >In case someone who is interested in the following panic: > >Occurred under a lightly loaded system that was not doing anything apart >from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512). >Kernel current as of yesterday. >No core file is available unfortunately. > > >panic: vm_fault: fault on nofault entry, addr: c35c6000 >(blabla about debugger) >> show registers >cs 0x8 >ds 0x10 >es 0x10 >ss 0x10 >eax 0x12 >ecx 0xc00b8f00 >edx 0xc024d1a4 db_lengths+0x11c >ebx 0xc0248255 >__set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9 >esp 0xc6f23ca8 >ebp 0xc6f23cb0 >esi 0x100 >edi 0xc35c6000 >eip 0xc020f993 Debugger+0x37 >efl 0x256 >> trace >panic >vm_fault >trap_pfault >trap >calltrap() >--- trap >slow_copyout >spec_read >ufsspec_read >ufs_vnoperatespec >vn_read >read >syscall >Xint0x80syscall > > >-- >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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:12:13 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 60A8B14F0B for ; Tue, 16 Mar 1999 11:12:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11778; Tue, 16 Mar 1999 11:11:44 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 11:11:44 -0800 (PST) From: Matthew Dillon Message-Id: <199903161911.LAA11778@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote: :> Compile up a kernel with 'options DDB' and get a backtrace when :> it panics next ( 'trace' command from DDB prompt ). : :Ok, here goes. The kernel is compiled without -g for the moment, :but I've provided the function offsets if that may help. : :vfs_busy() at vfs_busy+0x6d :lookup() +0x3b9 :namei() +0x180 :stat() +0x44 :syscall() +0x187 : :I also get what seems to be spurious EPROTONOSUPPORT errors that :show up in cp while copying files... :-- :Pierre Beyssac pb@enst.fr The code in lookup() that calls vfs_busy() is: while (dp->v_type == VDIR && (mp = dp->v_mountedhere) && (cnp->cn_flags & NOCROSSMOUNT) == 0) { if (vfs_busy(mp, 0, 0, p)) continue; error = VFS_ROOT(mp, &tdp); vfs_unbusy(mp, p); if (error) goto bad2; vput(dp); ndp->ni_vp = dp = tdp; } You shouldn't be crossing a mount point. Are you by chance doing a recursive copy onto itself? e.g. cp -rp src dest where dest is mounted under src somewhere ? Of course, it is still a serious kernel bug. I would like to try to reproduce it in order to track it down. How are things mounted on your system ( df ) and what are the *exact* arguments you are using with cp? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:16:17 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 13E2A1516B for ; Tue, 16 Mar 1999 11:16:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA11827; Tue, 16 Mar 1999 11:15:49 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 11:15:49 -0800 (PST) From: Matthew Dillon Message-Id: <199903161915.LAA11827@apollo.backplane.com> To: Nick Hibma Cc: FreeBSD current mailing list Subject: Re: panic occurred: vm_fault References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the panic reproduceable? What is the CCD configuration? -Matt Matthew Dillon :In case someone who is interested in the following panic: : :Occurred under a lightly loaded system that was not doing anything apart :from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512). :Kernel current as of yesterday. :No core file is available unfortunately. : : :panic: vm_fault: fault on nofault entry, addr: c35c6000 :(blabla about debugger) :> show registers :cs 0x8 :ds 0x10 :es 0x10 :ss 0x10 :eax 0x12 :ecx 0xc00b8f00 :edx 0xc024d1a4 db_lengths+0x11c :ebx 0xc0248255 :__set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9 :esp 0xc6f23ca8 :ebp 0xc6f23cb0 :esi 0x100 :edi 0xc35c6000 :eip 0xc020f993 Debugger+0x37 :efl 0x256 :> trace :panic :vm_fault :trap_pfault :trap :calltrap() :--- trap :slow_copyout :spec_read :ufsspec_read :ufs_vnoperatespec :vn_read :read :syscall :Xint0x80syscall : : :-- :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 Tue Mar 16 11:16:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (Postfix) with ESMTP id C7E4115309 for ; Tue, 16 Mar 1999 11:16:38 -0800 (PST) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.9.1/8.8.8) id NAA28623; Tue, 16 Mar 1999 13:12:49 -0600 (CST) (envelope-from pmckenna) 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: <199903161807.TAA23665@freebsd.dk> Date: Tue, 16 Mar 1999 13:12:49 -0600 (CST) From: Pete Mckenna To: =?us-ascii?Q?S=F8ren?= Schmidt Subject: Re: IDE tape drive support Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren, Here's what Aiwa has to say; BOLT utilizes an ATAPI (IDE) interface. It connects to an existing IDE interface as either master or slave. To configure, simply enter a single jumper setting. AIWA BOLT uses Travan drive hardware and records on Travan 3 cartridges, although with a different format. I guess I'll be the guinea pig and send it to you if it can't be made to work. Pete On 16-Mar-99 Søren Schmidt wrote: > It seems Pete Mckenna wrote: >> Do the AIWA bolt and Sony superstation tape drives work with the new >> ATA/ATAPI driver or the old drivers ? >> I've been following Soren's posting on the new driver but haven't seen >> mention >> of this, and saw on linux lists that they seemed to be writting specific >> drivers >> for these drives. Are they non-standard ? Can someone help me out with this >> ? > > No idea, but if they claim to be ATAPI compatible, they should work, but > then again.... > However if anybody has an urgent need for a special driver, let me now > by sending me a drive :) > > -Søren ---------------------------------- E-Mail: Pete Mckenna Date: 16-Mar-99 Time: 13:01:26 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 Tue Mar 16 11:22: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 9DF6815041 for ; Tue, 16 Mar 1999 11:22:49 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10MzPt-000HSE-00; Tue, 16 Mar 1999 21:22:17 +0200 From: Sheldon Hearn To: Karl Pielorz Cc: current@freebsd.org Subject: Re: FTP client dies when not in passive mode? In-reply-to: Your message of "Tue, 16 Mar 1999 18:14:25 GMT." <36EE9F81.75B2D33F@tdx.co.uk> Date: Tue, 16 Mar 1999 21:22:17 +0200 Message-ID: <67097.921612137@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Mar 1999 18:14:25 GMT, Karl Pielorz wrote: > Is there any way to stop the FTP client from either taking _ages_, or > just dying stone dead (i.e. CTRL-\ is the only way out - forcing a > core dump) when connecting through Firewalls that only allow Passive > FTP? alias ftp='ftp -p' or alias ftp='pftp' See the ftp(1) manpage for an explanation. In future, please refer general questions related to FreeBSD to the freebsd-questions mailing list -- freebsd-current is for issues relating specifically to CURRENT (4.0-CURRENT at the moment). Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:23: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DAAC61524C for ; Tue, 16 Mar 1999 11:23:02 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA23779; Tue, 16 Mar 1999 20:22:41 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903161922.UAA23779@freebsd.dk> Subject: Re: IDE tape drive support In-Reply-To: from Pete Mckenna at "Mar 16, 1999 1:12:49 pm" To: pmckenna@uswest.net (Pete Mckenna) Date: Tue, 16 Mar 1999 20:22:41 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Pete Mckenna wrote: > Soren, > > Here's what Aiwa has to say; > BOLT utilizes an ATAPI (IDE) interface. It connects to an existing IDE interface > as either master or slave. To configure, simply enter a single jumper setting. > AIWA BOLT uses Travan drive hardware and records on Travan 3 cartridges, > although with a different format. > > I guess I'll be the guinea pig and send it to you if it can't be made to work. Deal! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:34:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id BBE281550F for ; Tue, 16 Mar 1999 11:33:27 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3/Kp) with ESMTP id TAA68202; Tue, 16 Mar 1999 19:32:48 GMT Message-ID: <36EEB1E0.75F6C1BB@tdx.co.uk> Date: Tue, 16 Mar 1999 19:32:48 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: FTP client dies when not in passive mode? References: <67097.921612137@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: > See the ftp(1) manpage for an explanation. I know about the command line/environment variables that can be used to override this - but it's still annoying (see below)... > In future, please refer general questions related to FreeBSD to the > freebsd-questions mailing list -- freebsd-current is for issues relating > specifically to CURRENT (4.0-CURRENT at the moment). It happens on -current as well as the past versions... I seem to remember someone mentioned it before, but I can't remember the outcome (I think it was mentioned on -current)... Surely it's behaviour should be consistant? - i.e. CTRL-C should abort the current transfer/command (which it does), _unless_ your the other side of a firewall without PASSIVE then CTRL-C does nothing, and your forced to wait, and wait - or dump core... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:37: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 4A7671553C for ; Tue, 16 Mar 1999 11:36:57 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id WAA86208 for current@freebsd.org; Tue, 16 Mar 1999 22:36:38 +0300 (MSK) (envelope-from mishania) Date: Tue, 16 Mar 1999 22:36:38 +0300 From: "Mikhail A. Sokolov" To: current@freebsd.org Subject: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990316223637.A31464@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, we're experiencing repeated 4.0-C (as of today, something around 12:00 GMT, 1999-03-16) ufs_dirbad() panics, which are the following (below), which usually occur when squid is running. The box doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): /var/crash# gdb -k kernel.1 vmcore.1 IdlePTD 2682880 initial pcb at 21c7b8 panicstr: ufs_dirbad: bad dir panic messages: --- panic: ufs_dirbad: bad dir syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation code dumping to dev 20401, offset 821524 dump 256..... --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc013b4b9 in panic (fmt=0xc01fe80f "ufs_dirbad: bad dir") at ../../kern/kern_shutdown.c:448 #2 0xc01bdd1a in ufs_dirbad (ip=0xc20b0800, offset=0, how=0xc01fe7c9 "mangled entry") at ../../ufs/ufs/ufs_lookup.c:566 #3 0xc01bd5be in ufs_lookup (ap=0xce271d40) at ../../ufs/ufs/ufs_lookup.c:243 #4 0xc01c23a1 in ufs_vnoperate (ap=0xce271d40) at ../../ufs/ufs/ufs_vnops.c:2309 #5 0xc015999c in vfs_cache_lookup (ap=0xce271d9c) at vnode_if.h:55 #6 0xc01c23a1 in ufs_vnoperate (ap=0xce271d9c) at ../../ufs/ufs/ufs_vnops.c:2309 #7 0xc015bdc1 in lookup (ndp=0xce271f04) at vnode_if.h:31 #8 0xc015b894 in namei (ndp=0xce271f04) at ../../kern/vfs_lookup.c:152 #9 0xc01632a2 in vn_open (ndp=0xce271f04, fmode=5, cmode=420) at ../../kern/vfs_vnops.c:125 #10 0xc015fee9 in open (p=0xcce8b5a0, uap=0xce271f94) at ../../kern/vfs_syscalls.c:928 #11 0xc01e769f in syscall (frame={tf_es = 47, tf_ds = -1078067153, tf_edi = 4, tf_esi = 226253296, tf_ebp = -1078019504, tf_isp = -836296732, tf_ebx = 134785100, tf_edx = 228027232, tf_ecx = 0, tf_eax = 5, tf_trapno = 0, tf_err = 2, tf_eip = 672227132, tf_cs = 31, tf_eflags = 534, tf_esp = -1078019532, tf_ss = 47}) at ../../i386/i386/trap.c:1101 ---Type to continue, or q to quit--- #12 0xc01de9fc in Xint0x80_syscall () #13 0x808a844 in ?? () #14 0x808a795 in ?? () #15 0x80867f6 in ?? () #16 0x8086584 in ?? () #17 0x80585b0 in ?? () #18 0x80556a7 in ?? () #19 0x807a6c1 in ?? () #20 0x80553d3 in ?? () #21 0x804d229 in ?? () #22 0x804d163 in ?? () #23 0x804d3f5 in ?? () #24 0x8055207 in ?? () #25 0x8059824 in ?? () #26 0x805c06a in ?? () #27 0x8071f7f in ?? () #28 0x804a1b1 in ?? () (kgdb) Thanks for comments, -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:42:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 949CA153A4 for ; Tue, 16 Mar 1999 11:41:41 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id WAA86438 for current@freebsd.org; Tue, 16 Mar 1999 22:41:22 +0300 (MSK) (envelope-from mishania) Date: Tue, 16 Mar 1999 22:41:22 +0300 From: "Mikhail A. Sokolov" To: current@freebsd.org Subject: repeated ffs_blkfreepanics@demos.su, 4.0-C Message-ID: <19990316224121.A86239@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, the box is the same as in previous mail of mine which described ufs_dirbad() panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some 30 requests/second). /var/crash# gdb -k kernel.2 vmcore.2 panicstr: ffs_blkfree: freeing free frag panic messages: --- panic: ffs_blkfree: freeing free frag syncing disks... 107 52 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation code dumping to dev 20401, offset 821524 dump 256 ... --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc013b4b9 in panic (fmt=0xc01fe159 "ffs_blkfree: freeing free frag") at ../../kern/kern_shutdown.c:448 #2 0xc01b6760 in ffs_blkfree (ip=0xc2050f00, bno=4888, size=7168) at ../../ufs/ffs/ffs_alloc.c:1352 #3 0xc01b877f in ffs_truncate (vp=0xce247b40, length=0x0000000000000000, flags=0, cred=0xc1f9c780, p=0xcce8b860) at ../../ufs/ffs/ffs_inode.c:341 #4 0xc01bff2d in ufs_setattr (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:499 #5 0xc01c23a1 in ufs_vnoperate (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:2309 #6 0xc0163451 in vn_open (ndp=0xce264f04, fmode=1038, cmode=420) at vnode_if.h:275 #7 0xc015fee9 in open (p=0xcce8b860, uap=0xce264f94) at ../../kern/vfs_syscalls.c:928 #8 0xc01e769f in syscall (frame={tf_es = 47, tf_ds = -1078001617, tf_edi = 1549, tf_esi = 191218144, tf_ebp = -1078011116, tf_isp = -836349980, tf_ebx = 134788528, tf_edx = 191218128, tf_ecx = 0, tf_eax = 5, tf_trapno = 22, tf_err = 2, tf_eip = 672227132, tf_cs = 31, tf_eflags = 534, tf_esp = -1078011144, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #9 0xc01de9fc in Xint0x80_syscall () #10 0x808ae54 in ?? () #11 0x808b3c2 in ?? () ---Type to continue, or q to quit--- #12 0x8086d0b in ?? () #13 0x80563b6 in ?? () #14 0x8057e15 in ?? () #15 0x80580a5 in ?? () #16 0x805a125 in ?? () #17 0x805b6e6 in ?? () #18 0x805c10b in ?? () #19 0x8071f7f in ?? () #20 0x804a1b1 in ?? () -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 11:49:40 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 5238115028 for ; Tue, 16 Mar 1999 11:49:32 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Mzpu-000HVa-00 for current@freebsd.org; Tue, 16 Mar 1999 21:49:10 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Re: FTP client dies when not in passive mode? In-reply-to: Your message of "Tue, 16 Mar 1999 19:32:48 GMT." <36EEB1E0.75F6C1BB@tdx.co.uk> Date: Tue, 16 Mar 1999 21:49:10 +0200 Message-ID: <67305.921613750@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Mar 1999 19:32:48 GMT, Karl Pielorz wrote: > I know about the command line/environment variables that can be used to > override this - but it's still annoying (see below)... Taken off-line. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:15:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CC0514D78 for ; Tue, 16 Mar 1999 12:15:20 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id NAA27542; Tue, 16 Mar 1999 13:14:52 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903162014.NAA27542@panzer.plutotech.com> Subject: Re: repeated ufs_dirbad() panics on 4.0-c In-Reply-To: <19990316223637.A31464@demos.su> from "Mikhail A. Sokolov" at "Mar 16, 1999 10:36:38 pm" To: mishania@demos.net (Mikhail A. Sokolov) Date: Tue, 16 Mar 1999 13:14:52 -0700 (MST) Cc: 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 Mikhail A. Sokolov wrote... > Hello, > > we're experiencing repeated 4.0-C (as of today, something around 12:00 > GMT, 1999-03-16) ufs_dirbad() panics, which are the > following (below), which usually occur when squid is running. The box > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. > Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): > /var/crash# gdb -k kernel.1 vmcore.1 > IdlePTD 2682880 > initial pcb at 21c7b8 > panicstr: ufs_dirbad: bad dir > panic messages: > --- > panic: ufs_dirbad: bad dir I have no idea why you're getting a panic, but I do have a question... > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 > (da1:ahc1:0:1:0): Invalid command operation code > (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 > (da2:ahc1:0:2:0): Invalid command operation code > (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 > (da3:ahc1:0:3:0): Invalid command operation code Are you *sure* you're running -current as of today? Justin put code in to silence Illegal request error messages from the sync cache command. What revision of scsi_da.c do you have, and has it been modified? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:21:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0E66514C3C for ; Tue, 16 Mar 1999 12:21:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA23935 for current@freebsd.org; Tue, 16 Mar 1999 21:20:56 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903162020.VAA23935@freebsd.dk> Subject: How to add a new bootdevice to the new boot code ??? To: current@freebsd.org Date: Tue, 16 Mar 1999 21:20:56 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So here I am with our new boot code and a new device, how the @ž$ am I supposed to boot from that with the glory new boot blocks, forth and what have we ??? If my suspicion is right, the glory fades pretty damn fast... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:26:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id CB55B1538D for ; Tue, 16 Mar 1999 12:25:53 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id VAA17845; Tue, 16 Mar 1999 21:25:28 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id VAA03082; Tue, 16 Mar 1999 21:14:00 +0100 (CET) (envelope-from andreas) Date: Tue, 16 Mar 1999 21:14:00 +0100 From: Andreas Klemm To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP Message-ID: <19990316211359.A3068@titan.klemm.gtn.com> References: <199903151939.UAA26529@wurzelausix.cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903151939.UAA26529@wurzelausix.cs.uni-sb.de>; from Thomas Schuerger on Mon, Mar 15, 1999 at 08:39:17PM +0100 X-Operating-System: FreeBSD 3.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 15, 1999 at 08:39:17PM +0100, Thomas Schuerger wrote: > Hi! > > Will an SMP Kernel of 4.0-Current for two processors also run on > one processor? I'd like to check whether the SMP-kernel runs stable > on my Asus P2B-DS with two processors, but I'd like to be able to > switch back to the non-SMP kernel afterwards. No AFAIK two CPU's has to be there, so that the SMP kernel boots successfully. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas FreeBSD SMP is approximately 120% of Linux SMP http://www.freebsd.org/~andreas/benches/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:27: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 3E74214D52 for ; Tue, 16 Mar 1999 12:27:00 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id XAA87671; Tue, 16 Mar 1999 23:26:33 +0300 (MSK) (envelope-from mishania) Date: Tue, 16 Mar 1999 23:26:33 +0300 From: "Mikhail A. Sokolov" To: "Kenneth D. Merry" Cc: "Mikhail A. Sokolov" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990316232633.A87597@demos.su> References: <19990316223637.A31464@demos.su> <199903162014.NAA27542@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199903162014.NAA27542@panzer.plutotech.com>; from "Kenneth D. Merry" on Tue, Mar 16, 1999 at 01:14:52PM -0700 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 01:14:52PM -0700, Kenneth D. Merry wrote: # Mikhail A. Sokolov wrote... # > Hello, # > # I have no idea why you're getting a panic, but I do have a question... # # > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up # > (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 # > (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 # > (da1:ahc1:0:1:0): Invalid command operation code # > (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 # > (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 # > (da2:ahc1:0:2:0): Invalid command operation code # > (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 # > (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 # > (da3:ahc1:0:3:0): Invalid command operation code # # Are you *sure* you're running -current as of today? Justin put code in to # silence Illegal request error messages from the sync cache command. # # What revision of scsi_da.c do you have, and has it been modified? * $Id: scsi_da.c,v 1.21 1999/03/05 23:20:20 gibbs Exp $ No, it haven't been modified, yes, I know IFT shouldn't shutup about this. Strange, but it is 4.0c as of today as described, and, to add misterious details, not all panics the box experiences are followed by such messages of sync cache. # # Ken # -- # Kenneth Merry # ken@plutotech.com -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:31:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id E879E14BCE for ; Tue, 16 Mar 1999 12:31:26 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id XAA87775; Tue, 16 Mar 1999 23:30:41 +0300 (MSK) (envelope-from mishania) Date: Tue, 16 Mar 1999 23:30:41 +0300 From: "Mikhail A. Sokolov" To: "Mikhail A. Sokolov" Cc: "Kenneth D. Merry" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990316233041.A87727@demos.su> References: <19990316223637.A31464@demos.su> <199903162014.NAA27542@panzer.plutotech.com> <19990316232633.A87597@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990316232633.A87597@demos.su>; from "Mikhail A. Sokolov" on Tue, Mar 16, 1999 at 11:26:33PM +0300 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 11:26:33PM +0300, Mikhail A. Sokolov wrote: # # Are you *sure* you're running -current as of today? Justin put code in to # # silence Illegal request error messages from the sync cache command. # # # # What revision of scsi_da.c do you have, and has it been modified? # # * $Id: scsi_da.c,v 1.21 1999/03/05 23:20:20 gibbs Exp $ # # No, it haven't been modified, yes, I know IFT shouldn't shutup about this. Sigh, what a day. "Should be silent" # # Kenneth Merry -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:34:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 7384415413 for ; Tue, 16 Mar 1999 12:34:39 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from email.enst.fr (muse-2.enst.fr [137.194.2.33]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id VAA27759; Tue, 16 Mar 1999 21:34:03 +0100 (MET) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by email.enst.fr (8.9.3/8.9.3) with ESMTP id VAA01114; Tue, 16 Mar 1999 21:34:02 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id 04373D21A; Tue, 16 Mar 1999 21:33:56 +0100 (CET) Message-ID: <19990316213355.A4561@enst.fr> Date: Tue, 16 Mar 1999 21:33:55 +0100 From: Pierre Beyssac To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903161911.LAA11778@apollo.backplane.com>; from Matthew Dillon on Tue, Mar 16, 1999 at 11:11:44AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 11:11:44AM -0800, Matthew Dillon wrote: > (cnp->cn_flags & NOCROSSMOUNT) == 0) { > if (vfs_busy(mp, 0, 0, p)) > continue; ... > You shouldn't be crossing a mount point. Are you by chance doing a > recursive copy onto itself? > e.g. cp -rp src dest where dest is mounted under src somewhere ? No. At first it was from a NFS-mounted volume to another NFS-mounted volume. I then found that it panic'ed the same when I copied from a local FFS volume to the same NFS volume. The NFS volumes are automounted by amd under /a. That may well have something to do with the panic: that's a recent change in my configuration; I previously used NFS mounts in /etc/fstab which didn't cause me any trouble. > Of course, it is still a serious kernel bug. I would like to try > to reproduce it in order to track it down. How are things mounted on > your system ( df ) and what are the *exact* arguments you are using with > cp? Here's the df (I removed some of the amd dummy mount points). $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 49583 34595 11022 76% / /dev/wd1s1e 5975845 3556146 1941632 65% /home /dev/wd0s1f 148823 1290 135628 1% /tmp /dev/wd0s1g 5380597 1615221 3334929 33% /usr /dev/wd0s1e 396895 38127 327017 10% /var procfs 4 4 0 100% /proc [ ten pid156@bofh:/xyz lines removed ] pid156@bofh:/cal 0 0 0 100% /cal huuh:/home/huuh 1217519 1064153 141191 88% /a/huuh/home/huuh The failing cp is: $ cp -rp /home/beyssac/src/sendmail-8.9.3/cf/ /home/beyssac/nfs/junk/ In the above, "/home/beyssac/nfs" is a symbolic link to /cal/huuh/cal/beyssac which is automounted by amd (last line in the above df). -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:37:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 87D3015485 for ; Tue, 16 Mar 1999 12:37:06 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id NAA27623; Tue, 16 Mar 1999 13:36:41 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903162036.NAA27623@panzer.plutotech.com> Subject: Re: repeated ufs_dirbad() panics on 4.0-c In-Reply-To: <19990316232633.A87597@demos.su> from "Mikhail A. Sokolov" at "Mar 16, 1999 11:26:33 pm" To: mishania@demos.net (Mikhail A. Sokolov) Date: Tue, 16 Mar 1999 13:36:40 -0700 (MST) Cc: 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 Mikhail A. Sokolov wrote... > On Tue, Mar 16, 1999 at 01:14:52PM -0700, Kenneth D. Merry wrote: > # Mikhail A. Sokolov wrote... > # > Hello, > # > > # I have no idea why you're getting a panic, but I do have a question... > # > # > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up > # > (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > # > (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 > # > (da1:ahc1:0:1:0): Invalid command operation code > # > (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > # > (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 > # > (da2:ahc1:0:2:0): Invalid command operation code > # > (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > # > (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 > # > (da3:ahc1:0:3:0): Invalid command operation code > # > # Are you *sure* you're running -current as of today? Justin put code in to > # silence Illegal request error messages from the sync cache command. > # > # What revision of scsi_da.c do you have, and has it been modified? > > * $Id: scsi_da.c,v 1.21 1999/03/05 23:20:20 gibbs Exp $ > > No, it haven't been modified, yes, I know IFT shouldn't shutup about this. > Strange, but it is 4.0c as of today as described, and, to add misterious > details, not all panics the box experiences are followed by such messages > of sync cache. Well, that's what I wanted to know. You're using the latest version of scsi_da.c, so I suppose I'll leave it up to Justin to figure out why you're seeing those error messages. (since he wrote the code) Don't worry, those messages are generally harmless. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 12:53:52 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 89A3014D9C for ; Tue, 16 Mar 1999 12:52:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA12300; Tue, 16 Mar 1999 12:52:32 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 12:52:32 -0800 (PST) From: Matthew Dillon Message-Id: <199903162052.MAA12300@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> <19990316213355.A4561@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Tue, Mar 16, 1999 at 11:11:44AM -0800, Matthew Dillon wrote: :> (cnp->cn_flags & NOCROSSMOUNT) == 0) { :> if (vfs_busy(mp, 0, 0, p)) :> continue; :... :> You shouldn't be crossing a mount point. Are you by chance doing a :> recursive copy onto itself? :> e.g. cp -rp src dest where dest is mounted under src somewhere ? : :No. At first it was from a NFS-mounted volume to another NFS-mounted :volume. I then found that it panic'ed the same when I copied from :a local FFS volume to the same NFS volume. : :The NFS volumes are automounted by amd under /a. That may well have :something to do with the panic: that's a recent change in my :configuration; I previously used NFS mounts in /etc/fstab which :didn't cause me any trouble. : :> Of course, it is still a serious kernel bug. I would like to try :> to reproduce it in order to track it down. How are things mounted on :> your system ( df ) and what are the *exact* arguments you are using with :> cp? : :Here's the df (I removed some of the amd dummy mount points). : :$ df :Filesystem 1K-blocks Used Avail Capacity Mounted on :/dev/wd0s1a 49583 34595 11022 76% / :/dev/wd1s1e 5975845 3556146 1941632 65% /home :/dev/wd0s1f 148823 1290 135628 1% /tmp :/dev/wd0s1g 5380597 1615221 3334929 33% /usr :/dev/wd0s1e 396895 38127 327017 10% /var :procfs 4 4 0 100% /proc :[ ten pid156@bofh:/xyz lines removed ] :pid156@bofh:/cal 0 0 0 100% /cal :huuh:/home/huuh 1217519 1064153 141191 88% /a/huuh/home/huuh : :The failing cp is: : :$ cp -rp /home/beyssac/src/sendmail-8.9.3/cf/ /home/beyssac/nfs/junk/ : :In the above, "/home/beyssac/nfs" is a symbolic link to :/cal/huuh/cal/beyssac which is automounted by amd (last line in :the above df). :-- :Pierre Beyssac pb@enst.fr Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't fry? If so, then we have a bug in AMD somewhere. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 13:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id F3D8515079 for ; Tue, 16 Mar 1999 13:11:32 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from email.enst.fr (muse-2.enst.fr [137.194.2.33]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id WAA29319; Tue, 16 Mar 1999 22:11:01 +0100 (MET) Received: from bofh.enst.fr (bofh.enst.fr [137.194.32.191]) by email.enst.fr (8.9.3/8.9.3) with ESMTP id WAA01134; Tue, 16 Mar 1999 22:11:00 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id 8DB23D21A; Tue, 16 Mar 1999 22:10:57 +0100 (CET) Message-ID: <19990316221057.A382@enst.fr> Date: Tue, 16 Mar 1999 22:10:57 +0100 From: Pierre Beyssac To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> <19990316213355.A4561@enst.fr> <199903162052.MAA12300@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903162052.MAA12300@apollo.backplane.com>; from Matthew Dillon on Tue, Mar 16, 1999 at 12:52:32PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: > Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't > fry? If so, then we have a bug in AMD somewhere. I tried the cp several times again on a regular NFS mount, to make sure, and no, it doesn't seem to panic. So yes, that seems to be AMD-related. Can't it be in the vfs layer though? -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 13:41:50 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 5A6FB14E75 for ; Tue, 16 Mar 1999 13:41:37 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-135.skylink.it [194.177.113.135]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA26909; Tue, 16 Mar 1999 22:40:00 +0100 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id WAA00727; Tue, 16 Mar 1999 22:37:11 +0100 (CET) Date: Tue, 16 Mar 1999 22:37:11 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Matthew Dillon Cc: FreeBSD current Mailing list Subject: Re: panic occurred: vm_fault In-Reply-To: <199903161915.LAA11827@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 > Is the panic reproduceable? What is the CCD configuration? not ccd, cd. old atapi stuff if I remember correctly. Machine has not crashed since, sorry, switched on dumpdev however, so I can send you the core file (and kernel and whatever else) if it happens agains if you like. Nick > > -Matt > Matthew Dillon > > > :In case someone who is interested in the following panic: > : > :Occurred under a lightly loaded system that was not doing anything apart > :from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512). > :Kernel current as of yesterday. > :No core file is available unfortunately. > : > : > :panic: vm_fault: fault on nofault entry, addr: c35c6000 > :(blabla about debugger) > :> show registers > :cs 0x8 > :ds 0x10 > :es 0x10 > :ss 0x10 > :eax 0x12 > :ecx 0xc00b8f00 > :edx 0xc024d1a4 db_lengths+0x11c > :ebx 0xc0248255 > :__set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9 > :esp 0xc6f23ca8 > :ebp 0xc6f23cb0 > :esi 0x100 > :edi 0xc35c6000 > :eip 0xc020f993 Debugger+0x37 > :efl 0x256 > :> trace > :panic > :vm_fault > :trap_pfault > :trap > :calltrap() > :--- trap > :slow_copyout > :spec_read > :ufsspec_read > :ufs_vnoperatespec > :vn_read > :read > :syscall > :Xint0x80syscall > : > : > :-- > :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 > > -- 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 Tue Mar 16 14:19:12 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 DA22D14EBB for ; Tue, 16 Mar 1999 14:19:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA09995; Tue, 16 Mar 1999 14:17:09 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdCx9990; Tue Mar 16 22:17:07 1999 Message-ID: <36EED85B.59E2B600@whistle.com> Date: Tue, 16 Mar 1999 14:16:59 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: "Mikhail A. Sokolov" Cc: current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c References: <19990316223637.A31464@demos.su> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail A. Sokolov wrote: > > Hello, > > we're experiencing repeated 4.0-C (as of today, something around 12:00 > GMT, 1999-03-16) ufs_dirbad() panics, which are the > following (below), which usually occur when squid is running. The box > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. soft updates? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 14:21:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 2AD57151B9 for ; Tue, 16 Mar 1999 14:21:43 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id BAA91030; Wed, 17 Mar 1999 01:21:20 +0300 (MSK) (envelope-from mishania) Date: Wed, 17 Mar 1999 01:21:19 +0300 From: "Mikhail A. Sokolov" To: Julian Elischer Cc: "Mikhail A. Sokolov" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990317012119.A91006@demos.su> References: <19990316223637.A31464@demos.su> <36EED85B.59E2B600@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <36EED85B.59E2B600@whistle.com>; from Julian Elischer on Tue, Mar 16, 1999 at 02:16:59PM -0800 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nope, gone one month ago, FS's rebuilt since then On Tue, Mar 16, 1999 at 02:16:59PM -0800, Julian Elischer wrote: # Mikhail A. Sokolov wrote: # > # > Hello, # > # > we're experiencing repeated 4.0-C (as of today, something around 12:00 # > GMT, 1999-03-16) ufs_dirbad() panics, which are the # > following (below), which usually occur when squid is running. The box # > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. # # # soft updates? -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 14:24:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from telos.odyssey.cs.cmu.edu (TELOS.ODYSSEY.CS.CMU.EDU [128.2.185.175]) by hub.freebsd.org (Postfix) with ESMTP id 60037152CB for ; Tue, 16 Mar 1999 14:24:28 -0800 (PST) (envelope-from jaharkes@telos.odyssey.cs.cmu.edu) Received: (from jaharkes@localhost) by telos.odyssey.cs.cmu.edu (8.8.7/8.8.7) id RAA00699 for current@freebsd.org; Tue, 16 Mar 1999 17:24:09 -0500 Date: Tue, 16 Mar 1999 17:24:09 -0500 From: jaharkes@cs.cmu.edu Message-Id: <199903162224.RAA00699@telos.odyssey.cs.cmu.edu> To: current@freebsd.org Subject: [Ann] Coda FS version 5.2.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Coda Distributed File System, version 5.2 Coda is a distributed file system like NFS and AFS. It is freely available under the GPL. It functions somewhat like AFS in being a "stateful" file system. Coda and AFS cache files on your local machine to improve performance. But Coda goes a step further than AFS by letting you access the cached files when there is no available network, viz. disconnected laptops and network outages. Coda also has read write replication servers. The Coda file server is outside the kernel and on the client theCoda cache manager Venus is again outside of the kernel, but on clients one needs a kernel module. To get more information on Coda, check out our WWW site: http://www.coda.cs.cmu.edu If you are using Coda or have had trouble using it, please send us some feedback at: http://www.coda.cs.cmu.edu/feedback.html There is a wealth of documents, papers, and theses on our WWW site. There is also a good introduction to the Coda File System in http://www.coda.cs.cmu.edu/ljpaper/lj.html and a Coda-HOWTO: http://www.coda.cs.cmu.edu/doc/html/coda-howto.html Coda was originally developed as an academic prototype/testbed. It is being polished and rewritten where necessary. Coda is a work in progress and does have bugs. It is, though, very usable. Our interest is in making Coda available to as many people as possible and to have Coda evolve and flourish. The bulk of the Coda file system code supports the Coda client program, the Coda server program and the utilities needed by both. All these programs are unix programs and can run equally well on any Unix platform. Our main development thrust is improving these programs. There is a small part of Coda that deals with the kernel to file system interface. This code is OS specific (but should not be platform specific). Coda is currently available for several OS's and platforms: linux 2.0: i386 & sparc linux 2.2: i386 & sparc Freebsd 2.2.x: i386 Freebsd current: i386 NetBSD 1.3x: i386 & sparc NetBSD current: i386 There are also alpha releases for: Windows 95 & 98 -- Coda client Windows NT -- Coda server The relevant sources, binaries, and docs can be found in ftp://ftp.coda.cs.cmu.edu/pub/coda/ There are several mailing lists @coda.cs.cmu.edu that discuss coda: coda-announce and codalist. We appreciate comments, feedback, bug reports, bug fixes, enhancements, etc. Changes: summary of some of the differences since 5.0.x * Updated documentation. * New protection database (simplyfies user administration). * Removed obsolete venus-vice rpc2 calls. * Server support for trickle fetch and fetch continuations. * Improved support on the Windows platforms. * Avoid deadlocks in the rpc2 binding sequence. * Added support for FreeBSD 4.0 (Robert Watson) * Testing for -fno-exceptions in configure script. * Switching fetches between volume replicas. * Removed the need for -child flag on Win95. * Nice GUI frontend on Windows for starting/stopping venus. (Michael Callahan and Marc Schnieder) * Fixed @sys/@cpu expansions in venus, and allow setuid bits. * Added @sys/@cpu commands to cfs to show the `current' expansion. * Normal symlinks were sometimes mistaken for inconsistent objects. * Fixed a linux-coda kernel problem in lookup * Fixed several bugs in the volume package Please let us know about problems, since we will try to fix them right away. Compatibility with previous versions: - network protocol: can coexists with 4.6.7 and later - disk format client: clients need to be reinitialized - disk format for server: backward compatible Peter Braam Bob Baron Jan Harkes Marc Schnieder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 15:27:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-6-dbn.dial-up.net [196.34.155.70]) by hub.freebsd.org (Postfix) with ESMTP id 93C8B15220 for ; Tue, 16 Mar 1999 15:26:45 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA07920; Wed, 17 Mar 1999 01:22:12 +0200 (SAT) From: Robert Nordier Message-Id: <199903162322.BAA07920@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903162020.VAA23935@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 16, 99 09:20:56 pm" To: sos@freebsd.dk (Søren Schmidt) Date: Wed, 17 Mar 1999 01:22:10 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt wrote: > So here I am with our new boot code and a new device, how the > @ž$ am I supposed to boot from that with the glory new > boot blocks, forth and what have we ??? > > If my suspicion is right, the glory fades pretty damn fast... This is a bit on the incoherent side, Soren. :-) If the problem is the bootblocks, why not send a message to Robert Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And say, "This is what I want to do, what are we going to do about it?" or something similar? -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 15:46: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id A95E714C8E for ; Tue, 16 Mar 1999 15:46:02 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA28674; Wed, 17 Mar 1999 10:15:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990316211359.A3068@titan.klemm.gtn.com> Date: Wed, 17 Mar 1999 10:15:30 +1030 (CST) From: "Daniel O'Connor" To: Andreas Klemm Subject: Re: SMP Cc: freebsd-current@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG, Thomas Schuerger Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Mar-99 Andreas Klemm wrote: > No AFAIK two CPU's has to be there, so that the SMP kernel boots > successfully. Yes this is true. You have to make a UP kernel (ie remove the SMP lines).. I have 2 kernels on my SMP box, they are the same except one has SMP in it :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 16:14:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 5E33114C37 for ; Tue, 16 Mar 1999 16:14:03 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Wed, 17 Mar 1999 00:11:59 -0000 Message-ID: From: paul@originative.co.uk To: current@freebsd.org Subject: panic: zone: entry not free Date: Wed, 17 Mar 1999 00:11:53 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to be able to repeat this panic, every time I make a certain change to a file and save it out this happens. It's a NFS mounted file from my i386 box to my alpha, both running pretty much current. It's the alpha that panics. Stopped at Debugger..ng+0x24: ldq ra,0(sp) <0xfffffe00059e7bc0> db> t Debugger..ng() at Debugger..ng+0x24 panic..ng() at panic..ng+0xf0 zerror..ng() at zerror..ng+0x6c namei..ng() at namei..ng+0x140 stat..ng() at stat..ng+0x44 syscall..ng() at syscall..ng+0x1dc XentSys() at XentSys+0x50 (null)() at 0x120009e38 No debugger on the alpha at the moment (but I'm working on that) and I probably won't be able to do anything for another 24 hours if you need more info. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 16:56:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 93B0A14CD2 for ; Tue, 16 Mar 1999 16:56:17 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id BAA17367; Wed, 17 Mar 1999 01:55:35 +0100 (CET) (envelope-from des) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: latest -current doesn't execute BSDI-binary bladeenc References: <199903160038.TAA15366@kot.ne.mediaone.net> From: Dag-Erling Smorgrav Date: 17 Mar 1999 01:55:35 +0100 In-Reply-To: Mikhail Teterin's message of "Mon, 15 Mar 1999 19:38:30 -0500 (EST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: > Does not seem a better solution to me at all. The problem is not > that bladeenc does not run, the problem is that a BSDI executable > does not run. Which breaks a promise from > http://www.freebsd.org/features.html The bug is on the web site, not in the kernel. David Greenman committed a patch to better support large memory configurations. Unfortunately, it seems this was not possible to achieve without breaking BSDI compatibility. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 17: 3:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id BD83E1512A; Tue, 16 Mar 1999 17:03:07 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id UAA53718; Tue, 16 Mar 1999 20:02:49 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: current@freebsd.org Cc: yokota@freebsd.org From: "Gary Palmer" Subject: breakage on alpha Date: Tue, 16 Mar 1999 20:02:49 -0500 Message-ID: <53714.921632569@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.sbin/kbdcontrol cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c gzip -cn /usr/src/usr.sbin/kbdcontrol/kbdcontrol.1 > kbdcontrol.1.gz lex -t /usr/src/usr.sbin/kbdcontrol/lex.l > lex.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c lex.c /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:418: warning: `struct key_t' declared inside parameter list /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:418: warning: its scope is only this definition or declaration, /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:418: warning: which is probably not what you want. /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c: In function `print_key_definition_line': /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:431: dereferencing pointer to incomplete type /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:432: dereferencing pointer to incomplete type /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:434: dereferencing pointer to incomplete type /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:438: dereferencing pointer to incomplete type /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c: In function `print_keymap': /usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:722: warning: passing arg 3 of `print_key_definition_line' from incompatible pointer type *** Error code 1 I can't find a key_t anywhere in the source tree (not relative to the console anyhow)... Is that meant to be a keyent_t? I believe so... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 17: 7: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9891D1519C for ; Tue, 16 Mar 1999 17:07:02 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA03003; Wed, 17 Mar 1999 11:36:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 17 Mar 1999 11:36:32 +1030 (CST) From: "Daniel O'Connor" To: Dag-Erling Smorgrav Subject: Re: latest -current doesn't execute BSDI-binary bladeenc Cc: current@FreeBSD.ORG, Mikhail Teterin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-99 Dag-Erling Smorgrav wrote: > > that bladeenc does not run, the problem is that a BSDI executable > > does not run. Which breaks a promise from > The bug is on the web site, not in the kernel. David Greenman > committed a patch to better support large memory configurations. > Unfortunately, it seems this was not possible to achieve without > breaking BSDI compatibility. Would it be feasable to have an option to switch between the two? I can see people wanting BSDI compatibility and not having large quantities of RAM being fairly common. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 18: 7:41 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 F264C14FE6 for ; Tue, 16 Mar 1999 18:05:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA21093; Tue, 16 Mar 1999 18:05:10 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 18:05:10 -0800 (PST) From: Matthew Dillon Message-Id: <199903170205.SAA21093@apollo.backplane.com> To: paul@originative.co.uk Cc: current@FreeBSD.ORG Subject: Re: panic: zone: entry not free References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's your memory configuration and what's your kernel configuration? df dmesg cat /usr/src/sys/i386/conf/YOURKERNELCONFIG In general, the more information you include in the email, the easier it is on the list. -Matt Matthew Dillon : :I seem to be able to repeat this panic, every time I make a certain change :to a file and save it out this happens. It's a NFS mounted file from my i386 :box to my alpha, both running pretty much current. It's the alpha that :panics. : :Stopped at Debugger..ng+0x24: ldq ra,0(sp) :<0xfffffe00059e7bc0> :db> t :Debugger..ng() at Debugger..ng+0x24 :panic..ng() at panic..ng+0xf0 :zerror..ng() at zerror..ng+0x6c :namei..ng() at namei..ng+0x140 :stat..ng() at stat..ng+0x44 :syscall..ng() at syscall..ng+0x1dc :XentSys() at XentSys+0x50 :(null)() at 0x120009e38 :... :Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 18:21:50 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 67C2B14E7A for ; Tue, 16 Mar 1999 18:21:35 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA18462; Wed, 17 Mar 1999 12:51:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA69335; Wed, 17 Mar 1999 12:51:12 +1030 (CST) Message-ID: <19990317125112.T429@lemis.com> Date: Wed, 17 Mar 1999 12:51:12 +1030 From: Greg Lehey To: "Mikhail A. Sokolov" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c References: <19990316223637.A31464@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990316223637.A31464@demos.su>; from Mikhail A. Sokolov on Tue, Mar 16, 1999 at 10:36:38PM +0300 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 March 1999 at 22:36:38 +0300, Mikhail A. Sokolov wrote: > Hello, > > we're experiencing repeated 4.0-C (as of today, something around 12:00 > GMT, 1999-03-16) ufs_dirbad() panics, which are the > following (below), which usually occur when squid is running. The box > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. > Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): > /var/crash# gdb -k kernel.1 vmcore.1 > IdlePTD 2682880 > initial pcb at 21c7b8 > panicstr: ufs_dirbad: bad dir > panic messages: > --- > panic: ufs_dirbad: bad dir Have you looked at the directory? Theoretically this could be a really mangled directory structure. 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 Tue Mar 16 18:25: 5 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 4786A14F82 for ; Tue, 16 Mar 1999 18:25:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA18474; Wed, 17 Mar 1999 12:54:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA69344; Wed, 17 Mar 1999 12:54:40 +1030 (CST) Message-ID: <19990317125440.U429@lemis.com> Date: Wed, 17 Mar 1999 12:54:40 +1030 From: Greg Lehey To: "Mikhail A. Sokolov" , current@FreeBSD.org Subject: Re: repeated ffs_blkfreepanics@demos.su, 4.0-C References: <19990316224121.A86239@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990316224121.A86239@demos.su>; from Mikhail A. Sokolov on Tue, Mar 16, 1999 at 10:41:22PM +0300 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 March 1999 at 22:41:22 +0300, Mikhail A. Sokolov wrote: > Hello, > the box is the same as in previous mail of mine which described ufs_dirbad() > panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some > 30 requests/second). These two crashes both tend to suggest a file system structure problem which fsck doesn't detect. What's the vp in the ffs_truncate frame? How does it compare to the *vpp in the ufs_lookup frame of the previous dump? 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 Tue Mar 16 18:29:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 315FA152C2 for ; Tue, 16 Mar 1999 18:29:30 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id DAA19890; Wed, 17 Mar 1999 03:28:25 +0100 (CET) (envelope-from des) To: "Daniel O'Connor" Cc: Dag-Erling Smorgrav , current@FreeBSD.ORG, Mikhail Teterin Subject: Re: latest -current doesn't execute BSDI-binary bladeenc References: From: Dag-Erling Smorgrav Date: 17 Mar 1999 03:28:24 +0100 In-Reply-To: "Daniel O'Connor"'s message of "Wed, 17 Mar 1999 11:36:32 +1030 (CST)" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel O'Connor" writes: > On 17-Mar-99 Dag-Erling Smorgrav wrote: > > The bug is on the web site, not in the kernel. David Greenman > > committed a patch to better support large memory configurations. > > Unfortunately, it seems this was not possible to achieve without > > breaking BSDI compatibility. > Would it be feasable to have an option to switch between the two? Probably. I was just about to investigate this possibility. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 18:38:32 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 562B015351; Tue, 16 Mar 1999 18:38:28 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:64ChR3HyMUcBmZonAVPrXbOX/Mu4aUBM@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id LAA22107; Wed, 17 Mar 1999 11:38:08 +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 LAA28653; Wed, 17 Mar 1999 11:41:25 +0900 (JST) Message-Id: <199903170241.LAA28653@zodiac.mech.utsunomiya-u.ac.jp> To: "Gary Palmer" Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: breakage on alpha In-reply-to: Your message of "Tue, 16 Mar 1999 20:02:49 EST." <53714.921632569@gjp.erols.com> References: <53714.921632569@gjp.erols.com> Date: Wed, 17 Mar 1999 11:41:25 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >===> usr.sbin/kbdcontrol >cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/kbdcontr >ol/kbdcontrol.c >gzip -cn /usr/src/usr.sbin/kbdcontrol/kbdcontrol.1 > kbdcontrol.1.gz >lex -t /usr/src/usr.sbin/kbdcontrol/lex.l > lex.c >cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c lex.c >/usr/src/usr.sbin/kbdcontrol/kbdcontrol.c:418: warning: `struct key_t' declare >d inside parameter list [...] It was in machine/console.h and renamed to keyent_t. I don't remember when this `#ifdef __i386__' bit came in... Kazu Index: kbdcontrol.c =================================================================== RCS file: /src/CVS/src/usr.sbin/kbdcontrol/kbdcontrol.c,v retrieving revision 1.23 diff -u -r1.23 kbdcontrol.c --- kbdcontrol.c 1999/03/10 10:36:51 1.23 +++ kbdcontrol.c 1999/03/17 02:39:15 @@ -410,13 +410,8 @@ } -#ifdef __i386__ void print_key_definition_line(FILE *fp, int scancode, struct keyent_t *key) -#else -void -print_key_definition_line(FILE *fp, int scancode, struct key_t *key) -#endif { int i; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 18:54:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 1623214D6A for ; Tue, 16 Mar 1999 18:54:18 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id VAA55122 for ; Tue, 16 Mar 1999 21:53:59 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: current@freebsd.org From: "Gary Palmer" Subject: usb/ugen problem? Date: Tue, 16 Mar 1999 21:53:59 -0500 Message-ID: <55118.921639239@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Output from dmesg: usbd_match usb0: usbd_attach usbd_new_device bus=0xc09b9000 depth=0 lowspeed=0 usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, ls=0 usbd_new_device: new dev (addr 1), dev=0xc09b7b00, parent=0xc09b5040 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 usbd_set_config_index: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 uhub0: 2 ports with 2 removable, self powered usbd_init_port: adding hub port=1 status=0x0101 change=0x0001 usbd_init_port: adding hub port=2 status=0x0100 change=0x0000 uhub_explore: status change hub=1 port=1 usbd_new_device bus=0xc09b9000 depth=1 lowspeed=0 usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=0 usbd_new_device: new dev (addr 2), dev=0xc09b7800, parent=0xc09b4d00 usbd_probe_and_attach: no device specific driver found usbd_set_config_index: (addr 2) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 usbd_probe_and_attach: no interface drivers found ugen0 ugen0: Microsoft Microsoft Digital Sound System 80, rev 1.00/1.00, addr 2 If I cat /dev/ugen0, I get ugenread: no edesc splatted across the console (if I enable DIAGNOSTIC), otherwise I get a panic. Personally, I'd prefer that the tests in ugen.c that are currently behind DIAGNOSTIC (i.e. checking for null pointers basically) are made the default. How does a device end up with no edesc? Do you have to set the config first? Is there any docs on our USB stuff apart from the src code? Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 18:58:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 2D3CA14FCE for ; Tue, 16 Mar 1999 18:58:34 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id VAA20641; Tue, 16 Mar 1999 21:56:12 -0500 (EST) From: Mikhail Teterin Message-Id: <199903170256.VAA20641@kot.ne.mediaone.net> Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-Reply-To: from Dag-Erling Smorgrav at "Mar 17, 1999 03:28:24 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Tue, 16 Mar 1999 21:56:12 -0500 (EST) Cc: doconnor@gsoft.com.au, current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" > The bug is on the web site, not in the kernel. I'd consider the web-site a "spec" and the kernel -- "implementation". By this logic, the kernel needs fixing... => > David Greenman committed a patch to better support large memory => > configurations. Unfortunately, it seems this was not possible to => > achieve without breaking BSDI compatibility. => => Would it be feasable to have an option to switch between the two? = =Probably. I was just about to investigate this possibility. It should definitly be on automaticly if the memory configuration is not large, if you ask me... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 19: 0:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 71AE815053 for ; Tue, 16 Mar 1999 19:00:29 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA01200; Tue, 16 Mar 1999 18:58:33 -0800 (PST) Message-Id: <199903170258.SAA01200@implode.root.com> To: Dag-Erling Smorgrav Cc: "Daniel O'Connor" , current@FreeBSD.ORG, Mikhail Teterin Subject: Re: latest -current doesn't execute BSDI-binary bladeenc In-reply-to: Your message of "17 Mar 1999 03:28:24 +0100." From: David Greenman Reply-To: dg@root.com Date: Tue, 16 Mar 1999 18:58:33 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"Daniel O'Connor" writes: >> On 17-Mar-99 Dag-Erling Smorgrav wrote: >> > The bug is on the web site, not in the kernel. David Greenman >> > committed a patch to better support large memory configurations. >> > Unfortunately, it seems this was not possible to achieve without >> > breaking BSDI compatibility. >> Would it be feasable to have an option to switch between the two? > >Probably. I was just about to investigate this possibility. If the remaining userland issues are dealt with, then perhaps. It is currently necessary to rebuild certain utilities after changing this, however, so making it a simple kernel compile time option isn't sufficient. A much better solution would be for someone to spend the time to implement the needed VM frobbing of modifying, at BSDI binary exec-time, the ps_strings address constant in the binary's crt0 that is causing the problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 19:12:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9FCE014E7A for ; Tue, 16 Mar 1999 19:12:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA11788; Wed, 17 Mar 1999 13:41:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903170256.VAA20641@kot.ne.mediaone.net> Date: Wed, 17 Mar 1999 13:41:52 +1030 (CST) From: "Daniel O'Connor" To: Mikhail Teterin Subject: Re: latest -current doesn't execute BSDI-binary bladeenc Cc: current@FreeBSD.ORG, (Dag-Erling Smorgrav) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-99 Mikhail Teterin wrote: > => > The bug is on the web site, not in the kernel. > I'd consider the web-site a "spec" and the kernel -- "implementation". > By this logic, the kernel needs fixing... I think its a little too rapidly evolving for that, especially -current. > =Probably. I was just about to investigate this possibility. > It should definitly be on automaticly if the memory configuration > is not large, if you ask me... That would be nice, but it has to be an option before you can make it the default behaviour. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 19:14:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5E78715217 for ; Tue, 16 Mar 1999 19:12:55 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id EAA21036; Wed, 17 Mar 1999 04:12:19 +0100 (CET) (envelope-from des) To: dg@root.com Cc: Dag-Erling Smorgrav , "Daniel O'Connor" , current@FreeBSD.ORG, Mikhail Teterin Subject: Re: latest -current doesn't execute BSDI-binary bladeenc References: <199903170258.SAA01200@implode.root.com> From: Dag-Erling Smorgrav Date: 17 Mar 1999 04:12:18 +0100 In-Reply-To: David Greenman's message of "Tue, 16 Mar 1999 18:58:33 -0800" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > If the remaining userland issues are dealt with, then perhaps. It is > currently necessary to rebuild certain utilities after changing this, > however, so making it a simple kernel compile time option isn't sufficient. Are these crash-and-burn-class problems, or is it just a matter of ps and top not working? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 19:43:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 51F6D151E5 for ; Tue, 16 Mar 1999 19:42:45 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id WAA55821; Tue, 16 Mar 1999 22:42:20 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: Kazutaka YOKOTA Cc: current@freebsd.org From: "Gary Palmer" Subject: Re: breakage on alpha In-reply-to: Your message of "Wed, 17 Mar 1999 11:41:25 +0900." <199903170241.LAA28653@zodiac.mech.utsunomiya-u.ac.jp> Date: Tue, 16 Mar 1999 22:42:20 -0500 Message-ID: <55817.921642140@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote in message ID <199903170241.LAA28653@zodiac.mech.utsunomiya-u.ac.jp>: > It was in machine/console.h and renamed to keyent_t. > > I don't remember when this `#ifdef __i386__' bit came in... revision 1.23 date: 1999/03/10 10:36:51; author: yokota; state: Exp; lines: +12 -33 Keyboard driver update in preparation for the USB keyboard driver. Seems to be when it was introduced. > Index: kbdcontrol.c > =================================================================== > RCS file: /src/CVS/src/usr.sbin/kbdcontrol/kbdcontrol.c,v > retrieving revision 1.23 > diff -u -r1.23 kbdcontrol.c > --- kbdcontrol.c 1999/03/10 10:36:51 1.23 > +++ kbdcontrol.c 1999/03/17 02:39:15 > @@ -410,13 +410,8 @@ > } > > > -#ifdef __i386__ > void > print_key_definition_line(FILE *fp, int scancode, struct keyent_t *key) > -#else > -void > -print_key_definition_line(FILE *fp, int scancode, struct key_t *key) -#endif > { > int i; Will you commit this? Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 20: 8:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 48E93152A4 for ; Tue, 16 Mar 1999 20:08:26 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id XAA14845 for current@freebsd.org; Tue, 16 Mar 1999 23:08:02 -0500 (EST) (envelope-from luoqi) Date: Tue, 16 Mar 1999 23:08:02 -0500 (EST) From: Luoqi Chen Message-Id: <199903170408.XAA14845@lor.watermarkgroup.com> To: current@freebsd.org Subject: VM86 assembly code problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There're a couple places in swtch.s with code like, #ifdef VM86 btrl %esi, _private_tss je 3f ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 20:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 8BA7B15257 for ; Tue, 16 Mar 1999 20:14:09 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id XAA14900 for current@freebsd.org; Tue, 16 Mar 1999 23:13:46 -0500 (EST) (envelope-from luoqi) Date: Tue, 16 Mar 1999 23:13:46 -0500 (EST) From: Luoqi Chen Message-Id: <199903170413.XAA14900@lor.watermarkgroup.com> To: current@freebsd.org Subject: VM86 assembly code problem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There're a couple of places in swtch.s where code looks like this, #ifdef VM86 btrl %esi, _private_tss je 3f ... 3: #endif The conditional jump statement doesn't seem right, according to manual, btrl instruction modifies CF flag but not Z, so the jump should be jae/jb instead of je/jne. Could anyone confirm this? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 21:29: 9 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 86FEF14F24 for ; Tue, 16 Mar 1999 21:29:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA24119; Tue, 16 Mar 1999 21:28:47 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 21:28:47 -0800 (PST) From: Matthew Dillon Message-Id: <199903170528.VAA24119@apollo.backplane.com> To: Luoqi Chen Cc: current@FreeBSD.ORG Subject: Re: VM86 assembly code problem References: <199903170413.XAA14900@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :There're a couple of places in swtch.s where code looks like this, : :#ifdef VM86 : btrl %esi, _private_tss : je 3f : ... :3: :#endif : :The conditional jump statement doesn't seem right, according to manual, :btrl instruction modifies CF flag but not Z, so the jump should be jae/jb :instead of je/jne. Could anyone confirm this? : :-lq btrl only effects the Carry. The VM86 code looks wrong to me, though there is an outside chance that it is doing a conditional jump based on something that occured prior to the btrl. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 16 22:43:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id BA7E315244 for ; Tue, 16 Mar 1999 22:43:24 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 1455 invoked from network); 17 Mar 1999 06:43:04 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 17 Mar 1999 06:43:04 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id BAA03109; Wed, 17 Mar 1999 01:42:58 -0500 (EST) Message-Id: <199903170642.BAA03109@y.dyson.net> Subject: Re: VM86 assembly code problem In-Reply-To: <199903170528.VAA24119@apollo.backplane.com> from Matthew Dillon at "Mar 16, 99 09:28:47 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 17 Mar 1999 01:42:58 -0500 (EST) Cc: luoqi@watermarkgroup.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > :There're a couple of places in swtch.s where code looks like this, > : > :#ifdef VM86 > : btrl %esi, _private_tss > : je 3f > : ... > :3: > :#endif > : > :The conditional jump statement doesn't seem right, according to manual, > :btrl instruction modifies CF flag but not Z, so the jump should be jae/jb > :instead of je/jne. Could anyone confirm this? > : > :-lq > > btrl only effects the Carry. The VM86 code looks wrong to me, though > there is an outside chance that it is doing a conditional jump based > on something that occured prior to the btrl. > Even though you are correct in practice, the Intel Architecture Software developer's manual #2 says that the ZF is undefined, not that it is unchanged. In fact, the above code sequence is incorrect "by the book." -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 0: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 500AF152B6 for ; Wed, 17 Mar 1999 00:05:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA25289; Wed, 17 Mar 1999 09:05:00 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903170805.JAA25289@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903162322.BAA07920@ceia.nordier.com> from Robert Nordier at "Mar 17, 1999 1:22:10 am" To: rnordier@nordier.com (Robert Nordier) Date: Wed, 17 Mar 1999 09:05:00 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Robert Nordier wrote: > If the problem is the bootblocks, why not send a message to Robert > Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And > say, "This is what I want to do, what are we going to do about it?" > or something similar? OK, easy enough, this is what I want to do: Boot from an ata disk on major# 30, device name "ad", plain and simple. As the bootcode is now this wont work. If its as simple as me adding the pair 30 & "ad" somewhere, I'm satisfied, if not, I'm dissapointed :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 0:36:27 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 2885F152B9 for ; Wed, 17 Mar 1999 00:36:24 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id RAA02301; Wed, 17 Mar 1999 17:33:50 +0900 (JST) Message-ID: <36EF681E.D7669497@newsguy.com> Date: Wed, 17 Mar 1999 17:30:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <199903162020.VAA23935@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > So here I am with our new boot code and a new device, how the > @=9E$ am I supposed to boot from that with the glory new > boot blocks, forth and what have we ??? The glory new boot blocks rely on the good old BIOS to boot. Anything else is a chicken&egg problem. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 1:38:31 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 A1756151AE for ; Wed, 17 Mar 1999 01:38:20 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA25242; Wed, 17 Mar 1999 10:40:51 +0100 (MET) Date: Wed, 17 Mar 1999 10:37:49 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: dillon@backplane.com Cc: FreeBSD current mailing list Subject: Re: panic occurred: vm_fault 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 The fault seems to be reproducable. mount /cdrom find /cdrom -type f -exec cat \{\} >/dev/null \; -ls and pop it goes. Same stack trace. We could do a try-this-game this weekend (up to then I'm covered in work) if that would be helpfull. Let me know what information you need. Nick On Tue, 16 Mar 1999, Nick Hibma wrote: > > In case someone who is interested in the following panic: > > Occurred under a lightly loaded system that was not doing anything apart > from reading a CD (dd if=/dev/cd0c of=/dev/null bs=512). > Kernel current as of yesterday. > No core file is available unfortunately. > > > panic: vm_fault: fault on nofault entry, addr: c35c6000 > (blabla about debugger) > > show registers > cs 0x8 > ds 0x10 > es 0x10 > ss 0x10 > eax 0x12 > ecx 0xc00b8f00 > edx 0xc024d1a4 db_lengths+0x11c > ebx 0xc0248255 > __set_sysctl_set_sym_sysctl__vm_swap_async_max+0x1d9 > esp 0xc6f23ca8 > ebp 0xc6f23cb0 > esi 0x100 > edi 0xc35c6000 > eip 0xc020f993 Debugger+0x37 > efl 0x256 > > trace > panic > vm_fault > trap_pfault > trap > calltrap() > --- trap > slow_copyout > spec_read > ufsspec_read > ufs_vnoperatespec > vn_read > read > syscall > Xint0x80syscall > > > -- > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy > > > -- 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 Wed Mar 17 3: 9: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id 5D34314EE5 for ; Wed, 17 Mar 1999 03:08:51 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA13749; Wed, 17 Mar 1999 13:03:35 +0200 (SAT) From: Robert Nordier Message-Id: <199903171103.NAA13749@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903170805.JAA25289@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 17, 99 09:05:00 am" To: sos@freebsd.dk (Søren Schmidt) Date: Wed, 17 Mar 1999 13:03:33 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt wrote: > OK, easy enough, this is what I want to do: > > Boot from an ata disk on major# 30, device name "ad", plain and simple. I'd be inclined to handle this outside the boot code, by treating the passed in major# as describing the device rather than specifying the driver. The point about the boot code is it is deliberately intended to be usable when completely out of sync with any actual kernel it is booting. (I expect to be able to use 2.0 bootblocks with 4.0, and also that loader will be able to boot a 2.0 kernel.) I assume at some stage that some stage the new driver will take over completely, and the older driver will disappear. Before that, as people grow accustomed to thinking "ad" rather than "wd", it will probably make sense for the boot code to accept (say) 0:ad(0,a)boot/loader rather than 0:wd(0,a)boot/loader However, I'd *still* expect it to pass a major# of 0 rather than 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel knows only 30, it is -- at least -- in a position to know what 0 meant, and simply substitute one for the other (under the influence of a kernel configuration option, if necessary). As an example of the kind of reasoning that goes into the above, consider the case of booting from CD-ROM. If the boot image used is that of a floppy, the major# used is 2; if the boot image uses is that of a hard disk (quite probably a old 20M MFM 615x4x17 hard disk), the major# used is 0. So in both cases, the major# doesn't relate to what was booted from, and may not even describe the underlying technology correctly. > As the bootcode is now this wont work. If its as simple as me adding > the pair 30 & "ad" somewhere, I'm satisfied, if not, I'm dissapointed :) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:17:44 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 3E01214F4F for ; Wed, 17 Mar 1999 03:17:41 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id MAA25664; Wed, 17 Mar 1999 12:16:49 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171116.MAA25664@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171103.NAA13749@ceia.nordier.com> from Robert Nordier at "Mar 17, 1999 1: 3:33 pm" To: rnordier@nordier.com (Robert Nordier) Date: Wed, 17 Mar 1999 12:16:49 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Robert Nordier wrote: > Søren Schmidt wrote: > > > OK, easy enough, this is what I want to do: > > > > Boot from an ata disk on major# 30, device name "ad", plain and simple. > > I'd be inclined to handle this outside the boot code, by treating the > passed in major# as describing the device rather than specifying > the driver. > > The point about the boot code is it is deliberately intended to be > usable when completely out of sync with any actual kernel it is > booting. (I expect to be able to use 2.0 bootblocks with 4.0, and > also that loader will be able to boot a 2.0 kernel.) > > I assume at some stage that some stage the new driver will take over > completely, and the older driver will disappear. Before that, as > people grow accustomed to thinking "ad" rather than "wd", it will Not likely, as long as we need support for MFM/RLL/ESDI disk, wd.c will stay around. > probably make sense for the boot code to accept (say) > > 0:ad(0,a)boot/loader > > rather than > > 0:wd(0,a)boot/loader That would be nice, could I please have that ?? > However, I'd *still* expect it to pass a major# of 0 rather than > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > knows only 30, it is -- at least -- in a position to know what > 0 meant, and simply substitute one for the other (under the > influence of a kernel configuration option, if necessary). Hmm, wd should give 0 and ad should give 30, no AI please :) I've tried fooling the driver to just use the 0 number, but mount blows up, complaing that mounted root is different from specified root... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:34:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0B54815090 for ; Wed, 17 Mar 1999 03:34:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id DAA36816; Wed, 17 Mar 1999 03:32:40 -0800 (PST) (envelope-from obrien) Date: Wed, 17 Mar 1999 03:32:40 -0800 From: "David O'Brien" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990317033240.A36782@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903162322.BAA07920@ceia.nordier.com> <199903170805.JAA25289@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: =?iso-8859-1?Q?=3C199903170805=2EJAA25289=40freebsd=2Edk=3E=3B_from_S=F8?= =?iso-8859-1?Q?ren_Schmidt_on_Wed=2C_Mar_17=2C_1999_at_09:05:00AM_+0100?= X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Boot from an ata disk on major# 30, device name "ad", plain and simple. Does this mean ata disks won't come under CAM/da ? If not, can we PLEASE rename SCSI disks back to ``sd''? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:43:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 2279815274; Wed, 17 Mar 1999 03:43:05 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id OAA16894; Wed, 17 Mar 1999 14:42:46 +0300 (MSK) Date: Wed, 17 Mar 1999 14:42:46 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: disk quota overriding 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! There is a way to overflow / filesystem even is quota is enabled. Just make many hard links (for example /bin/sh) to /tmp/ for ($q=0;$q<100000;$q++){ system ("ln /bin/sh /tmp/ln$q"); } Because /tmp directory usually owned by root that why quotas has no effect. *Directory* size of /tmp can be grown up to available space on / filesystem. Any way to fix it? Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:50:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from bofh.fastnet.co.uk (lart.org.uk [194.207.104.22]) by hub.freebsd.org (Postfix) with ESMTP id 47C171500B; Wed, 17 Mar 1999 03:50:02 -0800 (PST) (envelope-from netadmin@bofh.fastnet.co.uk) Received: (from netadmin@localhost) by bofh.fastnet.co.uk (8.8.8/8.8.8) id LAA23132; Wed, 17 Mar 1999 11:49:33 GMT (envelope-from netadmin) Date: Wed, 17 Mar 1999 11:49:32 +0000 From: Jay Tribick To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding Message-ID: <19990317114932.Z21466@bofh.fastnet.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; "Dmitry Valdov" on 17.03.1999 @ 11:42:46 GMT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > There is a way to overflow / filesystem even is quota is enabled. > > Just make many hard links (for example /bin/sh) to /tmp/ > > for ($q=0;$q<100000;$q++){ > system ("ln /bin/sh /tmp/ln$q"); > } > > Because /tmp directory usually owned by root that why quotas has no effect. > *Directory* size of /tmp can be grown up to available space on / filesystem. > > Any way to fix it? Haven't tested this, but are you sure it fills the filesystem up - all a hard link is, is a file with the same inode as the original file (correct me if I'm wrong) - therefore it doesn't actually use any space other than that required to store the file entry. -- Regards, Jay Tribick [| Network Admin | FastNet International | http://fast.net.uk/ |] [| Finger netadmin@fastnet.co.uk for contact info & PGP PubKey |] [| +44 (0)1273 T: 677633 F: 621631 e: netadmin@fast.net.uk |] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:51:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sminter.com.ar (ns1.sminter.com.ar [200.10.100.10]) by hub.freebsd.org (Postfix) with ESMTP id 3DEAB1506F; Wed, 17 Mar 1999 03:51:23 -0800 (PST) (envelope-from fpscha@ns1.sminter.com.ar) Received: (from fpscha@localhost) by ns1.sminter.com.ar (8.8.5/8.8.4) id IAA23361; Wed, 17 Mar 1999 08:50:50 -0300 (GMT) From: Fernando Schapachnik Message-Id: <199903171150.IAA23361@ns1.sminter.com.ar> Subject: Re: disk quota overriding In-Reply-To: from Dmitry Valdov at "Mar 17, 99 02:42:46 pm" To: dv@dv.ru (Dmitry Valdov) Date: Wed, 17 Mar 1999 08:50:50 -0300 (GMT) Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 Are you aware that, due to nature of hardlinks the only extra space is same that for an empty file? Due to this, how many empty files do you think it takes to eat the whole space of / ? I'm I loosing something? Regards. En un mensaje anterior, Dmitry Valdov escribió: > Hi! > > There is a way to overflow / filesystem even is quota is enabled. > > Just make many hard links (for example /bin/sh) to /tmp/ > > for ($q=0;$q<100000;$q++){ > system ("ln /bin/sh /tmp/ln$q"); > } > > Because /tmp directory usually owned by root that why quotas has no effect. > *Directory* size of /tmp can be grown up to available space on / filesystem. > > Any way to fix it? Fernando P. Schapachnik Administracion de la red VIA Net Works Argentina SA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:53:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 66B2814CFB; Wed, 17 Mar 1999 03:53:52 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id OAA21067; Wed, 17 Mar 1999 14:53:19 +0300 (MSK) Date: Wed, 17 Mar 1999 14:53:19 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Jay Tribick Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <19990317114932.Z21466@bofh.fastnet.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Jay Tribick wrote: > Date: Wed, 17 Mar 1999 11:49:32 +0000 > From: Jay Tribick > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG > Subject: Re: disk quota overriding > > Hi > > > There is a way to overflow / filesystem even is quota is enabled. > > > > Just make many hard links (for example /bin/sh) to /tmp/ > > > > for ($q=0;$q<100000;$q++){ > > system ("ln /bin/sh /tmp/ln$q"); > > } > > > > Because /tmp directory usually owned by root that why quotas has no effect. > > *Directory* size of /tmp can be grown up to available space on / filesystem. > > > > Any way to fix it? > > Haven't tested this, but are you sure it fills the filesystem up - > all a hard link is, is a file with the same inode as the > original file (correct me if I'm wrong) - therefore it > doesn't actually use any space other than that required > to store the file entry. ^^^^^^^^^^^^^^^^^^^^^ Yes. But /tmp dir is under root filesystem. So *directory* size of /tmp can be grown up to free space on /. Which will result 0 bytes free on / :) All available space will be used to store directory entries. Dmitry. PS. Sorry for my english. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 3:56:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id F259E1535D; Wed, 17 Mar 1999 03:56:34 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with ESMTP id OAA21212; Wed, 17 Mar 1999 14:56:07 +0300 (MSK) Date: Wed, 17 Mar 1999 14:56:07 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Fernando Schapachnik Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <199903171150.IAA23361@ns1.sminter.com.ar> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Fernando Schapachnik wrote: > Date: Wed, 17 Mar 1999 08:50:50 -0300 (GMT) > From: Fernando Schapachnik > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG > Subject: Re: disk quota overriding > > Are you aware that, due to nature of hardlinks the only extra space is > same that for an empty file? Due to this, how many empty files do you > think it takes to eat the whole space of / ? No. Many empty files can be controlled by INODE QUOTAS. Hard links can't. But I can create as many hard links as I need to eat up the whole space of /... > > I'm I loosing something? > > Regards. > > En un mensaje anterior, Dmitry Valdov escribió: > > Hi! > > > > There is a way to overflow / filesystem even is quota is enabled. > > > > Just make many hard links (for example /bin/sh) to /tmp/ > > > > for ($q=0;$q<100000;$q++){ > > system ("ln /bin/sh /tmp/ln$q"); > > } > > > > Because /tmp directory usually owned by root that why quotas has no effect. > > *Directory* size of /tmp can be grown up to available space on / filesystem. > > > > Any way to fix it? > > > Fernando P. Schapachnik > Administracion de la red > VIA Net Works Argentina SA > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4: 6:27 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 4A9FB154C2 for ; Wed, 17 Mar 1999 04:06:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id NAA25764; Wed, 17 Mar 1999 13:05:51 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171205.NAA25764@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317033240.A36782@relay.nuxi.com> from "David O'Brien" at "Mar 17, 1999 3:32:40 am" To: obrien@NUXI.com Date: Wed, 17 Mar 1999 13:05:51 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David O'Brien wrote: > > Boot from an ata disk on major# 30, device name "ad", plain and simple. > > Does this mean ata disks won't come under CAM/da ? Not if I can help it :) It could be done by slamming a translation layer ontop of the existing wd driver or of cause on top of the new I'm doing, but all it adds is overhead, both performance wise and codesize wise. There is nothing that prohibits having both of cause, but it is not a priority for me to add more complexity into the picture before everything else is done. > If not, can we PLEASE rename SCSI disks back to ``sd''? No objections from me. But why, it will only confuse users once again... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:10:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id AF5EF15567 for ; Wed, 17 Mar 1999 04:10:14 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 29384 invoked by uid 1001); 17 Mar 1999 12:09:55 +0000 (GMT) To: obrien@NUXI.com Cc: sos@freebsd.dk, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? From: sthaug@nethelp.no In-Reply-To: Your message of "Wed, 17 Mar 1999 03:32:40 -0800" References: <19990317033240.A36782@relay.nuxi.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 17 Mar 1999 13:09:54 +0100 Message-ID: <29382.921672594@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Boot from an ata disk on major# 30, device name "ad", plain and simple. > > Does this mean ata disks won't come under CAM/da ? > If not, can we PLEASE rename SCSI disks back to ``sd''? Agreed. I see no justification for the sd -> da change if the ATA disks won't (eventually) be included. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:20: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id DE24514C46 for ; Wed, 17 Mar 1999 04:19:55 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id PAA03974; Wed, 17 Mar 1999 15:19:25 +0300 (MSK) (envelope-from mishania) Date: Wed, 17 Mar 1999 15:19:25 +0300 From: "Mikhail A. Sokolov" To: Greg Lehey Cc: "Mikhail A. Sokolov" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990317151924.B3718@demos.su> References: <19990316223637.A31464@demos.su> <19990317125112.T429@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990317125112.T429@lemis.com>; from Greg Lehey on Wed, Mar 17, 1999 at 12:51:12PM +1030 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 12:51:12PM +1030, Greg Lehey wrote: # On Tuesday, 16 March 1999 at 22:36:38 +0300, Mikhail A. Sokolov wrote: # > Hello, # > # > we're experiencing repeated 4.0-C (as of today, something around 12:00 # > GMT, 1999-03-16) ufs_dirbad() panics, which are the # > following (below), which usually occur when squid is running. The box # > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. # > Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): # > /var/crash# gdb -k kernel.1 vmcore.1 # > IdlePTD 2682880 # > initial pcb at 21c7b8 # > panicstr: ufs_dirbad: bad dir # > panic messages: # > --- # > panic: ufs_dirbad: bad dir # # Have you looked at the directory? Theoretically this could be a # really mangled directory structure. Yes, of course. Those swap catalogues which are not to be touched by squid are turned into it's swapfiles, sometimes there's an error of 'bad file descriptor' and such. As I said in reply to Julian, I've newfs'ed these spools plenty times, - errors are repeated and, besides, lookalike. That's a glitch in FFS somewhere, I assume: I've had similiar panics on another squid with exactly the very same hardware/software configuration, besides the fact the OS there was 3.[01]-S. Similiar panics, different scsi disks, tryed not to use the mentioned IFT RAID - no difference. I.e. I could've agreed with that this could be really doomed directory, but no, it's not that way, squid's allocating objects in memory, when it reaches the limit it'd swap it to the spool (as per LRU and such rules) and then, after it dies, I find that ~1 recursive swap file (2 disksx9gb, 256 catalogues of 16 subdirs each in 8 and 6 cache_dirs as applicable to two spools) in each of the subdirs (second level cache) has died, - has been automagically converted to contain some crap [by FFS?]. What could help is that squid is configured to use poll(), doesn't use threads, doesn't do async (i.e. as squid undestands it, it's an option there) operations. Mounts on the FS's are noatime, but that ain't is the culprit, ain't they? # Greg # -- # See complete headers for address, home page and phone numbers # finger grog@lemis.com for PGP public key -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:21:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 54B4415281 for ; Wed, 17 Mar 1999 04:21:28 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (postfix@myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id OAA28718; Wed, 17 Mar 1999 14:21:07 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 2EAEE10B; Wed, 17 Mar 1999 14:21:07 +0200 (EET) Message-ID: <19990317142107.A78437@matti.ee> Date: Wed, 17 Mar 1999 14:21:07 +0200 From: Vallo Kallaste To: Greg Lehey Cc: freebsd-current@freebsd.org Subject: Crash while newfs'ing innocent vinum volume on fresh system. Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.93.2i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! Before of all I want to make sure that you understand the conditions=20 here: I have reinstalled fresh 3.1-RELEASE to the machine in question,=20 before swapped out two memory DIMM's to the single new 32MB one, just=20 to be sure it's not some kind of memory error. Installation went=20 fine, the developer type of installation with full sources but no=20 games, heh. Then I downloaded your newest archive for vinum installation:=20 vinum-4.0-CURRENT.tar.gz from ftp.nanyang-computer.com/pub/vinum/. =20 It's marked as March 14. Packed it off over the /usr/src and done=20 compilations in module section and control program section. I also=20 done make cleandir; make clean in the appropriate directories=20 several times just to be sure. Compilations went fine and the module=20 and control program are in the right places with right dates showing=20 these are newer ones. Copied the same kernel configuration file as usual to the right place=20 from backup. Made some minor changes to kernel configuration, removed=20 DMA support for ata disks, I don't trust the support very much yet. Made new debug kernel, copied to /var/crash, stripped the original=20 with -g and installed. Reboot. Machine goes up, multiuser mode. Right after reboot there are no=20 modules in loaded. Executed "vinum create stripe.conf", ok. Executed=20 vinum init, vinum debug 96, vinum saveconfig, vinum printconfig=20 blabla. All is ok yet. Newfs -n1 -d0 -v /dev/vinum/rsvol .... two lines newfs output and=20 crash: Script started on Wed Mar 17 13:24:45 1999 sh-2.02# gdb -k ker=07nel.gdb vmcore.0=20 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd),=20 Copyright 1996 Free Software Foundation, Inc... IdlePTD 2760704 initial pcb at 23af94 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xdeadc0e6 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xf0a4bc34 stack pointer =3D 0x10:0xf3db8da8 frame pointer =3D 0x10:0xf3db8db8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 259 (newfs) interrupt mask =3D=20 panic: from debugger panic: from debugger dumping to dev 20001, offset 65536 dump 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=20 --- #0 boot (howto=3D260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 =3D rcr3(); (kgdb) add-symbol-file /modules/vinum.ko 0x00005ba8+ A syntax error in expression, near `'. (kgdb) add-symbol-file /modules/vinum.ko 0x00005ba8 add symbol table from file "/modules/vinum.ko" at text_addr =3D 0x5ba8? (y or n) y (kgdb) bt #0 boot (howto=3D260) at ../../kern/kern_shutdown.c:285 #1 0xf01324b5 in panic (fmt=3D0xf020e0cc "from debugger") at ../../kern/kern_shutdown.c:446 #2 0xf01188fd in db_panic (addr=3D-257639372, have_addr=3D0, count=3D-1,= =20 modif=3D0xf3db8c2c "") at ../../ddb/db_command.c:432 #3 0xf011889d in db_command (last_cmdp=3D0xf0227e7c, cmd_table=3D0xf0227cd= c,=20 aux_cmd_tablep=3D0xf0238c80) at ../../ddb/db_command.c:332 #4 0xf0118962 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf011acb3 in db_trap (type=3D12, code=3D0) at ../../ddb/db_trap.c:71 #6 0xf01e1056 in kdb_trap (type=3D12, code=3D0, regs=3D0xf3db8d6c) at ../../i386/i386/db_interface.c:157 #7 0xf01eb47c in trap_fatal (frame=3D0xf3db8d6c, eva=3D3735929062) at ../../i386/i386/trap.c:937 #8 0xf01eb15b in trap_pfault (frame=3D0xf3db8d6c, usermode=3D0, eva=3D3735= 929062) at ../../i386/i386/trap.c:835 #9 0xf01eadba in trap (frame=3D{tf_es =3D -203751408, tf_ds =3D -203751408= ,=20 tf_edi =3D -559038242, tf_esi =3D -2147483648, tf_ebp =3D -203715144,= =20 tf_isp =3D -203715180, tf_ebx =3D -258066920, tf_edx =3D 16384, tf_ec= x =3D 14,=20 tf_eax =3D -16162, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -257639= 372,=20 tf_cs =3D 8, tf_eflags =3D 66182, tf_esp =3D -257699840, tf_ss =3D -2= 45981592}) at ../../i386/i386/trap.c:437 #10 0xf0a4bc34 in ?? () #11 0xf0a4bae1 in ?? () #12 0xf0a4b8b6 in ?? () ---Type to continue, or q to quit--- #13 0xf012ffec in physio (strategy=3D0xf0a4b808 , bp=3D0x0,= =20 dev=3D23296, rw=3D0, minp=3D0xf01300dc , uio=3D0xf3db8f34) at ../../kern/kern_physio.c:113 #14 0xf0a4c97c in ?? () #15 0xf0162f2f in spec_write (ap=3D0xf3db8ef8) at ../../miscfs/specfs/spec_vnops.c:355 #16 0xf01c3b18 in ufsspec_write (ap=3D0xf3db8ef8) at ../../ufs/ufs/ufs_vnops.c:1840 #17 0xf01c408d in ufs_vnoperatespec (ap=3D0xf3db8ef8) at ../../ufs/ufs/ufs_vnops.c:2312 #18 0xf015d3b7 in vn_write (fp=3D0xf0a3ca80, uio=3D0xf3db8f34, cred=3D0xf0a= 39f80) at vnode_if.h:331 #19 0xf013cf46 in write (p=3D0xf3d71b20, uap=3D0xf3db8f84) at ../../kern/sys_generic.c:270 #20 0xf01eb68b in syscall (frame=3D{tf_es =3D 39, tf_ds =3D 39, tf_edi =3D = 134669408,=20 tf_esi =3D 8192, tf_ebp =3D -272641880, tf_isp =3D -203714604, tf_ebx= =3D 64,=20 tf_edx =3D 0, tf_ecx =3D 32768, tf_eax =3D 4, tf_trapno =3D 12, tf_er= r =3D 2,=20 tf_eip =3D 134539244, tf_cs =3D 31, tf_eflags =3D 582, tf_esp =3D -27= 2641916,=20 tf_ss =3D 39}) at ../../i386/i386/trap.c:1100 #21 0xf01e19ac in Xint0x80_syscall () #22 0x804b80d in ?? () #23 0x804b245 in ?? () #24 0x80490bc in ?? () #25 0x80480e9 in ?? () (kgdb) f 1 #1 0xf01324b5 in panic (fmt=3D0xf020e0cc "from debugger") at ../../kern/kern_shutdown.c:446 446 boot(bootopt); (kgdb) quit sh-2.02# exit Script done on Wed Mar 17 13:25:52 1999 kernel configuration: # Vokk machine "i386" ident Vokk maxusers 80 options PQ_NOOPT # color for 512k/16k cache config kernel root on wd0 cpu "I686_CPU" # aka Pentium Pro(tm) options "NO_F00F_HACK" options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options "VM86" options DDB options INVARIANTS options INVARIANT_SUPPORT options UCONSOLE options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter options "ICMP_BANDLIM" options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device #options SOFTUPDATES options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=3D199309L" pseudo-device pty 32 #Pseudo ttys - can go as high as 256 pseudo-device vn 2 #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. options "MSGBUF_SIZE=3D40960" controller isa0 controller pnp0 device atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=3D8 # number of virtual consoles options SC_HISTORY_SIZE=3D600 # number of history buffer lines options VESA # needs VM86 defined too!! device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80ff80ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM options IDE_DELAY=3D2000 # Be optimistic about Joe IDE device device acd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device pcm0 at isa? port ? tty irq ? drq ? controller pci0 device fxp0 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? controller ppc0 at isa? port ? tty irq 7 options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION #options COMPAT_LINUX options PANIC_REBOOT_WAIT_TIME=3D30 Stripe configuration: # mingi konf vinumile # Kettad drive drive1 device /dev/wd1s1e drive drive2 device /dev/wd2s1e # Volume u"he stripitud plexiga volume svol plex org striped 256b sd length 2380m drive drive1 sd length 2380m drive drive2 mount information: /dev/wd0s1a on / (local, writes: sync 14 async 82) /dev/wd0s1f on /usr (local, writes: sync 2 async 63) /dev/wd0s1e on /var (local, writes: sync 93 async 215) procfs on /proc (local) swap information: Device 1K-blocks Used Avail Capacity Type /dev/wd0s1b 65536 0 65408 0% Interleaved /dev/wd1s1b 65536 0 65408 0% Interleaved /dev/wd2s1b 65536 0 65408 0% Interleaved Total 196224 0 196224 0% disklabels: # /dev/rwd0c: type: ESDI disk: wd0s1 label:=20 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 6255 sectors/unit: 6305985 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0=20 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 262144 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 260*) b: 131072 262144 swap # (Cyl. 260*- 390*) c: 6305985 0 unused 0 0 # (Cyl. 0 - 6255*) e: 262144 393216 4.2BSD 1024 8192 16 # (Cyl. 390*- 650*) f: 5650625 655360 4.2BSD 1024 8192 16 # (Cyl. 650*- 6255*) # /dev/rwd1c: type: ESDI disk: wd1s1 label:=20 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 15 sectors/cylinder: 945 cylinders: 5299 sectors/unit: 5008437 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0=20 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 131072 0 swap # (Cyl. 0 - 138*) c: 5008437 0 unused 0 0 # (Cyl. 0 - 5299*) e: 4877365 131072 unused 0 0 # (Cyl. 138*- 5299*) # /dev/rwd2c: type: ESDI disk: wd2s1 label:=20 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 15 sectors/cylinder: 945 cylinders: 5299 sectors/unit: 5008437 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0=20 8 partitions: # size offset fstype [fsize bsize bps/cpg] b: 131072 0 swap # (Cyl. 0 - 138*) c: 5008437 0 unused 0 0 # (Cyl. 0 - 5299*) e: 4877365 131072 unused 0 0 # (Cyl. 138*- 5299*) Your access to the machine in question is alive when you need it. I=20 don't have any clue what's going on, the machine crashes left and=20 right with vinum under quite light load. Without it I'm able to do=20 buildworld -j8 without any trouble. Thanks for your ongoing work --=20 Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:33:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 7353614FC1 for ; Wed, 17 Mar 1999 04:33:46 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id PAA04443; Wed, 17 Mar 1999 15:33:06 +0300 (MSK) (envelope-from mishania) Date: Wed, 17 Mar 1999 15:33:06 +0300 From: "Mikhail A. Sokolov" To: Greg Lehey Cc: "Mikhail A. Sokolov" , current@FreeBSD.org Subject: Re: repeated ffs_blkfreepanics@demos.su, 4.0-C Message-ID: <19990317153305.C3718@demos.su> References: <19990316224121.A86239@demos.su> <19990317125440.U429@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990317125440.U429@lemis.com>; from Greg Lehey on Wed, Mar 17, 1999 at 12:54:40PM +1030 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 17, 1999 at 12:54:40PM +1030, Greg Lehey wrote: # On Tuesday, 16 March 1999 at 22:41:22 +0300, Mikhail A. Sokolov wrote: # > Hello, # > the box is the same as in previous mail of mine which described ufs_dirbad() # > panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some # > 30 requests/second). # # These two crashes both tend to suggest a file system structure problem # which fsck doesn't detect. What's the vp in the ffs_truncate frame? Couldn't help agreeing more ;) See previous answer, though. # How does it compare to the *vpp in the ufs_lookup frame of the # previous dump? Unfortunately, at the moment I have to admit I have been able to afford keeping the dumps, let's wait the next time. Then again, whilst I am typing this (below). I tend to be somewhat amazed that the frame 8 is usually the same for many different panics this box experiences (little summary: this is probably to be named the most panicing FreeBSD box in the world, 140 panics in a month, all the hardware has been swapped to the same, but new (i.e. reproduced the same configuration from spare new parts), panics were either already announced by other peple, like, Matthew Jacob's reports, or fixed after many other different reports, like, Matthew Dillon's work brought much more stability to the beast, no more 'lockmgr: locking against myself' and 'vm_page*' of many kinds. Then again, this box is an experimental and was brought to 4.0-C to check if it could survive with it, since it couldn't when it was 3.1-S) var/crash# gdb -k *3 initial pcb at 21c7b8 panicstr: ffs_valloc: dup alloc panic messages: --- panic: ffs_valloc: dup alloc syncing disks... 147 75 2 done (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation code Btw, Kenneth, I know this is harmless, but didn't Justing's (Gibbs) explicitely forbid the sync cache to be so verbose or I confuse wanted with the done things?;) dumping to dev 20401, offset 821524 dump 256 ... --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc013b4b9 in panic (fmt=0xc01fdf01 "ffs_valloc: dup alloc") at ../../kern/kern_shutdown.c:448 #2 0xc01b4e84 in ffs_valloc (pvp=0xce418ac0, mode=33188, cred=0xc1fab580, vpp=0xce264cd0) at ../../ufs/ffs/ffs_alloc.c:604 #3 0xc01c21cd in ufs_makeinode (mode=33188, dvp=0xce418ac0, vpp=0xce264f14, cnp=0xce264f28) at ../../ufs/ufs/ufs_vnops.c:2097 #4 0xc01bf9de in ufs_create (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:179 #5 0xc01c23a1 in ufs_vnoperate (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:2309 #6 0xc01631c7 in vn_open (ndp=0xce264f04, fmode=1550, cmode=420) at vnode_if.h:83 #7 0xc015fee9 in open (p=0xcce8b860, uap=0xce264f94) at ../../kern/vfs_syscalls.c:928 #8 0xc01e769f in syscall (frame={tf_es = 47, tf_ds = -1078067153, tf_edi = 1549, tf_esi = 247619088, tf_ebp = -1078010952, tf_isp = -836349980, tf_ebx = 134788528, tf_edx = 219774816, tf_ecx = 0, tf_eax = 5, tf_trapno = 22, tf_err = 2, tf_eip = 672227132, tf_cs = 31, tf_eflags = 534, tf_esp = -1078010980, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #9 0xc01de9fc in Xint0x80_syscall () #10 0x808ae54 in ?? () #11 0x808b3c2 in ?? () #12 0x8084c1f in ?? () #13 0x8067e87 in ?? () #14 0x805c06a in ?? () #15 0x8071f7f in ?? () #16 0x804a1b1 in ?? () (kgdb) # # Greg # -- # See complete headers for address, home page and phone numbers # finger grog@lemis.com for PGP public key -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:37:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 135DB15614; Wed, 17 Mar 1999 04:37:23 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id PAA05380; Wed, 17 Mar 1999 15:37:03 +0300 (MSK) Date: Wed, 17 Mar 1999 15:37:03 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: Re: disk quota overriding 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! I think that there is only one way to fix it - it's to disable making *hard*links to directory with mode 1777. On Wed, 17 Mar 1999, Dmitry Valdov wrote: > Date: Wed, 17 Mar 1999 14:42:46 +0300 (MSK) > From: Dmitry Valdov > To: freebsd-current@freebsd.org, freebsd-security@freebsd.org > Subject: disk quota overriding > > Hi! > > There is a way to overflow / filesystem even is quota is enabled. > > Just make many hard links (for example /bin/sh) to /tmp/ > > for ($q=0;$q<100000;$q++){ > system ("ln /bin/sh /tmp/ln$q"); > } > > Because /tmp directory usually owned by root that why quotas has no effect. > *Directory* size of /tmp can be grown up to available space on / filesystem. > > Any way to fix it? > > Dmitry. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:46:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CD0A3152D4 for ; Wed, 17 Mar 1999 04:46:15 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id HAA01173; Wed, 17 Mar 1999 07:45:27 -0500 (EST) Date: Wed, 17 Mar 1999 07:45:26 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Vallo Kallaste Cc: Greg Lehey , freebsd-current@FreeBSD.ORG Subject: Re: Crash while newfs'ing innocent vinum volume on fresh system. In-Reply-To: <19990317142107.A78437@matti.ee> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know what frames 10-12 are supposed to be, but I can give you the short answer on why it crashed: you have INVARIANTS on (good!), so free()ing stuffs memory with 0xdeadc0de. Whatever frame 10 was doing tried to dereference previously freed memory. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:48:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 386A41522E for ; Wed, 17 Mar 1999 04:48:48 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id EAA17854; Wed, 17 Mar 1999 04:47:55 -0800 Date: Wed, 17 Mar 1999 04:47:54 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "David O'Brien" Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317033240.A36782@relay.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I asked Soren just this kind of question, and he declined to answer. I doan geddit... On Wed, 17 Mar 1999, David O'Brien wrote: > > Boot from an ata disk on major# 30, device name "ad", plain and simple. > > Does this mean ata disks won't come under CAM/da ? > If not, can we PLEASE rename SCSI disks back to ``sd''? > > -- > -- 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 4:55:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-3-dbn.dial-up.net [196.34.155.3]) by hub.freebsd.org (Postfix) with ESMTP id 790D814D4D for ; Wed, 17 Mar 1999 04:55:05 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA14182; Wed, 17 Mar 1999 14:49:52 +0200 (SAT) From: Robert Nordier Message-Id: <199903171249.OAA14182@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171116.MAA25664@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 17, 99 12:16:49 pm" To: sos@freebsd.dk (Søren Schmidt) Date: Wed, 17 Mar 1999 14:49:50 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I assume at some stage that some stage the new driver will take over > > completely, and the older driver will disappear. Before that, as > > people grow accustomed to thinking "ad" rather than "wd", it will > > Not likely, as long as we need support for MFM/RLL/ESDI disk, wd.c > will stay around. > > > probably make sense for the boot code to accept (say) > > > > 0:ad(0,a)boot/loader > > > > rather than > > > > 0:wd(0,a)boot/loader > > That would be nice, could I please have that ?? OK, I'll add it to the bootblocks. Incidentally, while I'm in there and thinking about it, I'd quite like to fix the boot code to boot from LS-120 drives at the same time. So if anyone has one of these, and wouldn't mind spending some time running a few bits of test code, I'd appreciate it. > > However, I'd *still* expect it to pass a major# of 0 rather than > > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > > knows only 30, it is -- at least -- in a position to know what > > 0 meant, and simply substitute one for the other (under the > > influence of a kernel configuration option, if necessary). > > Hmm, wd should give 0 and ad should give 30, no AI please :) I wasn't actually thinking at all along the lines of "smart" code at all: #ifdef FORCE_FOO if (foo == 0) foo = 30; #endif The administrator or operator is still entirely in control; the only difference is in what part of the code the control is exercised. AFAICS, adopting the separate "wd" and "ad" route entails the following: Update your bootblocks. Add a /boot.config statement like "0:ad(0,a)" to make use of the driver the default. Failure to boot if you inadvertently specify wd out of habit, or if you specify ad when booting an earlier system. So we're introducing three points with good potential for failure. In contrast, the kernel configuration route requires commenting or uncommenting a single statement. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5: 1:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (Postfix) with ESMTP id D216C14BE5 for ; Wed, 17 Mar 1999 05:01:08 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id GAA01545; Wed, 17 Mar 1999 06:00:48 -0700 (MST) Date: Wed, 17 Mar 1999 06:00:48 -0700 (MST) Message-Id: <199903171300.GAA01545@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 3.1-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRATA.TXT The last update was sent: Sat Mar 13 03:20:55 1999 This update is sent: Wed Mar 17 06:00:48 1999 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o DOS installation fails when you actually follow the instructions to install stuff under C:\FREEBSD\BIN\... and so on. Fix: The instructions are correct but the code was wrong in 3.1-RELEASE, sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) or under C:\RELEASES\ (C:\RELEASES\BIN\... and so on). Fixed in 3.1-STABLE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:28:31 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 4E4BE150EF for ; Wed, 17 Mar 1999 05:28:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA26004; Wed, 17 Mar 1999 14:28:03 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171328.OAA26004@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: from Matthew Jacob at "Mar 17, 1999 4:47:54 am" To: mjacob@feral.com Date: Wed, 17 Mar 1999 14:28:02 +0100 (CET) Cc: obrien@NUXI.com, 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 Matthew Jacob wrote: > > I asked Soren just this kind of question, and he declined to answer. I > doan geddit... WHAT ?? I replied with this: #From sos Wed Mar 17 08:51:14 1999 #Subject: Re: How to add a new bootdevice to the new boot code ??? #In-Reply-To: from Matthew Jacob at "Mar 16, 1999 3:11: 1 pm" #To: mjacob@feral.com #Date: Wed, 17 Mar 1999 08:51:14 +0100 (CET) # #It seems Matthew Jacob wrote: # #>Is this a rant or a request for information? # #I could be both :), but basically I want to know what should be #done to have it boot from a new major#, in this case 30 the #new ata driver. But from a look at the code it seems that this #might be alot more work than it should be.... Geddit now ?? At least try to read to the end of your mailbox, before accusing me for ignorance, thankyou! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:39: 3 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 AB5EB14D41 for ; Wed, 17 Mar 1999 05:39:00 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id OAA26021; Wed, 17 Mar 1999 14:38:17 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171338.OAA26021@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171249.OAA14182@ceia.nordier.com> from Robert Nordier at "Mar 17, 1999 2:49:50 pm" To: rnordier@nordier.com (Robert Nordier) Date: Wed, 17 Mar 1999 14:38:17 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Robert Nordier wrote: > OK, I'll add it to the bootblocks. > > Incidentally, while I'm in there and thinking about it, I'd quite > like to fix the boot code to boot from LS-120 drives at the same > time. So if anyone has one of these, and wouldn't mind spending > some time running a few bits of test code, I'd appreciate it. I have a ZIP if that can help you ?? > > > However, I'd *still* expect it to pass a major# of 0 rather than > > > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > > > knows only 30, it is -- at least -- in a position to know what > > > 0 meant, and simply substitute one for the other (under the > > > influence of a kernel configuration option, if necessary). > > > > Hmm, wd should give 0 and ad should give 30, no AI please :) > > I wasn't actually thinking at all along the lines of "smart" code > at all: > > #ifdef FORCE_FOO > if (foo == 0) > foo = 30; > #endif Well, that breaks somewhere else, as the mount code is clever enough to look at the name of the driver in this case "ad" which doesn't match the specified #0 ie "wd". I kindof tried this by having my driver put itself in both the wd & ad majors in the table, but that doesn't work, because the mount stuff gets confused on the root name somehow, and fails to mount root because the names dont match... > AFAICS, adopting the separate "wd" and "ad" route entails the > following: > > Update your bootblocks. > Add a /boot.config statement like "0:ad(0,a)" to make use > of the driver the default. > Failure to boot if you inadvertently specify wd out of habit, > or if you specify ad when booting an earlier system. > > So we're introducing three points with good potential for failure. Well, what else can we do as long as we potentially need both drivers in the kernel. I'm pretty sure that if I kill of wd.c et all, there will be screams of bloody murder again... been there done that :) > In contrast, the kernel configuration route requires commenting > or uncommenting a single statement. But that doesn't work, at least as the mount code behaves now. At any rate, any solution that makes it possible to boot with a new driver without me having to call it "wd" something all over the place is acceptable to me... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id C24FD15165; Wed, 17 Mar 1999 05:40:36 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Wed, 17 Mar 1999 14:42:39 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097564@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Dmitry Valdov' , freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: RE: disk quota overriding Date: Wed, 17 Mar 1999 14:37:32 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Dmitry Valdov [SMTP:dv@dv.ru] > Sent: Wednesday, March 17, 1999 1:37 PM > To: freebsd-current@freebsd.org; freebsd-security@freebsd.org > Subject: Re: disk quota overriding > > Hi! > > > I think that there is only one way to fix it - it's to disable making > *hard*links to directory with mode 1777. > [ML] But only if the quotas have been turned on. BTW, has chown been "fixed" to the ludicrous SysV semantics that the root and owner can chown a file? If so, the latter has to be disabled in presence of quotas on the volume--otherwise: touch big_file chmod 777 big_file chown root:wheel big_file cat /dev/zero >>big_file This joke used to work on HPUX 10.something which kept the owner-may-chown semantics even in presence of quotas. It was not funny. (I don't know whether HP has fixed that). /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:45:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 2974215222; Wed, 17 Mar 1999 05:45:47 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id IAA21904; Wed, 17 Mar 1999 08:44:12 -0500 (EST) From: Mikhail Teterin Message-Id: <199903171344.IAA21904@kot.ne.mediaone.net> Subject: Re: disk quota overriding In-Reply-To: from Dmitry Valdov at "Mar 17, 1999 03:37:03 pm" To: dv@dv.ru (Dmitry Valdov) Date: Wed, 17 Mar 1999 08:44:11 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Because /tmp directory usually owned by root that why quotas has no effect. => *Directory* size of /tmp can be grown up to available space on / filesystem. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:49:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 4202F1531C; Wed, 17 Mar 1999 05:49:34 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id QAA29170; Wed, 17 Mar 1999 16:47:36 +0300 (MSK) Date: Wed, 17 Mar 1999 16:47:36 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Ladavac Marino Cc: freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: RE: disk quota overriding In-Reply-To: <97A8CA5BF490D211A94F0000F6C2E55D097564@s-lmh-wi-900.corpnet.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Ladavac Marino wrote: > Date: Wed, 17 Mar 1999 14:37:32 +0100 > From: Ladavac Marino > To: 'Dmitry Valdov' , freebsd-current@freebsd.org, > freebsd-security@freebsd.org > Subject: RE: disk quota overriding > > > -----Original Message----- > > From: Dmitry Valdov [SMTP:dv@dv.ru] > > Sent: Wednesday, March 17, 1999 1:37 PM > > To: freebsd-current@freebsd.org; freebsd-security@freebsd.org > > Subject: Re: disk quota overriding > > > > Hi! > > > > > > I think that there is only one way to fix it - it's to disable making > > *hard*links to directory with mode 1777. > > > [ML] But only if the quotas have been turned on. Sure. What Core Team thinks about it? Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 5:50:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 2996814CC5 for ; Wed, 17 Mar 1999 05:50:17 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA01090; Wed, 17 Mar 1999 14:49:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA41616; Wed, 17 Mar 1999 14:49:44 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: "David O'Brien" , =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Wed, 17 Mar 1999 04:47:54 PST." Date: Wed, 17 Mar 1999 14:49:43 +0100 Message-ID: <41614.921678583@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you are missing the point. We will not chuck the old wd* driver until people have crashed all MFM, RLL, ESDI and !ATA IDE drives. So we WANT to be able to tell the difference... Poul-Henning In message , Matthew Jacob w rites: > >I asked Soren just this kind of question, and he declined to answer. I >doan geddit... > >On Wed, 17 Mar 1999, David O'Brien wrote: > >> > Boot from an ata disk on major# 30, device name "ad", plain and simple. >> >> Does this mean ata disks won't come under CAM/da ? >> If not, can we PLEASE rename SCSI disks back to ``sd''? >> >> -- >> -- 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 >> > > > >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 Wed Mar 17 6:42:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from woodstock.monkey.net (pern-2-41.mdm.mkt.execpc.com [169.207.89.169]) by hub.freebsd.org (Postfix) with ESMTP id 50BA114BF1; Wed, 17 Mar 1999 06:42:10 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 12DFF62; Wed, 17 Mar 1999 08:41:48 -0600 (CST) To: Ladavac Marino Cc: "'Dmitry Valdov'" , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-reply-to: Your message of "Wed, 17 Mar 1999 14:37:32 +0100." <97A8CA5BF490D211A94F0000F6C2E55D097564@s-lmh-wi-900.corpnet.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Mar 1999 08:41:47 -0600 From: Jon Hamilton Message-Id: <19990317144148.12DFF62@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <97A8CA5BF490D211A94F0000F6C2E55D097564@s-lmh-wi-900.corpnet.at>, La davac Marino wrote: } BTW, has chown been "fixed" to the ludicrous SysV semantics that } the root and owner can chown a file? If so, the latter has to be } disabled in presence of quotas on the volume--otherwise: } } touch big_file } chmod 777 big_file } chown root:wheel big_file } cat /dev/zero >>big_file } } This joke used to work on HPUX 10.something which kept the } owner-may-chown semantics even in presence of quotas. It was not funny. } (I don't know whether HP has fixed that). Under HP-UX 9.x, the behavior you describe was the default, and it was changable by altering a kernel config parameter and relinking the kernel. The same tunable is available under 10.x, but I'm less certain what the default behavior is there. Whether quotas are enabled or not does not affect the behavior, only the kernel tunable parameter. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 6:59:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.acadiau.ca (relay.acadiau.ca [131.162.2.90]) by hub.freebsd.org (Postfix) with ESMTP id 89AEC14D71; Wed, 17 Mar 1999 06:59:24 -0800 (PST) (envelope-from 026809r@dragon.acadiau.ca) Received: from dragon.acadiau.ca (dragon.acadiau.ca [131.162.1.79]) by relay.acadiau.ca (8.8.5/8.8.5) with ESMTP id KAA02991; Wed, 17 Mar 1999 10:58:21 -0400 (AST) Received: from localhost (026809r@localhost) by dragon.acadiau.ca (8.8.8+Sun/8.8.8) with ESMTP id KAA11028; Wed, 17 Mar 1999 10:58:16 -0400 (AST) Date: Wed, 17 Mar 1999 10:58:16 -0400 (AST) From: Michael Richards <026809r@dragon.acadiau.ca> X-Sender: 026809r@dragon To: Jon Hamilton Cc: Ladavac Marino , "'Dmitry Valdov'" , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <19990317144148.12DFF62@woodstock.monkey.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 Wed, 17 Mar 1999, Jon Hamilton wrote: > } touch big_file > } chmod 777 big_file > } chown root:wheel big_file > } cat /dev/zero >>big_file > } This joke used to work on HPUX 10.something which kept the > } owner-may-chown semantics even in presence of quotas. It was not funny. > } (I don't know whether HP has fixed that). > > Under HP-UX 9.x, the behavior you describe was the default, and it > was changable by altering a kernel config parameter and relinking the > kernel. The same tunable is available under 10.x, but I'm less certain > what the default behavior is there. Whether quotas are enabled or not > does not affect the behavior, only the kernel tunable parameter. We all know that there are oodles of security problems associated with file giveaways. As I recall, all the texts I have ever read on the subject say that unless there is a very good reason to allow giveaways, they should be disabled. -Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 7:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from tsolab.org (dnn.rockefeller.edu [129.85.17.127]) by hub.freebsd.org (Postfix) with ESMTP id 8FB7814CA9; Wed, 17 Mar 1999 07:20:32 -0800 (PST) (envelope-from dan@tsolab.org) Received: from tsolab.org (ts011d14.hil-ny.concentric.net [206.173.17.26]) by tsolab.org (8.8.7/8.8.7) with ESMTP id KAA00470; Wed, 17 Mar 1999 10:20:30 -0500 (EST) (envelope-from dan@tsolab.org) Message-ID: <36EFC7F2.860738C4@tsolab.org> Date: Wed, 17 Mar 1999 10:19:14 -0500 From: Dan Tso Reply-To: dan@tsolab.org Organization: The Rockefeller University X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: > There is a way to overflow / filesystem even is quota is enabled. > > Just make many hard links (for example /bin/sh) to /tmp/ > > for ($q=0;$q<100000;$q++){ > system ("ln /bin/sh /tmp/ln$q"); > } > > Because /tmp directory usually owned by root that why quotas has no effect. > *Directory* size of /tmp can be grown up to available space on / filesystem. > > Any way to fix it? I've always thought that /tmp should be its own filesystem anyways and I generally make it so. Avoids all sorts of nasties. It seems silly to mix up the most vital system files on the same filesystem as the most volitile, damage-prone directory (/tmp). Its better to newfs /tmp regularly. As far as the other issue, the ability to fill up any public 777 directory even with quotas, perhaps the quota system should look at the 1000 bit and do something special with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 8:30:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 27F6414FAA for ; Wed, 17 Mar 1999 08:30:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA30097; Wed, 17 Mar 1999 08:29:54 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 08:29:54 -0800 (PST) From: Matthew Dillon Message-Id: <199903171629.IAA30097@apollo.backplane.com> To: "Mikhail A. Sokolov" Cc: Greg Lehey , "Mikhail A. Sokolov" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c References: <19990316223637.A31464@demos.su> <19990317125112.T429@lemis.com> <19990317151924.B3718@demos.su> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I.e. I could've agreed with that this could be really doomed directory, but no, :it's not that way, squid's allocating objects in memory, when it reaches the :limit it'd swap it to the spool (as per LRU and such rules) and then, after :it dies, I find that ~1 recursive swap file (2 disksx9gb, 256 catalogues of :16 subdirs each in 8 and 6 cache_dirs as applicable to two spools) in each :of the subdirs (second level cache) has died, - has been automagically converted :to contain some crap [by FFS?]. : :What could help is that squid is configured to use poll(), doesn't use threads, :doesn't do async (i.e. as squid undestands it, it's an option there) operations. :Mounts on the FS's are noatime, but that ain't is the culprit, ain't they? : :-- :-mishania It kinda sounds like you have two overlapping partitions. -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 Mar 17 8:50:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 0733A14C29 for ; Wed, 17 Mar 1999 08:50:28 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id TAA16123; Wed, 17 Mar 1999 19:49:46 +0300 (MSK) (envelope-from mishania) Date: Wed, 17 Mar 1999 19:49:46 +0300 From: "Mikhail A. Sokolov" To: Matthew Dillon Cc: "Mikhail A. Sokolov" , Greg Lehey , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990317194946.A16101@demos.su> References: <19990316223637.A31464@demos.su> <19990317125112.T429@lemis.com> <19990317151924.B3718@demos.su> <199903171629.IAA30097@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199903171629.IAA30097@apollo.backplane.com>; from Matthew Dillon on Wed, Mar 17, 1999 at 08:29:54AM -0800 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nope /dev/da1e 17235735 7414244 8442633 47% /mnt/arc /dev/da2e 8617355 1724705 6892650 20% /mnt/spool1 /dev/da3e 8617355 1723638 6893717 20% /mnt/spool2 On Wed, Mar 17, 1999 at 08:29:54AM -0800, Matthew Dillon wrote: # : # :What could help is that squid is configured to use poll(), doesn't use threads, # :doesn't do async (i.e. as squid undestands it, it's an option there) operations. # :Mounts on the FS's are noatime, but that ain't is the culprit, ain't they? # : # :-- # :-mishania # # It kinda sounds like you have two overlapping partitions. # # -Matt # Matthew Dillon # -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 9: 0:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (c1-64-dbn.dial-up.net [196.34.155.64]) by hub.freebsd.org (Postfix) with ESMTP id 5052515238 for ; Wed, 17 Mar 1999 09:00:00 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA00910; Wed, 17 Mar 1999 18:55:46 +0200 (SAT) From: Robert Nordier Message-Id: <199903171655.SAA00910@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171338.OAA26021@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 17, 99 02:38:17 pm" To: sos@freebsd.dk (Søren Schmidt) Date: Wed, 17 Mar 1999 18:55:44 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Incidentally, while I'm in there and thinking about it, I'd quite > > like to fix the boot code to boot from LS-120 drives at the same > > time. So if anyone has one of these, and wouldn't mind spending > > some time running a few bits of test code, I'd appreciate it. > > I have a ZIP if that can help you ?? Thanks. AFAIK, the essential difference is that the LS-120 needs to be treated (in the boot code) like a floppy, whereas the ZIP should be treated like a hard disk. But we need to accommodate both, so I'd be glad if you'd test the changes, once I've done them. > > #ifdef FORCE_FOO > > if (foo == 0) > > foo = 30; > > #endif > > Well, that breaks somewhere else, as the mount code is clever enough > to look at the name of the driver in this case "ad" which doesn't > match the specified #0 ie "wd". > I kindof tried this by having my driver put itself in both the > wd & ad majors in the table, but that doesn't work, because the mount > stuff gets confused on the root name somehow, and fails to mount > root because the names dont match... The arguments passed from the boot code to the kernel are howto, bootdev, res1, res2, res3, bootinfop where "howto" is an int containing RB_* bitflags (sys/reboot.h) which represent the boot options like -c, -v, etc. "bootdev" is an int put together using the MAKEBOOTDEV macro (sys/reboot.h) from the major#, unit#, slice#, and partition# of the boot device. "res1" through "res3" are reserved/ignored. "bootinfop" is a pointer to a bootinfo structure (machine/bootinfo.h) which contains an assortments of parameters, but none relating directly to the boot device driver (bi_bios_dev is for /boot/loader's benefit). So the *only* relevant info passed by the boot code is the major#. And if we force a change in the major# (for the sake of discussion, in the section of src/sys/i386/i386/locore.s that already has compatibility code for dealing with legacy bootblocks -- though I'm not saying that is the best place for it), we've done all we *can* do in the boot code, within the framework as it exists. So whether we add {"da", 30} to a lookup table in boot2, or use the FORCE_FOO approach, the results will be identical. > At any rate, any solution that makes it possible to boot with > a new driver without me having to call it "wd" something all > over the place is acceptable to me... Anyway, I take a look at both approaches, probably later today, and send you some diffs, hopefully relating to each way of doing things. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 9:16:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from host07.rwsystems.net (kasie.rwsystems.net [209.197.192.103]) by hub.freebsd.org (Postfix) with ESMTP id D538B15210; Wed, 17 Mar 1999 09:16:29 -0800 (PST) (envelope-from jwyatt@RWSystems.net) Received: from kasie.rwsystems.net([209.197.192.103]) (1771 bytes) by host07.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Wed, 17 Mar 1999 11:01:12 -0600 (CST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-24) Date: Wed, 17 Mar 1999 11:01:05 -0600 (CST) From: James Wyatt To: Fernando Schapachnik Cc: Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <199903171150.IAA23361@ns1.sminter.com.ar> 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, 17 Mar 1999, Fernando Schapachnik wrote: > Are you aware that, due to nature of hardlinks the only extra space is > same that for an empty file? Due to this, how many empty files do you > think it takes to eat the whole space of / ? They take *less* space than an empty file, just the directory entry. You can see how muchh by looking at the size of the '.' grow when you add one. An empty file still takes an inode, as an 'ls -li [filename]' will show. Now a small amount of anything multiplied by a large number can amount to something. If you have a small root, I can see where you could overwhelm it. It will also take longer and longer to ann the links and lookups in /tmp will take forever. Dmitry Valdov wrote: > > Because /tmp directory usually owned by root that why quotas has no effect. > > *Directory* size of /tmp can be grown up to available space on / filesystem. My favorite way is a /tmp filesystem. It solves stability problems unrelated to quotas as well. Same goes for /home if you have real users on your system (not just a server) - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 9:16:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from host07.rwsystems.net (kasie.rwsystems.net [209.197.192.103]) by hub.freebsd.org (Postfix) with ESMTP id D470615290; Wed, 17 Mar 1999 09:16:45 -0800 (PST) (envelope-from jwyatt@RWSystems.net) Received: from kasie.rwsystems.net([209.197.192.103]) (1049 bytes) by host07.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Wed, 17 Mar 1999 11:08:45 -0600 (CST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-24) Date: Wed, 17 Mar 1999 11:08:45 -0600 (CST) From: James Wyatt To: Dmitry Valdov Cc: freebsd-current@freebsd.org, freebsd-security@freebsd.org Subject: Re: disk quota overriding In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Dmitry Valdov wrote: > I think that there is only one way to fix it - it's to disable making > *hard*links to directory with mode 1777. I'm wondering: are you concerned this is possible, or that you really have a user doing it? I have kicked users off the system for less when they have trounced the machine for others. This is beginning to sound like more of the hard/symlink eruptions last week... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 9:57:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id B77BE14F06 for ; Wed, 17 Mar 1999 09:57:05 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id F350418C7; Wed, 17 Mar 1999 18:57:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id EC4814988; Wed, 17 Mar 1999 18:57:03 +0100 (CET) Date: Wed, 17 Mar 1999 18:57:02 +0100 (CET) From: Andrzej Bialecki To: Robert Nordier Cc: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171249.OAA14182@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Robert Nordier wrote: > Incidentally, while I'm in there and thinking about it, I'd quite > like to fix the boot code to boot from LS-120 drives at the same > time. So if anyone has one of these, and wouldn't mind spending > some time running a few bits of test code, I'd appreciate it. I can do that when I'm back in Poland (i.e. after Cebit). Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:21:30 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 D4F0815398; Wed, 17 Mar 1999 10:21:26 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28439; Thu, 18 Mar 1999 03:21:12 +0900 (JST) Message-ID: <36EFEE5A.DE68FF5F@newsguy.com> Date: Thu, 18 Mar 1999 03:03:06 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: > > Hi! > > I think that there is only one way to fix it - it's to disable making > *hard*links to directory with mode 1777. *IF* you are using quotas. Otherwise, it could break things for people. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:21:40 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 A39B8153A6; Wed, 17 Mar 1999 10:21:35 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28431; Thu, 18 Mar 1999 03:21:04 +0900 (JST) Message-ID: <36EFEDEC.D11C7599@newsguy.com> Date: Thu, 18 Mar 1999 03:01:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Jay Tribick Cc: Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: <19990317114932.Z21466@bofh.fastnet.co.uk> 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 Jay Tribick wrote: > > > There is a way to overflow / filesystem even is quota is enabled. > > > > Just make many hard links (for example /bin/sh) to /tmp/ > > > > for ($q=0;$q<100000;$q++){ > > system ("ln /bin/sh /tmp/ln$q"); > > } > > > > Because /tmp directory usually owned by root that why quotas has no effect. > > *Directory* size of /tmp can be grown up to available space on / filesystem. > > > > Any way to fix it? > > Haven't tested this, but are you sure it fills the filesystem up - > all a hard link is, is a file with the same inode as the > original file (correct me if I'm wrong) - therefore it > doesn't actually use any space other than that required > to store the file entry. You missed the dirty trick... :-) It's the size of +/tmp+ that fills /. The *directory* size. Because it has to *store* all these links... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:24:13 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 7461F152E0 for ; Wed, 17 Mar 1999 10:24:10 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28460; Thu, 18 Mar 1999 03:21:28 +0900 (JST) Message-ID: <36EFF139.7F2E3AD7@newsguy.com> Date: Thu, 18 Mar 1999 03:15:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: Robert Nordier , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <199903171338.OAA26021@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > Well, that breaks somewhere else, as the mount code is clever enough > to look at the name of the driver in this case "ad" which doesn't > match the specified #0 ie "wd". > I kindof tried this by having my driver put itself in both the > wd & ad majors in the table, but that doesn't work, because the mount > stuff gets confused on the root name somehow, and fails to mount > root because the names dont match... I know you most certainly could not possibly have forgotten that, but it's the kind of thing that just *must* be mentioned... /etc/fstab? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:27:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7C65A1500B for ; Wed, 17 Mar 1999 10:27:43 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28456; Thu, 18 Mar 1999 03:21:24 +0900 (JST) Message-ID: <36EFF0F0.9C57E653@newsguy.com> Date: Thu, 18 Mar 1999 03:14:08 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Poul-Henning Kamp Cc: mjacob@feral.com, "David O'Brien" , " =?iso-8859-1?Q?S=F8ren?= Schmidt" , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <41614.921678583@critter.freebsd.dk> 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 Poul-Henning Kamp wrote: > > I think you are missing the point. We will not chuck the old > wd* driver until people have crashed all MFM, RLL, ESDI and !ATA > IDE drives. > > So we WANT to be able to tell the difference... The point here is just naming. Right now, we have: wd0, ... ad0, ... da0, ... People are asking for: wd0, ... da0, ... Ie, join ad and da namespaces. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:41:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-1-dbn.dial-up.net [196.34.155.65]) by hub.freebsd.org (Postfix) with ESMTP id B351315502 for ; Wed, 17 Mar 1999 10:40:29 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA02105; Wed, 17 Mar 1999 20:35:29 +0200 (SAT) From: Robert Nordier Message-Id: <199903171835.UAA02105@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: from Andrzej Bialecki at "Mar 17, 99 06:57:02 pm" To: abial@webgiro.com (Andrzej Bialecki) Date: Wed, 17 Mar 1999 20:35:24 +0200 (SAT) Cc: sos@freebsd.dk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Wed, 17 Mar 1999, Robert Nordier wrote: > > > Incidentally, while I'm in there and thinking about it, I'd quite > > like to fix the boot code to boot from LS-120 drives at the same > > time. So if anyone has one of these, and wouldn't mind spending > > some time running a few bits of test code, I'd appreciate it. > > I can do that when I'm back in Poland (i.e. after Cebit). > > Andrzej Bialecki Thanks! I'll take you up on that. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 10:55:31 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 B6220155A6 for ; Wed, 17 Mar 1999 10:54:55 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA08100; Wed, 17 Mar 1999 10:43:22 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdAF8098; Wed Mar 17 18:43:18 1999 Message-ID: <36EFF7C2.41C67EA6@whistle.com> Date: Wed, 17 Mar 1999 10:43:14 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: sthaug@nethelp.no Cc: obrien@NUXI.com, sos@freebsd.dk, current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? References: <19990317033240.A36782@relay.nuxi.com> <29382.921672594@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > Amen. > > > > Does this mean ata disks won't come under CAM/da ? > > If not, can we PLEASE rename SCSI disks back to ``sd''? > > Agreed. I see no justification for the sd -> da change if > the ATA disks won't (eventually) be included. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11: 1: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 898F714BF1 for ; Wed, 17 Mar 1999 11:00:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA00771; Wed, 17 Mar 1999 20:00:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA43238; Wed, 17 Mar 1999 20:00:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: mjacob@feral.com, "David O'Brien" , " =?iso-8859-1?Q?S=F8ren?= Schmidt" , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Thu, 18 Mar 1999 03:14:08 +0900." <36EFF0F0.9C57E653@newsguy.com> Date: Wed, 17 Mar 1999 20:00:23 +0100 Message-ID: <43236.921697223@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36EFF0F0.9C57E653@newsguy.com>, "Daniel C. Sobral" writes: >Poul-Henning Kamp wrote: >> >> I think you are missing the point. We will not chuck the old >> wd* driver until people have crashed all MFM, RLL, ESDI and !ATA >> IDE drives. >> >> So we WANT to be able to tell the difference... > >The point here is just naming. Right now, we have: > >wd0, ... >ad0, ... >da0, ... > >People are asking for: > >wd0, ... >da0, ... > >Ie, join ad and da namespaces. If you want to join anything, go directly to "disk%d" instead. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11:13:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0D49B14D10 for ; Wed, 17 Mar 1999 11:13:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA26701; Wed, 17 Mar 1999 20:13:01 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171913.UAA26701@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <36EFF139.7F2E3AD7@newsguy.com> from "Daniel C. Sobral" at "Mar 18, 1999 3:15:21 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 17 Mar 1999 20:13:01 +0100 (CET) Cc: rnordier@nordier.com, 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 Daniel C. Sobral wrote: > "Søren Schmidt" wrote: > > > > Well, that breaks somewhere else, as the mount code is clever enough > > to look at the name of the driver in this case "ad" which doesn't > > match the specified #0 ie "wd". > > I kindof tried this by having my driver put itself in both the > > wd & ad majors in the table, but that doesn't work, because the mount > > stuff gets confused on the root name somehow, and fails to mount > > root because the names dont match... > > I know you most certainly could not possibly have forgotten that, > but it's the kind of thing that just *must* be mentioned... > /etc/fstab? Nope thats not it, been there too :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11:15:58 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 9C9BD15497 for ; Wed, 17 Mar 1999 11:15:55 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Mar 99 19:12:44 +0000 (GMT) To: Michael Richards <026809r@dragon.acadiau.ca> Cc: freebsd-current@freebsd.org Subject: Re: disk quota overriding In-reply-to: Your message of "Wed, 17 Mar 1999 10:58:16 -0400." X-Request-Do: Date: Wed, 17 Mar 1999 19:12:43 +0000 From: David Malone Message-ID: <9903171912.aa21610@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We all know that there are oodles of security problems associated with > file giveaways. As I recall, all the texts I have ever read on the subject > say that unless there is a very good reason to allow giveaways, they > should be disabled. You can play games with quotas anyway, because you are alowd to make hard links to files you don't own. I was considering writing some code to restrict the ability to make hardlinks to files to root and the file's owner. I guess it could either be a global sysctl or a per filesystem mount option. Would there be any interest in this it I put it together? Should it be a mount option or a sysctl? Would anyone consider commiting it if I did write it? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11:27: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A81C115260 for ; Wed, 17 Mar 1999 11:26:51 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA01399; Thu, 18 Mar 1999 04:24:02 +0900 (JST) Message-ID: <36F000B5.E87D2BF3@newsguy.com> Date: Thu, 18 Mar 1999 04:21:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <199903171913.UAA26701@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > It seems Daniel C. Sobral wrote: > > "S=F8ren Schmidt" wrote: > > > > > > Well, that breaks somewhere else, as the mount code is clever enoug= h > > > to look at the name of the driver in this case "ad" which doesn't > > > match the specified #0 ie "wd". > > > I kindof tried this by having my driver put itself in both the > > > wd & ad majors in the table, but that doesn't work, because the mou= nt > > > stuff gets confused on the root name somehow, and fails to mount > > > root because the names dont match... > > > > I know you most certainly could not possibly have forgotten that, > > but it's the kind of thing that just *must* be mentioned... > > /etc/fstab? > = > Nope thats not it, been there too :) Ok, I have a clue... bootdev can be different from rootdev. I don't know where this makes a difference, but it makes... :-) Meanwhile, edit sys/boot/i386/libi386/biosdisk.c and change WDMAJOR to 30. If that doesn't help, the problem must be elsewhere. Also, make sure you don't have any root_disk_unit or num_ide_disks set. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11:44: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0DC241556C for ; Wed, 17 Mar 1999 11:44:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA39152; Wed, 17 Mar 1999 11:39:18 -0800 (PST) (envelope-from obrien) Date: Wed, 17 Mar 1999 11:39:18 -0800 From: "David O'Brien" To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990317113918.B39105@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <36EFF0F0.9C57E653@newsguy.com> <43236.921697223@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <43236.921697223@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Mar 17, 1999 at 08:00:23PM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >People are asking for: > > > >wd0, ... > >da0, ... > > > >Ie, join ad and da namespaces. > > If you want to join anything, go directly to "disk%d" instead. But that is not the "deal" that was presented to us when we had to endure the gratuitous sd->da name change. The whole justification was a single device name for disks (and what ever else is direct access). -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 11:46: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 18E4B1540F for ; Wed, 17 Mar 1999 11:45:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id UAA01021; Wed, 17 Mar 1999 20:45:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id UAA43437; Wed, 17 Mar 1999 20:45:32 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Wed, 17 Mar 1999 11:39:18 PST." <19990317113918.B39105@relay.nuxi.com> Date: Wed, 17 Mar 1999 20:45:32 +0100 Message-ID: <43435.921699932@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990317113918.B39105@relay.nuxi.com>, "David O'Brien" writes: >> >People are asking for: >> > >> >wd0, ... >> >da0, ... >> > >> >Ie, join ad and da namespaces. >> >> If you want to join anything, go directly to "disk%d" instead. > >But that is not the "deal" that was presented to us when we had to endure >the gratuitous sd->da name change. The whole justification was a single >device name for disks (and what ever else is direct access). The fact that Justin promised that "ATA ***Could***" use CAM, didn't seem to imply to me that it would, unless somebody wrote code for it. That didn't happen. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 12:15:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (Postfix) with ESMTP id 2E925152B7; Wed, 17 Mar 1999 12:15:37 -0800 (PST) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id PAA06127; Wed, 17 Mar 1999 15:15:11 -0500 (EST) Date: Wed, 17 Mar 1999 15:15:10 -0500 (EST) From: To: Ladavac Marino Cc: "'Dmitry Valdov'" , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: RE: disk quota overriding In-Reply-To: <97A8CA5BF490D211A94F0000F6C2E55D097564@s-lmh-wi-900.corpnet.at> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Ladavac Marino wrote: > chown root:wheel big_file AFAIK, only root can 'give ownership away' on most modern Unix'. Later, -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 12:36:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3AB6E14C9C for ; Wed, 17 Mar 1999 12:36:16 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA07013; Wed, 17 Mar 1999 15:35:56 -0500 (EST) (envelope-from wollman) Date: Wed, 17 Mar 1999 15:35:56 -0500 (EST) From: Garrett Wollman Message-Id: <199903172035.PAA07013@khavrinen.lcs.mit.edu> To: obrien@NUXI.com Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317113918.B39105@relay.nuxi.com> References: <36EFF0F0.9C57E653@newsguy.com> <43236.921697223@critter.freebsd.dk> <19990317113918.B39105@relay.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > But that is not the "deal" that was presented to us when we had to endure > the gratuitous sd->da name change. The whole justification was a single > device name for disks (and what ever else is direct access). No, that was not the justification for the name change. The justification (Justinfication?) was that in SCSI terminology, these things -- not all of which are disks -- are called ``direct access'' devices. Similarly, `sa' is ``sequential access''. ATAPI had nothing whatsoever to do with 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 From owner-freebsd-current Wed Mar 17 12:48:11 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 76FCC14C9C for ; Wed, 17 Mar 1999 12:48:07 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id VAA26937; Wed, 17 Mar 1999 21:47:44 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903172047.VAA26937@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317113918.B39105@relay.nuxi.com> from "David O'Brien" at "Mar 17, 1999 11:39:18 am" To: obrien@NUXI.com Date: Wed, 17 Mar 1999 21:47:43 +0100 (CET) Cc: phk@critter.freebsd.dk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David O'Brien wrote: > > >People are asking for: > > > > > >wd0, ... > > >da0, ... > > > > > >Ie, join ad and da namespaces. > > > > If you want to join anything, go directly to "disk%d" instead. > > But that is not the "deal" that was presented to us when we had to endure > the gratuitous sd->da name change. The whole justification was a single > device name for disks (and what ever else is direct access). Yes on the SCSI busses, nothing more nothing less.... Direct Access is the SCSI term for, among others, disks... It was _mentioned_ that ATAPI devices was semilar to SCSI devices and that it _could_ be done through CAM, there was NO promise or anything back when, and there still isn't. ATA disks which this is about, is pretty far way from the CAM/SCSI world, but again a translation layer could be added inbetween. But given the situation that most ATA/ATAPI systems are used in, I belive that our user base will be more interested in max performance instead.. So the sd -> da etc namechange has nothing to do with what I'm about to do. I simply ask for the support for booting from any BDEV, and that has not been dealt with in the new boot stuff. Thats what I'm complaining about, dont tell me it wasn't done because all disk like device should be named "da", thats too naive to be belived :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 12:57: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id CE99714D38 for ; Wed, 17 Mar 1999 12:56:06 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA01481; Wed, 17 Mar 1999 22:50:29 +0200 (SAT) From: Robert Nordier Message-Id: <199903172050.WAA01481@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <36F000B5.E87D2BF3@newsguy.com> from "Daniel C. Sobral" at "Mar 18, 99 04:21:25 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 17 Mar 1999 22:50:27 +0200 (SAT) Cc: sos@freebsd.dk, rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Daniel C. Sobral wrote: > "Søren Schmidt" wrote: > > > I know you most certainly could not possibly have forgotten that, > > > but it's the kind of thing that just *must* be mentioned... > > > /etc/fstab? > > > > Nope thats not it, been there too :) > > Ok, I have a clue... bootdev can be different from rootdev. I don't > know where this makes a difference, but it makes... :-) In loader, you can have a default device (currdev), but load from a different device (loaddev) and pass a third device to the kernel (rootdev). In the simple case of booting from ad0, all the default settings would be correct, though. > Also, make sure you don't have any root_disk_unit or num_ide_disks > set. A num_ide_disks setting is used only where the major# indicates a SCSI device, so it wouldn't affect things. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 13: 1:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D2E94152F0 for ; Wed, 17 Mar 1999 13:01:32 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id NAA39652; Wed, 17 Mar 1999 13:01:07 -0800 (PST) (envelope-from obrien) Date: Wed, 17 Mar 1999 13:01:07 -0800 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990317130107.D39245@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <36EFF0F0.9C57E653@newsguy.com> <43236.921697223@critter.freebsd.dk> <19990317113918.B39105@relay.nuxi.com> <199903172035.PAA07013@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903172035.PAA07013@khavrinen.lcs.mit.edu>; from Garrett Wollman on Wed, Mar 17, 1999 at 03:35:56PM -0500 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No, that was not the justification for the name change. The > justification (Justinfication?) was that in SCSI terminology, these > things -- not all of which are disks -- are called ``direct access'' > devices. Similarly, `sa' is ``sequential access''. Then why do we still have ``cd''? Isn't a CDROM a direct access device? Last time I used my, I didn't have to read sector 1 before reading sector 9893. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 14:12:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from unix.tfs.net (as2-p80.tfs.net [139.146.205.80]) by hub.freebsd.org (Postfix) with ESMTP id 313271574B for ; Wed, 17 Mar 1999 14:12:30 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.3/8.8.5) id QAA00397 for freebsd-current@freebsd.org; Wed, 17 Mar 1999 16:12:10 -0600 (CST) From: Jim Bryant Message-Id: <199903172212.QAA00397@unix.tfs.net> Subject: spontaneous reboot during `mt erase` To: freebsd-current@freebsd.org Date: Wed, 17 Mar 1999 16:12:08 -0600 (CST) Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running: FreeBSD argus 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Sun Mar 14 18:20:15 CST 1999 jbryant@argus:/usr/src/sys/compile/ARGUS i386 I popped in a 60m tape and did an mt erase. After a couple of minutes, I had a spontaneous reboot. I also noticed that things had really slowed down right before the reboot [3 second delay to toggle the NumLock light]. I didn't catchy the exact time, but am willing to bet that I was in the middle of a popclient run when it happened, as my mailbox was corrupted, and I had to edit the /var/mail spoolfile, and re-get my mail which had the same message on the isp server [meaning that the transfer of the message never finished]. I am running softupdates. Oh yeah, I was running Netscape at the time, but the slowdown was definitely caused by the `mt erase`. This is about all the info I have at the moment. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 14:20:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id E0B371541E for ; Wed, 17 Mar 1999 14:20:35 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id WAA18256 for FreeBSD.ORG!freebsd-current; Wed, 17 Mar 1999 22:20:16 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 17 Mar 1999 22:11:59 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199903171300.GAA01545@ice.cold.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 17 Mar 1999 22:11:56 +0000 To: freebsd-current@FreeBSD.ORG From: Bob Bishop Subject: Re: ERRATA NOTICE: FreeBSD 3.1-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:00 am -0700 17/3/99, freebsd-errata-update@roguetrader.com wrote: >****************************************************************** >** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE ** >****************************************************************** >[etc] Er, why is this sent to -current? I would have thought this is -announce material. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 14:36: 3 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 03CE915222 for ; Wed, 17 Mar 1999 14:35:47 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA23492; Thu, 18 Mar 1999 09:05:27 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA72433; Thu, 18 Mar 1999 09:05:26 +1030 (CST) Message-ID: <19990318090526.I429@lemis.com> Date: Thu, 18 Mar 1999 09:05:26 +1030 From: Greg Lehey To: vallo@matti.ee Cc: freebsd-current@freebsd.org Subject: Re: Crash while newfs'ing innocent vinum volume on fresh system. References: <19990317142107.A78437@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.93.2i In-Reply-To: <19990317142107.A78437@matti.ee>; from Vallo Kallaste on Wed, Mar 17, 1999 at 02:21:07PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 17 March 1999 at 14:21:07 +0200, Vallo Kallaste wrote: > Newfs -n1 -d0 -v /dev/vinum/rsvol .... two lines newfs output and > crash: > > Script started on Wed Mar 17 13:24:45 1999 > sh-2.02# gdb -k ker=07nel.gdb vmcore.0 > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > IdlePTD 2760704 > initial pcb at 23af94 > panicstr: from debugger > panic messages: > --- > Fatal trap 12: page fault while in kernel mode Since I was looking at these dumps, I find it rather superfluous to copy -CURRENT on this message. I'll take a look and see what's going on. I'm particularly puzzled about the missing stack frames; did you remove the .gdbinit file? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 15: 1:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 5E266151A1 for ; Wed, 17 Mar 1999 15:01:19 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: (qmail 3696 invoked from network); 17 Mar 1999 23:01:00 -0000 Received: from nathan.enteract.com (dscheidt@207.229.143.6) by thor.enteract.com with SMTP; 17 Mar 1999 23:01:00 -0000 Date: Wed, 17 Mar 1999 17:01:00 -0600 (CST) From: David Scheidt To: Jon Hamilton Cc: Ladavac Marino , 'Dmitry Valdov' , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <19990317144148.12DFF62@woodstock.monkey.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 Wed, 17 Mar 1999, Jon Hamilton wrote: :Under HP-UX 9.x, the behavior you describe was the default, and it :was changable by altering a kernel config parameter and relinking the :kernel. The same tunable is available under 10.x, but I'm less certain :what the default behavior is there. Whether quotas are enabled or not :does not affect the behavior, only the kernel tunable parameter. This is still the default in 10.20. At least, all of the machines around here are that way. It has some uses on test and lab type machines, as it makes some tasks not have to involve root. As default behavior for a production machine, it is damn silly. David Scheidt : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 15:36: 7 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 DE94C1532C for ; Wed, 17 Mar 1999 15:35:58 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA01654 for current@FreeBSD.ORG; Thu, 18 Mar 1999 00:35:35 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F36658848; Thu, 18 Mar 1999 00:25:57 +0100 (CET) Date: Thu, 18 Mar 1999 00:25:57 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990318002557.A26117@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <19990316223637.A31464@demos.su> <19990317125112.T429@lemis.com> <19990317151924.B3718@demos.su> <199903171629.IAA30097@apollo.backplane.com> <19990317194946.A16101@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990317194946.A16101@demos.su>; from Mikhail A. Sokolov on Wed, Mar 17, 1999 at 07:49:46PM +0300 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mikhail A. Sokolov: > nope > > /dev/da1e 17235735 7414244 8442633 47% /mnt/arc > /dev/da2e 8617355 1724705 6892650 20% /mnt/spool1 > /dev/da3e 8617355 1723638 6893717 20% /mnt/spool2 disklabel output is what you want to send us, df is not enough :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 15:36:16 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 327D31537C for ; Wed, 17 Mar 1999 15:36:08 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA01655 for current@FreeBSD.ORG; Thu, 18 Mar 1999 00:35:49 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F1B5D8848; Thu, 18 Mar 1999 00:30:58 +0100 (CET) Date: Thu, 18 Mar 1999 00:30:58 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990318003058.B26117@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199903162322.BAA07920@ceia.nordier.com> <199903170805.JAA25289@freebsd.dk> <19990317033240.A36782@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <19990317033240.A36782@relay.nuxi.com>; from David E . O'Brien on Wed, Mar 17, 1999 at 03:32:40AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to David E . O'Brien: > If not, can we PLEASE rename SCSI disks back to ``sd''? I'm tempted to agree. Many people I know who are upgrading to 3.* are somewhat pissed off by the renaming, even if it is in the release notes. They don't see any good reason for it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 17: 1:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from aurora.galaxia.com (trantor.galaxia.com [209.213.94.97]) by hub.freebsd.org (Postfix) with ESMTP id D20C9152A6; Wed, 17 Mar 1999 17:01:33 -0800 (PST) (envelope-from dave@galaxia.com) Received: from localhost (dave@localhost) by aurora.galaxia.com (8.8.8/8.8.7) with ESMTP id UAA11484; Wed, 17 Mar 1999 20:00:17 -0500 (EST) (envelope-from dave@galaxia.com) Date: Wed, 17 Mar 1999 20:00:17 -0500 (EST) From: "David H. Brierley" To: James Wyatt Cc: Fernando Schapachnik , Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, James Wyatt wrote: > Now a small amount of anything multiplied by a large number can amount to > something. If you have a small root, I can see where you could overwhelm > it. It will also take longer and longer to ann the links and lookups in > /tmp will take forever. On any machine which allows general users to log in, I strongly recommend making separate file systems for /, /usr, /tmp, and /home, plus any other areas you expect to grow large. Keeping / and /usr separate prevents people from playing "ln" tricks to gain root access. Keeping /tmp separate helps prevent /tmp from breaking your system when it fills up (note that I say "when" and not "if"). Keeping the users on a separate partition helps keep them under control because you can do things like mount the partition with the "nosuid" attribute. The only time I ever create a machine with a single large partition is when I am creating a dedicated server machine that will only allow logins from trusted staff members. -- David H. Brierley dave@galaxia.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 17: 9:17 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 ADC591536B for ; Wed, 17 Mar 1999 17:09:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA34057; Wed, 17 Mar 1999 17:08:53 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 17:08:53 -0800 (PST) From: Matthew Dillon Message-Id: <199903180108.RAA34057@apollo.backplane.com> To: Nick Hibma Cc: FreeBSD current mailing list Subject: Re: panic occurred: vm_fault References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The fault seems to be reproducable. : : mount /cdrom : find /cdrom -type f -exec cat \{\} >/dev/null \; -ls : :and pop it goes. Same stack trace. We could do a try-this-game this weekend (up to :then I'm covered in work) if that would be helpfull. : :Let me know what information you need. : :Nick Doesn't happen to me, but I'll try a couple more CD's. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 17:11:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D906153CA for ; Wed, 17 Mar 1999 17:10:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id SAA35985; Wed, 17 Mar 1999 18:10:25 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903180110.SAA35985@panzer.plutotech.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990318003058.B26117@keltia.freenix.fr> from Ollivier Robert at "Mar 18, 1999 0:30:58 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 17 Mar 1999 18:10:25 -0700 (MST) Cc: 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 Ollivier Robert wrote... > According to David E . O'Brien: > > If not, can we PLEASE rename SCSI disks back to ``sd''? > > I'm tempted to agree. Many people I know who are upgrading to 3.* are > somewhat pissed off by the renaming, even if it is in the release > notes. They don't see any good reason for it... Do we have to go over this again and again? It'll be worse if we change back. And it's not like anyone had to upgrade their fstab -- all of the sd devices still work, since the major number is the same. So there's not a lot of room for complaint here. (Yeah, I'm sure someone will start squawking about it right about now.) So, just let it rest. There are lots of more pressing things to worry about. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 17:11:27 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 D48C0153E1 for ; Wed, 17 Mar 1999 17:11:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA34092; Wed, 17 Mar 1999 17:11:00 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 17:11:00 -0800 (PST) From: Matthew Dillon Message-Id: <199903180111.RAA34092@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> <19990316213355.A4561@enst.fr> <199903162052.MAA12300@apollo.backplane.com> <19990316221057.A382@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: :> Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't :> fry? If so, then we have a bug in AMD somewhere. : :I tried the cp several times again on a regular NFS mount, to make :sure, and no, it doesn't seem to panic. So yes, that seems to be :AMD-related. Can't it be in the vfs layer though? :-- :Pierre Beyssac pb@enst.fr It's probably AMD. I'm not really up on how AMD works... hasn't someone done some work on it recently to fix other breakages? Maybe they could look at this panic. -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 Mar 17 18:16:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A8D2614E4C for ; Wed, 17 Mar 1999 18:16:38 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA13070; Wed, 17 Mar 1999 21:14:44 -0500 (EST) Date: Wed, 17 Mar 1999 21:14:43 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: Robert Nordier , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903171338.OAA26021@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, S=F8ren Schmidt wrote: > It seems Robert Nordier wrote: > > OK, I'll add it to the bootblocks. > >=20 > > Incidentally, while I'm in there and thinking about it, I'd quite > > like to fix the boot code to boot from LS-120 drives at the same > > time. So if anyone has one of these, and wouldn't mind spending > > some time running a few bits of test code, I'd appreciate it. >=20 > I have a ZIP if that can help you ?? >=20 > > > > However, I'd *still* expect it to pass a major# of 0 rather than > > > > 30. Why? Because a 2.0 kernel knows only 0. And if a 5.0 kernel > > > > knows only 30, it is -- at least -- in a position to know what > > > > 0 meant, and simply substitute one for the other (under the > > > > influence of a kernel configuration option, if necessary). > > >=20 > > > Hmm, wd should give 0 and ad should give 30, no AI please :) > >=20 > > I wasn't actually thinking at all along the lines of "smart" code > > at all: > >=20 > > #ifdef FORCE_FOO > > =09if (foo =3D=3D 0) > > =09 foo =3D 30; > > #endif >=20 > Well, that breaks somewhere else, as the mount code is clever enough > to look at the name of the driver in this case "ad" which doesn't=20 > match the specified #0 ie "wd". > I kindof tried this by having my driver put itself in both the > wd & ad majors in the table, but that doesn't work, because the mount > stuff gets confused on the root name somehow, and fails to mount > root because the names dont match... >=20 > > AFAICS, adopting the separate "wd" and "ad" route entails the > > following: > >=20 > > Update your bootblocks. > > Add a /boot.config statement like "0:ad(0,a)" to make use > > of the driver the default. > > Failure to boot if you inadvertently specify wd out of habit, > > or if you specify ad when booting an earlier system. > >=20 > > So we're introducing three points with good potential for failure. >=20 > Well, what else can we do as long as we potentially need both > drivers in the kernel. I'm pretty sure that if I kill of wd.c > et all, there will be screams of bloody murder again... > been there done that :) Well, since the new ATA doesn't work with my LS-120 yet nor support DMA... ;) I want to see the LS-120 working, so where would I send it to if you wer= e to work on its driver? :) >=20 > > In contrast, the kernel configuration route requires commenting > > or uncommenting a single statement. >=20 > But that doesn't work, at least as the mount code behaves now. >=20 > At any rate, any solution that makes it possible to boot with=20 > a new driver without me having to call it "wd" something all=20 > over the place is acceptable to me... >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 Brian Feldman=09=09=09=09=09 _ __ ___ ___ ___ =20 green@unixhelp.org=09=09=09 _ __ ___ | _ ) __| \=20 =09 http://www.freebsd.org/=09 _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve!=09 _ __ ___ ____ _____ |___/___/___/=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 18:33:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E869714DAD for ; Wed, 17 Mar 1999 18:33:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA35179; Wed, 17 Mar 1999 18:33:10 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 18:33:10 -0800 (PST) From: Matthew Dillon Message-Id: <199903180233.SAA35179@apollo.backplane.com> To: Matthew Dillon Cc: Nick Hibma , FreeBSD current mailing list Subject: Re: panic occurred: vm_fault References: <199903180108.RAA34057@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: mount /cdrom :: find /cdrom -type f -exec cat \{\} >/dev/null \; -ls :: ::and pop it goes. Same stack trace. We could do a try-this-game this weekend (up to ::then I'm covered in work) if that would be helpfull. :: ::Let me know what information you need. :: ::Nick : : Doesn't happen to me, but I'll try a couple more CD's. : : -Matt Ok, I got a panic: mount /cdrom find /cdrom -type f -exec cat \{\} >/dev/null \; -ls This is with -current. Will the ATAPI driver writer please step forward :-) panic: vm_fault: fault on nofault entry, addr: c1d41000 db> trace Debugger... panic vm_fault trap_pfault trap calltrap --- trap atapi_io atapi_intr wdintr(1,80000000,10,10,0) Xresume15() --- interrupt default_halt() -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 Mar 17 19: 1:55 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 1CE9215264 for ; Wed, 17 Mar 1999 19:01:48 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA24755; Thu, 18 Mar 1999 13:31:25 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA76509; Thu, 18 Mar 1999 13:31:24 +1030 (CST) Message-ID: <19990318133123.S429@lemis.com> Date: Thu, 18 Mar 1999 13:31:23 +1030 From: Greg Lehey To: vallo@matti.ee Cc: freebsd-current@freebsd.org Subject: Help! (was: Crash while newfs'ing innocent vinum volume on fresh system.) References: <19990317142107.A78437@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.93.2i In-Reply-To: <19990317142107.A78437@matti.ee>; from Vallo Kallaste on Wed, Mar 17, 1999 at 02:21:07PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 17 March 1999 at 14:21:07 +0200, Vallo Kallaste wrote: > I have reinstalled fresh 3.1-RELEASE to the machine in question, > before swapped out two memory DIMM's to the single new 32MB one, just > to be sure it's not some kind of memory error. This is definitely not a memory error. I wish I knew what it was, though. In my last message I said it wasn't appropriate to copy -CURRENT, but maybe it is: I just can't figure out how this is happening. > Then I downloaded your newest archive for vinum installation: > vinum-4.0-CURRENT.tar.gz... > Copied the same kernel configuration file as usual to the right place > from backup. Made some minor changes to kernel configuration, removed > DMA support for ata disks, I don't trust the support very much yet. > Made new debug kernel, copied to /var/crash, stripped the original > with -g and installed. Reboot. For just testing Vinum, you don't need to build a kernel. > Newfs -n1 -d0 -v /dev/vinum/rsvol .... two lines newfs output and > crash: > > Script started on Wed Mar 17 13:24:45 1999 > sh-2.02# gdb -k ker=07nel.gdb vmcore.0 > (kgdb) add-symbol-file /modules/vinum.ko 0x00005ba8+ > A syntax error in expression, near `'. You shouldn't need to do this any more. The .gdbinit file I put in this directory did it for you. When removing dumps, don't remove the =2Egdbinit. > #9 0xf01eadba in trap (frame=3D{tf_es =3D -203751408, tf_ds =3D -2037514= 08, > tf_edi =3D -559038242, tf_esi =3D -2147483648, tf_ebp =3D -20371514= 4, > tf_isp =3D -203715180, tf_ebx =3D -258066920, tf_edx =3D 16384, tf_= ecx =3D 14, > tf_eax =3D -16162, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -2576= 39372, > tf_cs =3D 8, tf_eflags =3D 66182, tf_esp =3D -257699840, tf_ss =3D = -245981592}) > at ../../i386/i386/trap.c:437 > #10 0xf0a4bc34 in ?? () > #11 0xf0a4bae1 in ?? () > #12 0xf0a4b8b6 in ?? () > #13 0xf012ffec in physio (strategy=3D0xf0a4b808 , bp=3D0x0, > dev=3D23296, rw=3D0, minp=3D0xf01300dc , uio=3D0xf3db8f34) > at ../../kern/kern_physio.c:113 > #14 0xf0a4c97c in ?? () > #15 0xf0162f2f in spec_write (ap=3D0xf3db8ef8) > at ../../miscfs/specfs/spec_vnops.c:355 These are the critical frames. With syumbols, they read: #9 0xf01eadba in trap (frame=3D{tf_es =3D -203751408, tf_ds =3D -203751408= , tf_edi =3D -559038242, tf_esi =3D -2147483648, tf_ebp =3D -203715144, tf_isp =3D -203715180, tf_ebx =3D -258066920, = tf_edx =3D 16384, tf_ecx =3D 14, tf_eax =3D -16162, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -257639372, tf_cs =3D 8, t= f_eflags =3D 66182, tf_esp =3D -257699840, tf_ss =3D -245981592}) at ../../i386/i386/trap.c:437 #10 0xf0a4bc34 in launch_requests (rq=3D0xf0a3cb00, reviveok=3D0) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:370 #11 0xf0a4bae1 in vinumstart (bp=3D0xf1569e68, reviveok=3D0) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:300 #12 0xf0a4b8b6 in vinumstrategy (bp=3D0xf1569e68) at /usr/src/sys/modules/v= inum/../../dev/vinum/vinumrequest.c:151 #13 0xf012ffec in physio (strategy=3D0xf0a4b808 , bp=3D0x0, = dev=3D23296, rw=3D0, minp=3D0xf01300dc , uio=3D0xf3db8f34) at ../../kern/kern_physio.c:113 #14 0xf0a4c97c in vinumwrite (dev=3D23296, uio=3D0xf3db8f34, ioflag=3D1) at /usr/src/sys/modules/vinum/../../dev/vinum/vinumrequest.c:995 #15 0xf0162f2f in spec_write (ap=3D0xf3db8ef8) at ../../miscfs/specfs/spec_= vnops.c:355 This is a problem I've seen before, but it completely baffles me. The request passed to launch_requests (frame 10) has been deallocated. Some of the debug code I put in caught it: (kgdb) p freeinfo[7] $2 =3D { time =3D { tv_sec =3D 921669613,=20 tv_usec =3D 289712 },=20 seq =3D 24,=20 size =3D 36,=20 line =3D 174,=20 address =3D 0xf0a3cb00 "=DE=C0=AD=DEh\235\"=F0=DE=C0=AD=DE=C0=C8=A3=F0=DE= =C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0= =AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE=DE=C0=AD=DE",=20 file =3D "vinuminterrupt.c" } This was called from freerq, which frees the complete request. freerq is called from only four places: one on completion of the request (which in this case is just about to be started), one if the request is aborted (which also sets bp->b_error, which is not set here), once in a read context (which is not applicable here: it's a write), and once just before the call to launch_requests in frame 11: 292 if ((status > REQUEST_RECOVERED) /* can'= t satisfy it */ 293 ||(bp->b_flags & B_DONE)) { /* XXX = shouldn't get this without bad status */ 294 if (status =3D=3D REQUEST_DOWN) { /* = not enough subdisks */ 295 bp->b_error =3D EIO; /* I/= O error */ 296 bp->b_flags |=3D B_ERROR; 297 } 298 if ((bp->b_flags & B_DONE) =3D=3D 0) 299 biodone(bp); 300 freerq(rq); 301 return -1; 302 } 303 return launch_requests(rq, reviveok); /* now = start the requests if we can */ [the line numbers are off by 3, but the code here is unchanged]. If we go through this code, we will also return. There's something to suggest that this code was executed, since the buffer was also marked done (at line 298/300). I checked the assembly code and confirmed that it was, in fact, correct. So where is this coming from? I'm completely baffled. It doesn't happen to most people, though I have had reports of one or two other cases. About the only clue is that the problem didn't occur when I removed the debug memory allocator, but I don't know whether it went away or into hiding. I'd really like to find out what's going on here. Here's what I've done: I've built a version of vinum on your site with even more debug code, and would like you to run it again. It'll crash, but hopefully the dump will give me more information. If it's OK for me to run the tests, tell me so and I'll do it during the night. When you run this time, do the following: # vinum vinum -> debug 104 vinum -> setdaemon 1 Thanks for your patience. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 19:26:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 27729152DA for ; Wed, 17 Mar 1999 19:26:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id TAA41475 for current@FreeBSD.ORG; Wed, 17 Mar 1999 19:25:45 -0800 (PST) (envelope-from obrien) Date: Wed, 17 Mar 1999 19:25:45 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990317192545.A41444@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990318003058.B26117@keltia.freenix.fr> <199903180110.SAA35985@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903180110.SAA35985@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Mar 17, 1999 at 06:10:25PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And it's not like anyone had to upgrade their fstab -- all of the sd > devices still work, since the major number is the same. So there's not > a lot of room for complaint here. Only if sysinstall goes back to creating the /dev/sd* devices and matching fstab w/``sd''. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 20:11:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 78A6414C29 for ; Wed, 17 Mar 1999 20:11:33 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id OAA04291; Thu, 18 Mar 1999 14:42:19 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA01868; Thu, 18 Mar 1999 14:40:58 +0930 Date: Thu, 18 Mar 1999 14:40:57 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Matthew Dillon Cc: Nick Hibma , FreeBSD current mailing list Subject: Re: panic occurred: vm_fault In-Reply-To: <199903180108.RAA34057@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 Wed, 17 Mar 1999, Matthew Dillon wrote: > : mount /cdrom > : find /cdrom -type f -exec cat \{\} >/dev/null \; -ls > : > :and pop it goes. Same stack trace. We could do a try-this-game this weekend (up to > :then I'm covered in work) if that would be helpfull. > : > :Let me know what information you need. > : > :Nick > > Doesn't happen to me, but I'll try a couple more CD's. This panicked my machine with the first CD I tried it on - I can help with the testing if required. It was my Windows95 CD which caused it. Hmm :-) Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 17 20:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A821516C for ; Wed, 17 Mar 1999 20:40:40 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id VAA36978; Wed, 17 Mar 1999 21:40:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903180440.VAA36978@panzer.plutotech.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317192545.A41444@relay.nuxi.com> from "David O'Brien" at "Mar 17, 1999 7:25:45 pm" To: obrien@NUXI.com Date: Wed, 17 Mar 1999 21:40:07 -0700 (MST) Cc: 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 David O'Brien wrote... > > And it's not like anyone had to upgrade their fstab -- all of the sd > > devices still work, since the major number is the same. So there's not > > a lot of room for complaint here. > > Only if sysinstall goes back to creating the /dev/sd* devices and > matching fstab w/``sd''. What does that have to do anything? If sysinstall is doing the work, the user doesn't have to. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 0:36:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id 18C121535F for ; Thu, 18 Mar 1999 00:35:42 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Thu, 18 Mar 1999 09:37:47 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Ollivier Robert' , current@FreeBSD.ORG Subject: RE: repeated ufs_dirbad() panics on 4.0-c Date: Thu, 18 Mar 1999 09:32:42 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Ollivier Robert [SMTP:roberto@keltia.freenix.fr] > Sent: Thursday, March 18, 1999 12:26 AM > To: current@FreeBSD.ORG > Subject: Re: repeated ufs_dirbad() panics on 4.0-c > > According to Mikhail A. Sokolov: > > nope > > > > /dev/da1e 17235735 7414244 8442633 47% /mnt/arc > > /dev/da2e 8617355 1724705 6892650 20% > /mnt/spool1 > > /dev/da3e 8617355 1723638 6893717 20% > /mnt/spool2 > > disklabel output is what you want to send us, df is not enough :-) > [ML] In his case it is, because if you take a very careful look, you will see that he's using the e compatibility partition on three separate disks :) So, it's probably not overlapping, but the compatibility that may cause problems. /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 0:36:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles193.castles.com [208.214.165.193]) by hub.freebsd.org (Postfix) with ESMTP id B03AC1538F for ; Thu, 18 Mar 1999 00:36:42 -0800 (PST) (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 AAA01143; Thu, 18 Mar 1999 00:29:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903180829.AAA01143@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: S ren Schmidt Cc: rnordier@nordier.com (Robert Nordier), current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Wed, 17 Mar 1999 09:05:00 +0100." <199903170805.JAA25289@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 18 Mar 1999 00:29:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Robert Nordier wrote: > > If the problem is the bootblocks, why not send a message to Robert > > Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And > > say, "This is what I want to do, what are we going to do about it?" > > or something similar? > = > OK, easy enough, this is what I want to do: > = > Boot from an ata disk on major# 30, device name "ad", plain and simple.= > = > As the bootcode is now this wont work. If its as simple as me adding > the pair 30 & "ad" somewhere, I'm satisfied, if not, I'm dissapointed := ) Hah. You should be reusing the major from 'wd'; there is no other way = for this to work, sorry. More eloquently, the only information the loader has is the "disk type" = field from the disklabel, from which it has to decide the major for the = root device (this is all historical Vax breakage, but resistance to = fixing it has been strong). By picking a random number for the major for your new device, you make = the situation much worse than it needs to be; the loader can't tell = which ATA driver is in the kernel. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 0:52:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles193.castles.com [208.214.165.193]) by hub.freebsd.org (Postfix) with ESMTP id 5882215455 for ; Thu, 18 Mar 1999 00:52:54 -0800 (PST) (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 AAA01210; Thu, 18 Mar 1999 00:43:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903180843.AAA01210@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: mjacob@feral.com, "David O'Brien" , =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Wed, 17 Mar 1999 14:49:43 +0100." <41614.921678583@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 00:43:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This will require relabelling all of one class or the other (new disklabel), or a major overhaul of the way that the root disk is found inside the kernel. IMHO, the latter is where the change needs to happen. SLICE might have made it a little easier, but searching won't actually be all that difficult. Someone want to do the work? > > I think you are missing the point. We will not chuck the old > wd* driver until people have crashed all MFM, RLL, ESDI and !ATA > IDE drives. > > So we WANT to be able to tell the difference... > > Poul-Henning > > In message , Matthew Jacob w > rites: > > > >I asked Soren just this kind of question, and he declined to answer. I > >doan geddit... > > > >On Wed, 17 Mar 1999, David O'Brien wrote: > > > >> > Boot from an ata disk on major# 30, device name "ad", plain and simple. > >> > >> Does this mean ata disks won't come under CAM/da ? > >> If not, can we PLEASE rename SCSI disks back to ``sd''? > >> > >> -- > >> -- 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 > >> > > > > > > > >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 > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 1: 8:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 9CCE514C2B for ; Thu, 18 Mar 1999 01:08:22 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id KAA04182; Thu, 18 Mar 1999 10:08:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id KAA45276; Thu, 18 Mar 1999 10:07:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: mjacob@feral.com, "David O'Brien" , =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Thu, 18 Mar 1999 00:43:09 PST." <199903180843.AAA01210@dingo.cdrom.com> Date: Thu, 18 Mar 1999 10:07:50 +0100 Message-ID: <45274.921748070@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG SLICES, if done right, would make SO many things so much easier. Poul-Henning In message <199903180843.AAA01210@dingo.cdrom.com>, Mike Smith writes: > >This will require relabelling all of one class or the other (new >disklabel), or a major overhaul of the way that the root disk is found >inside the kernel. IMHO, the latter is where the change needs to >happen. SLICE might have made it a little easier, but searching won't >actually be all that difficult. Someone want to do the work? > >> >> I think you are missing the point. We will not chuck the old >> wd* driver until people have crashed all MFM, RLL, ESDI and !ATA >> IDE drives. >> >> So we WANT to be able to tell the difference... -- 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 Mar 18 1:23:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id D3EAC153AD for ; Thu, 18 Mar 1999 01:22:51 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id MAA42564; Thu, 18 Mar 1999 12:22:20 +0300 (MSK) (envelope-from mishania) Date: Thu, 18 Mar 1999 12:22:20 +0300 From: "Mikhail A. Sokolov" To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990318122220.A42361@demos.su> References: <19990316223637.A31464@demos.su> <19990317125112.T429@lemis.com> <19990317151924.B3718@demos.su> <199903171629.IAA30097@apollo.backplane.com> <19990317194946.A16101@demos.su> <19990318002557.A26117@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990318002557.A26117@keltia.freenix.fr>; from Ollivier Robert on Thu, Mar 18, 1999 at 12:25:57AM +0100 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 18, 1999 at 12:25:57AM +0100, Ollivier Robert wrote: # According to Mikhail A. Sokolov: # > nope # > # > /dev/da1e 17235735 7414244 8442633 47% /mnt/arc # > /dev/da2e 8617355 1724705 6892650 20% /mnt/spool1 # > /dev/da3e 8617355 1723638 6893717 20% /mnt/spool2 # # disklabel output is what you want to send us, df is not enough :-) We already checked with Greg and Matthew it is neat and ok, disklabel and such. (what did you expect? ;) # Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 1:29:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 5F33A15485 for ; Thu, 18 Mar 1999 01:29:14 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id MAA42711; Thu, 18 Mar 1999 12:28:36 +0300 (MSK) (envelope-from mishania) Date: Thu, 18 Mar 1999 12:28:35 +0300 From: "Mikhail A. Sokolov" To: Ladavac Marino Cc: "'Ollivier Robert'" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990318122835.A42632@demos.su> References: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at>; from Ladavac Marino on Thu, Mar 18, 1999 at 09:32:42AM +0100 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, new 6 panics of such during the night. I'm gonna reproduce the machine configuration without it using the IFT or any other but this precise IFT in general today. The below mentioned are identical. (Did I mention the rc knows about forced fsck -y only, no fsck -p or something?) gdb -k kernel.3 vmcore.3 panicstr: ffs_valloc: dup alloc panic messages: --- panic: ffs_valloc: dup alloc syncing disks... 147 75 2 done (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation code dumping to dev 20401, offset 821524 dump 256.. --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc013b4b9 in panic (fmt=0xc01fdf01 "ffs_valloc: dup alloc") at ../../kern/kern_shutdown.c:448 #2 0xc01b4e84 in ffs_valloc (pvp=0xce418ac0, mode=33188, cred=0xc1fab580, vpp=0xce264cd0) at ../../ufs/ffs/ffs_alloc.c:604 #3 0xc01c21cd in ufs_makeinode (mode=33188, dvp=0xce418ac0, vpp=0xce264f14, cnp=0xce264f28) at ../../ufs/ufs/ufs_vnops.c:2097 #4 0xc01bf9de in ufs_create (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:179 #5 0xc01c23a1 in ufs_vnoperate (ap=0xce264e30) at ../../ufs/ufs/ufs_vnops.c:2309 #6 0xc01631c7 in vn_open (ndp=0xce264f04, fmode=1550, cmode=420) at vnode_if.h:83 #7 0xc015fee9 in open (p=0xcce8b860, uap=0xce264f94) at ../../kern/vfs_syscalls.c:928 #8 0xc01e769f in syscall (frame={tf_es = 47, tf_ds = -1078067153, tf_edi = 1549, tf_esi = 247619088, tf_ebp = -1078010952, tf_isp = -836349980, tf_ebx = 134788528, tf_edx = 219774816, tf_ecx = 0, tf_eax = 5, tf_trapno = 22, tf_err = 2, tf_eip = 672227132, tf_cs = 31, tf_eflags = 534, tf_esp = -1078010980, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #9 0xc01de9fc in Xint0x80_syscall () #10 0x808ae54 in ?? () #11 0x808b3c2 in ?? () #12 0x8084c1f in ?? () #13 0x8067e87 in ?? () #14 0x805c06a in ?? () #15 0x8071f7f in ?? () #16 0x804a1b1 in ?? () -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 1:42:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id AEC251514B for ; Thu, 18 Mar 1999 01:42:12 -0800 (PST) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.2/8.9.1) id KAA09225; Thu, 18 Mar 1999 10:29:20 +0100 (CET) (envelope-from frodef) To: freebsd-current@freebsd.org Subject: MTRR registers From: Frode Vatvedt Fjeld Date: 18 Mar 1999 10:29:20 +0100 Message-ID: <2hk8wfb0y7.fsf@dslab7.cs.uit.no> Lines: 6 X-Mailer: Gnus v5.6.45/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a way in -current to manipulate the MTRR registers of recent intel processors? I really want to make my framebuffer write-combined. -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 3:59:44 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 1F6F6153AC for ; Thu, 18 Mar 1999 03:59:40 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega. (async2-12.iptelecom.net.ua [212.42.68.140]) by ipt2.iptelecom.net.ua (8.8.8/8.8.8) with ESMTP id OAA10103 for ; Thu, 18 Mar 1999 14:00:13 +0200 (EET) (envelope-from sobomax@altavista.net) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.2/8.9.2) with ESMTP id NAA19623 for ; Thu, 18 Mar 1999 13:49:01 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <36F0E836.D22D838D@altavista.net> Date: Thu, 18 Mar 1999 13:49:10 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Annoying behaviour of sysinstall Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD'ers, Can anybody explain why sysinstall (in post-install configuration mode) trying mount already configured swap devices (disk label editor)? Is it a bug or feature? Maybe it will be useful to add routine which will check if swap is already in use? Sincerely, Maxim Sobolev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 4:16: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 722C614E77 for ; Thu, 18 Mar 1999 04:16:03 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id PAA52540; Thu, 18 Mar 1999 15:15:18 +0300 (MSK) (envelope-from mishania) Date: Thu, 18 Mar 1999 15:15:18 +0300 From: "Mikhail A. Sokolov" To: "Mikhail A. Sokolov" Cc: Ladavac Marino , "'Ollivier Robert'" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990318151518.A52468@demos.su> References: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at> <19990318122835.A42632@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <19990318122835.A42632@demos.su>; from "Mikhail A. Sokolov" on Thu, Mar 18, 1999 at 12:28:35PM +0300 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote: # Hello, # panic: ffs_valloc: dup alloc And a brand new one (for today): IdlePTD 2682880 initial pcb at 21c7b8 panicstr: ffs_blkfree: freeing free frag panic messages: --- panic: ffs_blkfree: freeing free frag #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:287 #1 0xc013b4b9 in panic (fmt=0xc01fe159 "ffs_blkfree: freeing free frag") at ../../kern/kern_shutdown.c:448 #2 0xc01b6760 in ffs_blkfree (ip=0xc1fa6500, bno=3066, size=3072) at ../../ufs/ffs/ffs_alloc.c:1352 #3 0xc01b877f in ffs_truncate (vp=0xce571ac0, length=0x0000000000000000, flags=0, cred=0x0, p=0xcce8b2e0) at ../../ufs/ffs/ffs_inode.c:341 #4 0xc01bd1f6 in ufs_inactive (ap=0xce27cedc) at ../../ufs/ufs/ufs_inode.c:84 #5 0xc01c23a1 in ufs_vnoperate (ap=0xce27cedc) at ../../ufs/ufs/ufs_vnops.c:2309 #6 0xc015d91e in vput (vp=0xce571ac0) at vnode_if.h:767 #7 0xc0160c4d in unlink (p=0xcce8b2e0, uap=0xce27cf94) at ../../kern/vfs_syscalls.c:1333 #8 0xc01e769f in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = -1077944836, tf_esi = -1077944828, tf_ebp = -1077944880, tf_isp = -836251676, tf_ebx = -1077945904, tf_edx = -1077945871, tf_ecx = 10, tf_eax = 10, tf_trapno = 7, tf_err = 2, tf_eip = 671698620, tf_cs = 31, tf_eflags = 642, tf_esp = -1077945916, tf_ss = 47}) at ../../i386/i386/trap.c:1101 #9 0xc01de9fc in Xint0x80_syscall () #10 0x804846d in ?? () (kgdb) -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 4:45:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from aniwa.sky (p40-max5.wlg.ihug.co.nz [202.49.241.40]) by hub.freebsd.org (Postfix) with ESMTP id BCACD151DB; Thu, 18 Mar 1999 04:45:11 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from aniwa.sky (localhost [127.0.0.1]) by aniwa.sky (8.9.1a/8.9.1) with ESMTP id BAA22599; Fri, 19 Mar 1999 01:43:40 +1300 (NZDT) Message-Id: <199903181243.BAA22599@aniwa.sky> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-reply-to: Your message of "Thu, 18 Mar 1999 03:03:06 +0900." <36EFEE5A.DE68FF5F@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Mar 1999 01:43:39 +1300 From: Andrew McNaughton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dmitry Valdov wrote: > > I think that there is only one way to fix it - it's to disable making > > *hard*links to directory with mode 1777. I don't use quotas, and don't know a great deal about how they operate, but I think there's another disk filling DOS involving hard links lurking which the above measure would also solve. If a user starts making hard links to (large and growing) log files, with the new links being placed in /var/mail, then presumably those log files will not be deleted correctly as they are rolled over, and will quickly accumulate. This could not bring down a system as rapidly as growing the publicly writable directory with lots of links, but it is not desirable system behaviour. Andrew McNaughton -- ----------- Andrew McNaughton andrew@squiz.co.nz http://www.newsroom.co.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 6: 4:33 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 57504153ED; Thu, 18 Mar 1999 06:04:30 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA06792; Thu, 18 Mar 1999 23:03:32 +0900 (JST) Message-ID: <36F10682.1028368F@newsguy.com> Date: Thu, 18 Mar 1999 22:58:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrew McNaughton Cc: Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: <199903181243.BAA22599@aniwa.sky> 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 Andrew McNaughton wrote: > > I don't use quotas, and don't know a great deal about how they operate, but I think there's another disk filling DOS involving hard links lurking which the above measure would also solve. > > If a user starts making hard links to (large and growing) log files, with the new links being placed in /var/mail, then presumably those log files will not be deleted correctly as they are rolled over, and will quickly accumulate. And what the f* is the user doing with read access to the log directory? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 6:25:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 2849D15404; Thu, 18 Mar 1999 06:25:15 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id JAA00307; Thu, 18 Mar 1999 09:23:43 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Thu, 18 Mar 1999 09:23:43 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Andrew McNaughton Cc: "Daniel C. Sobral" , Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <199903181243.BAA22599@aniwa.sky> 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, 19 Mar 1999, Andrew McNaughton wrote: > > Dmitry Valdov wrote: > > > I think that there is only one way to fix it - it's to disable making > > > *hard*links to directory with mode 1777. > > I don't use quotas, and don't know a great deal about how they operate, > but I think there's another disk filling DOS involving hard links > lurking which the above measure would also solve. > > If a user starts making hard links to (large and growing) log files, > with the new links being placed in /var/mail, then presumably those log > files will not be deleted correctly as they are rolled over, and will > quickly accumulate. > > This could not bring down a system as rapidly as growing the publicly > writable directory with lots of links, but it is not desirable system > behaviour. So, yet another risk associated with allowing hard links :-). Again, presumably the answer here is either a) restrict the creation of hard links, and b) make sure that users never have write access to any partition you don't want them to have the ability to preserve files on. The linking behavior in conjunction with quotas makes a lot of sense: if a user wants to consume someone else's quota, she just hard links to their files so they cannot delete them. And if she are mean, she links to them in private directories so the victim cannot find the links. Even if the user truncates the file, the inode is still consumed in their name. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 6:50: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id A10B514E41 for ; Thu, 18 Mar 1999 06:50:02 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id WAA33699; Thu, 18 Mar 1999 22:49:10 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199903181449.WAA33699@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Pierre Beyssac , freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure In-reply-to: Your message of "Wed, 17 Mar 1999 17:11:00 PST." <199903180111.RAA34092@apollo.backplane.com> Date: Thu, 18 Mar 1999 22:49:10 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: > :> Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't > :> fry? If so, then we have a bug in AMD somewhere. > : > :I tried the cp several times again on a regular NFS mount, to make > :sure, and no, it doesn't seem to panic. So yes, that seems to be > :AMD-related. Can't it be in the vfs layer though? > :-- > :Pierre Beyssac pb@enst.fr > > It's probably AMD. I'm not really up on how AMD works... hasn't someone > done some work on it recently to fix other breakages? Maybe they could > look at this panic. AMD is easy to upset, and that's bad because it's holding a mountpoint in / (ie: /host) which often gets hit by every single getcwd() call when it gets a lstat("/host"...) or whatever. I think this is the single largest source of load on the amd process. The other problem is that amd is an rpc client, it depends on the libc rpc code for robustness, and that's not the first word that springs to mind when I think of it... When amd hangs on a dns lookup, there are all sorts of VFS locking cascades and NFS wedges while the kernel is retrying all those retransmitted packets to amd's pseudo-nfs server port. It's been found to be the primary cause of the 'nfsrcv' hangs - processes wedged in getcwd() style situations trying to stat /host. IMHO, /host needs to move down a level to get it out of the way of getcwd(). NFS mounts should probably move away from / as well, as they cause traffic on each getcwd(). I think the default settings should look something like this.. /net - amd and nfs related stuff /net/sysname/mount1 - nfs mount created by amd /net/sysname/mount2 - nfs mount created by amd /net/host - /host lives here instead. and a symlink: /host -> /net/host I think that'll stop amd from being hammered by all those lstat()'s in getcwd and friends in the root directory. And instead of mounting NFS things as: /a, mount them as /net/a instead and use a symlink. This isn't a "fix", it's just trying to move a particularly weak link out of the direct line of fire. A real solution would be a proper userfs interface that could cope with kernel<->user_process protocol timeouts, process deaths, etc. Of course, then there's always an in-kernel autofs etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 7:19:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 93A5514CA3 for ; Thu, 18 Mar 1999 07:19:41 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA12752; Thu, 18 Mar 1999 10:19:12 -0500 (EST) (envelope-from wollman) Date: Thu, 18 Mar 1999 10:19:12 -0500 (EST) From: Garrett Wollman Message-Id: <199903181519.KAA12752@khavrinen.lcs.mit.edu> To: Peter Wemm Cc: Matthew Dillon , Pierre Beyssac , freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure In-Reply-To: <199903181449.WAA33699@spinner.netplex.com.au> References: <199903180111.RAA34092@apollo.backplane.com> <199903181449.WAA33699@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > AMD is easy to upset, and that's bad because it's holding a mountpoint in / > (ie: /host) which often gets hit by every single getcwd() call when it > gets a lstat("/host"...) or whatever. I think this is the single largest > source of load on the amd process. > IMHO, /host needs to move down a level to get it out of the way of > getcwd(). NFS mounts should probably move away from / as well, as they > cause traffic on each getcwd(). `/host' is non-standard. The Standard Configuration is `/net' is the directory simulated by amd and `/a/${hostname}/root' is where amd mounts the directory tree. This is done specifically to avoid getcwd wedgitude. The example we ship would sorely puzzle anyone who is experienced running a Standard Configuration amd. My machine has, throughout its entire history, had `/home' simulated by amd. I have literally *never* had amd hose my configuration (and I would know it fast since both mail and Web service would break). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 7:36:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 466D11544A for ; Thu, 18 Mar 1999 07:35:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Nepc-000Lrq-00 for current@freebsd.org; Thu, 18 Mar 1999 17:35:36 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: Confused by wcd->acd in UPDATING Date: Thu, 18 Mar 1999 17:35:35 +0200 Message-ID: <84061.921771335@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, 19990316: The name of the old wd.c and atapi.c based CDROM driver has been changed back to wcd. So update your config file to use "device wcd" instead of "device acd". Am I right in thinking that this only applies to people who are _not_ using Soren's new IDE/ATA/ATAPI driver? I ask because I don't use acd at all, I use the recommended atapicd. So I assume that this doesn't apply to me. Old and new are confusing terms in the light of the fact that there are no less than 3 drivers available for ATAPI devices. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 7:51:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 6D6CE15404 for ; Thu, 18 Mar 1999 07:51:29 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id HAA38571 for freebsd-current@freebsd.org; Thu, 18 Mar 1999 07:51:10 -0800 (PST) Date: Thu, 18 Mar 1999 07:51:10 -0800 (PST) From: David Wolfskill Message-Id: <199903181551.HAA38571@pau-amma.whistle.com> To: freebsd-current@freebsd.org Subject: Re: disk quota overriding In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Wed, 17 Mar 1999 20:00:17 -0500 (EST) >From: "David H. Brierley" >On any machine which allows general users to log in, I strongly >recommend making separate file systems for /, /usr, /tmp, and /home, >.... I'll merely point out (since the relevance to -current, per se, is minimal at this point) that there was a recent thread on sage-members@usenix.org on how/whether to split up disks into separate filesystems. And mention that folks how are concerned with such issues might find that SAGE and USENIX may well be resources worth checking out. (Domain is usenix.org; I expect y'all can take Web & majordomo queries from there.) Cheers, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 7:58:13 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 A836215446 for ; Thu, 18 Mar 1999 07:58:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id QAA28850; Thu, 18 Mar 1999 16:57:32 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903181557.QAA28850@freebsd.dk> Subject: Re: Confused by wcd->acd in UPDATING In-Reply-To: <84061.921771335@axl.noc.iafrica.com> from Sheldon Hearn at "Mar 18, 1999 5:35:35 pm" To: sheldonh@iafrica.com (Sheldon Hearn) Date: Thu, 18 Mar 1999 16:57:32 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Sheldon Hearn wrote: > > Hi folks, > > 19990316: > The name of the old wd.c and atapi.c based CDROM driver has > been changed back to wcd. So update your config file to use > "device wcd" instead of "device acd". > > Am I right in thinking that this only applies to people who are _not_ > using Soren's new IDE/ATA/ATAPI driver? Yes. > I ask because I don't use acd at all, I use the recommended atapicd. So > I assume that this doesn't apply to me. No. > Old and new are confusing terms in the light of the fact that there are > no less than 3 drivers available for ATAPI devices. :-) 3 ?? I can only count two, the current one (now wcd) and my new one... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 8: 7:13 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 594F41544F for ; Thu, 18 Mar 1999 08:05:44 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10NfGg-000Lud-00; Thu, 18 Mar 1999 18:03:34 +0200 From: Sheldon Hearn To: Søren Schmidt Cc: current@FreeBSD.ORG Subject: Re: Confused by wcd->acd in UPDATING In-reply-to: Your message of "Thu, 18 Mar 1999 16:57:32 +0100." <199903181557.QAA28850@freebsd.dk> Date: Thu, 18 Mar 1999 18:03:33 +0200 Message-ID: <84234.921773013@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Mar 1999 16:57:32 +0100, Søren Schmidt wrote: > 3 ?? I can only count two, the current one (now wcd) and my new one... You're not as confused as I am. Thanks for the clarification. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 8:16:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from host07.rwsystems.net (kasie.rwsystems.net [209.197.192.103]) by hub.freebsd.org (Postfix) with ESMTP id C5DFA15404; Thu, 18 Mar 1999 08:16:39 -0800 (PST) (envelope-from jwyatt@RWSystems.net) Received: from kasie.rwsystems.net([209.197.192.103]) (1988 bytes) by host07.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 18 Mar 1999 10:01:28 -0600 (CST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-24) Date: Thu, 18 Mar 1999 10:01:20 -0600 (CST) From: James Wyatt To: Andrew McNaughton Cc: "Daniel C. Sobral" , Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: <199903181243.BAA22599@aniwa.sky> 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, 19 Mar 1999, Andrew McNaughton wrote: > > Dmitry Valdov wrote: > > > I think that there is only one way to fix it - it's to disable making > > > *hard*links to directory with mode 1777. > > I don't use quotas, and don't know a great deal about how they > operate, but I think there's another disk filling DOS involving hard > links lurking which the above measure would also solve. If a user > starts making hard links to (large and growing) log files, with the > new links being placed in /var/mail, then presumably those log files > will not be deleted correctly as they are rolled over, and will > quickly accumulate. > > This could not bring down a system as rapidly as growing the publicly > writable directory with lots of links, but it is not desirable system > behaviour. This is beginning to sound like a broken record: 1) I usually move mail to /var/spool/mail, 2) You can't hard link between /var and /var/spool partitions. On some machines /var/log is a filesys to prevent logfile overflows from filling /var anyway. I usually make a different /var/spool on largish machines to help upgrades go faster. I tend to unmount it, /home, and /usr/local and completely replace the OS. No doubt there are other ways to fix this... - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 10:16:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from host07.rwsystems.net (kasie.rwsystems.net [209.197.192.103]) by hub.freebsd.org (Postfix) with ESMTP id 4040314EAA; Thu, 18 Mar 1999 10:16:25 -0800 (PST) (envelope-from jwyatt@RWSystems.net) Received: from kasie.rwsystems.net([209.197.192.103]) (1979 bytes) by host07.rwsystems.net via sendmail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for ; Thu, 18 Mar 1999 11:53:59 -0600 (CST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-24) Date: Thu, 18 Mar 1999 11:53:54 -0600 (CST) From: James Wyatt To: Robert Watson Cc: Andrew McNaughton , "Daniel C. Sobral" , Dmitry Valdov , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Mar 1999, Robert Watson wrote: > The linking behavior in conjunction with quotas makes a lot of sense: if a > user wants to consume someone else's quota, she just hard links to their > files so they cannot delete them. And if she are mean, she links to them > in private directories so the victim cannot find the links. Even if the > user truncates the file, the inode is still consumed in their name. User's manager: Why can't you read your mail or write code? Now, *why* was your unix account blocked? Why did you do *that*? After I make systems fairly secure, I do not hesistate to warn users if they interfere with others. I raraly hesistate in cutting accounts off after warnings. I warn for things like filling /tmp when you vi a 100M application dumo file. I block for things like demonstrably(sp?) injuring others. As I usually log info (ls of dir, clip log msgs, etc...), I usually get cooperation from management. It has also assisted them in gathering enough records to remove such folks from the payroll - they are usually problem folks in other areas as well. Fix social problems with social tools - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 14: 2:40 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 D9E731558F for ; Thu, 18 Mar 1999 14:02:31 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (Postfix) with ESMTP id 70B591F5 for ; Fri, 19 Mar 1999 01:02:10 +0300 (MSK) Date: Fri, 19 Mar 1999 01:02:10 +0300 (MSK) From: oZZ!!! To: FreeBSD-current@FreeBSD.org Subject: BIND-8.2 Released March 16, 1999 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! What do think about add new version of BIND to -current? Rgdz, Sergey Osokin, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 18:36: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 D0B2314BDD for ; Thu, 18 Mar 1999 18:36:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA43337; Thu, 18 Mar 1999 18:36:09 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Mar 1999 18:36:09 -0800 (PST) From: Matthew Dillon Message-Id: <199903190236.SAA43337@apollo.backplane.com> To: "Mikhail A. Sokolov" Cc: "Mikhail A. Sokolov" , Ladavac Marino , "'Ollivier Robert'" , current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c References: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at> <19990318122835.A42632@demos.su> <19990318151518.A52468@demos.su> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote: :# Hello, :# panic: ffs_valloc: dup alloc : :And a brand new one (for today): : :IdlePTD 2682880 :initial pcb at 21c7b8 :panicstr: ffs_blkfree: freeing free frag :panic messages: :--- :panic: ffs_blkfree: freeing free frag I'm running out of ideas. Ok, three more things: First, when you updated your /usr/src/sys tree from cvs, did you also update /usr/src/contrib/sys? aka softupdates? Second, Make sure you are using softlinks for the softupdates files in /usr/src/sys/ufs/ffs/, pointing to their actual location in contrib, rather then a copies of the files. Third, Try turning off reallocblks: sysctl -w vfs.ffs.doreallocblks=0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 19:26: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 24D2B14D2E for ; Thu, 18 Mar 1999 19:25:58 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 3822 invoked by uid 1001); 19 Mar 1999 03:25:38 +0000 (GMT) To: osa@etrust.ru Cc: FreeBSD-current@FreeBSD.org Subject: Re: BIND-8.2 Released March 16, 1999 From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 19 Mar 1999 01:02:10 +0300 (MSK)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 19 Mar 1999 04:25:37 +0100 Message-ID: <3820.921813937@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What do think about add new version of BIND to -current? There have been some error reports against 8.2-REL, and I think we should let it have a few more weeks to stabilize before it is brought into -current. (We're running 8.2 at some important name servers here, for instance one which is authoritative for .no. It seems to be working fine for us now, but we had some crashes during 8.2 beta testing.) 8.2 compiles out of the box on FreeBSD ("make clean; make depend; make") so it's very easy to setup if you really need the new features in 8.2 right now. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 18 22: 0: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 1A31514BEF for ; Thu, 18 Mar 1999 22:00:03 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id WAA23916; Thu, 18 Mar 1999 22:59:35 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903190559.WAA23916@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: mishania@demos.net (Mikhail A. Sokolov), current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c In-reply-to: Your message of "Tue, 16 Mar 1999 13:36:40 MST." <199903162036.NAA27623@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 22:50:33 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> # Are you *sure* you're running -current as of today? Justin put code in to >> # silence Illegal request error messages from the sync cache command. These messages, since they are occurring only during a panic, are caused by the code in dashutdown(). I didn't modify this code in my last checkin, but cannot see why it would not properly prevent the messages from being displayed. Perhaps Mikhail would be willing to instrument the code and determine why it doesn't work properly? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 1:11:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2AB3614E85 for ; Fri, 19 Mar 1999 01:11:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA73362 for current@freebsd.org; Fri, 19 Mar 1999 01:11:17 -0800 (PST) (envelope-from obrien) Date: Fri, 19 Mar 1999 01:11:17 -0800 From: "David O'Brien" To: current@freebsd.org Subject: panics while reading Solaris CDROM Message-ID: <19990319011117.A73322@relay.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get very consistant panics when doing ``find . -type f |xargs grep foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm not sure how to proceed in fixing this. The core files from the panic seem to be useless -- I can't get anything useful out of ``where'' with a kernel w/debugging symbols: savecore: reboot after panic: vm_fault: fault on nofault entry, addr: c2923000 savecore: writing core to /var/crash/vmcore.2 savecore: writing kernel to /var/crash/kernel.2 (kgdb) symbol-file ./kernel (kgdb) exec-file /var/crash/kernel.2 (kgdb) core-file /var/crash/vmcore.2 IdlePTD 7630437 initial pcb at 2783e4 panic messages: --- dmesg: kvm_read: invalid address (c026ed38) --- #0 0x2520656c in ?? () (kgdb) In DDB I get: panic: vm_fault on nofault entry, addr: c2b08000 db> trace vm_fault(c029c854, c2b08000, 1, 0, c4f147e0) at vm_fault +0x120 trap_pfault(c56bdb40, 0, c2b08000, 80000000, c0a3500) at trap_pfault +0xf0 ... ---trap 0xc, eip=0xc0140146, esp=0xc56bdb7c, epb=0xc56bdd1c --- cd9660_lookup(c56bdd4c, c56de414, 16, c56bdf24, c56fc980) at cd9660_lookup+0x226 vfs_cache_lookup(c56bdd9c, c56d5ac0, c56bdf00, c56bdf24, 0) at vfs_cache_lookup+0x269 lookup(56bdf00, 0, c56bdf00, 9e9, c08fb580) at lookup+0x305 namei(56bdf00, 0, c56bdf94, fffffffc, c0a3e600) at namei+0x1cd vn_open(c56bdf00, 1, 9e9, c4f147e0, c027bdfc) at vn_open+0x1cd open(c4f147e0, c56bdf94, 9fb, bfbf9a4b, 8050f0d) at open+0xbb syscall(2f, 2f, 8050f0d, bfbf9a4b, bfbec648) at syscall+0x19b Xint0x80_syscall() at Xinit0x80_syscall+0x2c My kernel is compiled with ``option DIAGNOSTIC'', my only KLD's are linux.ko and daemon_saver.ko. FreeBSD 4.0-CURRENT #40: Fri Mar 19 00:20:08 PST 1999 rootk@dragon.nuxi.com:/FBSD/src/sys/compile/DRAGON Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199432607 Hz CPU: AMD-K6tm w/ multimedia extensions (199.43-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 94785536 (92564K bytes) Preloaded elf kernel "kernel" at 0xc0301000. ccd0-1: Concatenated disk drivers Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 fxp0: rev 0x02 int a irq 12 on pci0.17.0 fxp0: Ethernet address 00:a0:c9:8c:c4:49 vga0: rev 0x01 int a irq 9 on pci0.18.0 ahc0: rev 0x00 int a irq 11 on pci0.19.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 15 on pci0.20.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs Probing for PnP devices: CSN 1 Vendor ID: CTL00c7 [0xc7008c0e] Serial 0x101fd54b Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x101fd54b) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:ee:e8:bf, type SMC8216/SMC8216C (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pca0 on motherboard pca0: PC speaker audio driver pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6180MB (12658275 sectors), 13395 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled Waiting 2 seconds for SCSI devices to settle da12 at ahc1 bus 0 target 2 lun 0 da12: Fixed Direct Access SCSI-2 device da12: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da12: 2049MB (4197520 512 byte sectors: 255H 63S/T 261C) da13 at ahc1 bus 0 target 3 lun 0 da13: Fixed Direct Access SCSI-2 device da13: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da13: 2033MB (4165272 512 byte sectors: 255H 63S/T 259C) da11 at ahc1 bus 0 target 1 lun 0 da11: Fixed Direct Access SCSI-2 device da11: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da11: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 1222MB (2503872 512 byte sectors: 255H 63S/T 155C) cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 4.032MB/s transfers (4.032MHz, offset 15) cd1: cd present [326242 x 2048 byte records] da8 at ahc0 bus 0 target 8 lun 0 da8: Fixed Direct Access SCSI-2 device da8: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da8: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Start pid=2 Start pid=3 Start pid=4 da10 at ahc1 bus 0 target 0 lun 0 da10: Fixed Direct Access SCSI-2 device da10: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da10: 4303MB (8813870 512 byte sectors: 255H 63S/T 548C) cd2 at ahc0 bus 0 target 6 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 5.000MB/s transfers (5.000MHz, offset 15) cd2: cd present [313986 x 2048 byte records] cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [230993 x 2048 byte records] -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 1:47:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 35CD714CC4 for ; Fri, 19 Mar 1999 01:47:06 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id BAA73516; Fri, 19 Mar 1999 01:46:47 -0800 (PST) (envelope-from obrien) Date: Fri, 19 Mar 1999 01:46:47 -0800 From: "David O'Brien" To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: panics while reading Solaris CDROM Message-ID: <19990319014647.A73489@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990319011117.A73322@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990319011117.A73322@relay.nuxi.com>; from David O'Brien on Fri, Mar 19, 1999 at 01:11:17AM -0800 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 19, 1999 at 01:11:17AM -0800, David O'Brien wrote: > I get very consistant panics when doing ``find . -type f |xargs grep > foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm > not sure how to proceed in fixing this. On another machine (CVSuped and make world on Thur evening), the same command also crashes. The machine was so wedged, I couldn't drop into DDB, nor scroll to the first panic messages, but this is the last one: Fault trap 12: page fault while in kernel mode fault virual address = 0x8 fault code = supervisor write, page not present instruction pointer = 0x8:0xc012f531 stack pointer = 0x10:0xc4ab966c frame pointer = 0x10:0xc4a69678 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres1, def32 1, gran 1 processor eflags = interupt enable, resume, IOPL=0 current process = 328 (egrep) interupt mask = net tty bio cam trap number = 12 panic: page fault (da0:ahc0:0:0:0) Synchronize cache failed, status == 0xb, scsi status == 0x0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 2:38: 3 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 53E4314BF4 for ; Fri, 19 Mar 1999 02:37:58 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA22624; Fri, 19 Mar 1999 21:37:38 +1100 Date: Fri, 19 Mar 1999 21:37:38 +1100 From: Bruce Evans Message-Id: <199903191037.VAA22624@godzilla.zeta.org.au> To: current@FreeBSD.ORG, obrien@NUXI.com Subject: Re: panics while reading Solaris CDROM Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I get very consistant panics when doing ``find . -type f |xargs grep >foo'' on a Solaris CDROM in my Plextor 8x CDROM drive (device cd0). I'm >not sure how to proceed in fixing this. This should be fixed now. I got very consistent panics for `cd /dosD/windows; find . | xargs cksum' on an msdosfs with a block size of 2K :). cd9660 also has a block size of 2K, and getnewbuf() returned corrupt buffers when it reused buffers that had b_data offset 2K into the space reserved for the buffer data. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 5:33:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (Postfix) with ESMTP id 58AEB153F8 for ; Fri, 19 Mar 1999 05:33:02 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.9.3/8.9.2) id QAA02854; Fri, 19 Mar 1999 16:32:32 +0300 (MSK) (envelope-from mishania) Date: Fri, 19 Mar 1999 16:32:32 +0300 From: "Mikhail A. Sokolov" To: Matthew Dillon Cc: current@freebsd.org Subject: Re: repeated ufs_dirbad() panics on 4.0-c Message-ID: <19990319163231.A2727@demos.su> References: <97A8CA5BF490D211A94F0000F6C2E55D097567@s-lmh-wi-900.corpnet.at> <19990318122835.A42632@demos.su> <19990318151518.A52468@demos.su> <199903190236.SAA43337@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199903190236.SAA43337@apollo.backplane.com>; from Matthew Dillon on Thu, Mar 18, 1999 at 06:36:09PM -0800 X-Useless-Header: Look ma! It's a # sign! X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 18, 1999 at 06:36:09PM -0800, Matthew Dillon wrote: # :On Thu, Mar 18, 1999 at 12:28:35PM +0300, Mikhail A. Sokolov wrote: # :# Hello, # :# panic: ffs_valloc: dup alloc # : # :And a brand new one (for today): # : # :IdlePTD 2682880 # :initial pcb at 21c7b8 # :panicstr: ffs_blkfree: freeing free frag # :panic messages: # :--- # :panic: ffs_blkfree: freeing free frag # I'm running out of ideas. Ok, three more things: Well, me too.. # First, when you updated your /usr/src/sys tree from cvs, did you also # update /usr/src/contrib/sys? aka softupdates? Yes, I'm running cvsupd server myself and stuff ;) # Second, Make sure you are using softlinks for the softupdates files in # /usr/src/sys/ufs/ffs/, pointing to their actual location in contrib, # rather then a copies of the files. Of course # Third, Try turning off reallocblks: # sysctl -w vfs.ffs.doreallocblks=0 That's been in use since decided somewhere in November, 1998 on ~90% of machines. -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 13:17:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 57EB0155ED for ; Fri, 19 Mar 1999 13:17:46 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id PAA80886; Fri, 19 Mar 1999 15:14:30 -0600 (CST) (envelope-from bob) Date: Fri, 19 Mar 1999 15:14:30 -0600 From: Bob Willcox To: Robert Nordier Cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? Message-ID: <19990319151430.A80525@luke.pmr.com> Reply-To: Bob Willcox References: <199903171338.OAA26021@freebsd.dk> <199903171655.SAA00910@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903171655.SAA00910@ceia.nordier.com>; from Robert Nordier on Wed, Mar 17, 1999 at 06:55:44PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an LS-120 and I'd be happy to test the new boot code with it. Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 13:59:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 4FE7815650 for ; Fri, 19 Mar 1999 13:59:37 -0800 (PST) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id QAA25265 for ; Fri, 19 Mar 1999 16:59:19 -0500 (EST) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.8.8/8.8.7) with ESMTP id QAA15741 for ; Fri, 19 Mar 1999 16:59:17 -0500 (EST) (envelope-from ath@stiegl.niksun.com) Message-Id: <199903192159.QAA15741@stiegl.niksun.com> From: Andrew Heybey To: freebsd-current@freebsd.org Subject: deadlock in 3.1-RELEASE Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Fri, 19 Mar 1999 16:59:17 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Meta question: should I send this kind of thing to -current or -stable? I experienced it under 3.1, but I don't know if the people who are working on the VM and/or IO systems read -stable?] I can wedge my 3.1-RELEASE system under the following conditions: Two fxp fast ethernet interfaces, each receiving ~15k 512-byte pkts/sec. All of the above data (~15MB/sec) being written to a ccd partition striped across three disks. A couple of processes also trying to read the data from disk. It takes anywhere from 30 minutes to several hours to occur. It has happened with both an AIC7890 and an NCR 895 (Tekram 390U2W) disk controller. When the deadlock does occur, "ps" (in ddb) says that there are many processes in vmwait. The pagedaemon is in an inode wait. The stack trace is in default_halt() (which I assume just means that there are no runnable processes). The system is not short of memory (unless "short of memory" means that it is attempting to use it all as a disk cache). A search of cvs-commiters for "vmwait deadlock" did not reveal (to my ignorant eye, anyway) any fixes to -current that would apply to this problem. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 14:34:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 94A4615CBD for ; Fri, 19 Mar 1999 14:34:40 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA15884; Fri, 19 Mar 1999 15:24:55 -0700 (MST) Date: Fri, 19 Mar 1999 15:24:55 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199903192224.PAA15884@narnia.plutotech.com> To: Robert Nordier Cc: current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? X-Newsgroups: pluto.freebsd.current In-Reply-To: <199903171103.NAA13749@ceia.nordier.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903171103.NAA13749@ceia.nordier.com> you wrote: > Søren Schmidt wrote: > >> OK, easy enough, this is what I want to do: >> >> Boot from an ata disk on major# 30, device name "ad", plain and simple. > > I'd be inclined to handle this outside the boot code, by treating the > passed in major# as describing the device rather than specifying > the driver. Why not have the boot blocks pass in a device 'name' rather than a major number. If the goal is to ditch major numbers entirely with a properly working DEVFS, then using major numbers in the new boot loader seems to be the wrong way to go. Until DEVFS is a reality, the kernel will still need to perform a name to major number translation, but it should be left up to the kernel. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 14:50:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles228.castles.com [208.214.165.228]) by hub.freebsd.org (Postfix) with ESMTP id 64203157E7 for ; Fri, 19 Mar 1999 14:50:26 -0800 (PST) (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 OAA07306; Fri, 19 Mar 1999 14:43:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903192243.OAA07306@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Justin T. Gibbs" Cc: Robert Nordier , current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Fri, 19 Mar 1999 15:24:55 MST." <199903192224.PAA15884@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Mar 1999 14:43:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199903171103.NAA13749@ceia.nordier.com> you wrote: > > S=F8ren Schmidt wrote: > > = > >> OK, easy enough, this is what I want to do: > >> = > >> Boot from an ata disk on major# 30, device name "ad", plain and simp= le. > > = > > I'd be inclined to handle this outside the boot code, by treating the= > > passed in major# as describing the device rather than specifying > > the driver. > = > Why not have the boot blocks pass in a device 'name' rather than a > major number. If the goal is to ditch major numbers entirely with > a properly working DEVFS, then using major numbers in the new boot > loader seems to be the wrong way to go. Until DEVFS is a reality, > the kernel will still need to perform a name to major number translatio= n, > but it should be left up to the kernel. Because there's no way to work out a name either. All the loader has to go on is the BIOS unit number and the disklabel, = the latter of which can't be relied on to be up-to-date (ie. it = reflects what the disk was when it was laid out, not what some nominal = kernel is going to call it). The *only* way for this to work is for the kernel to hunt for the = root device, possibly with some helping hints from the loader. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 16:40:29 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 4E3CD14FDF for ; Fri, 19 Mar 1999 16:40:26 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA68823; Fri, 19 Mar 1999 16:33:38 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id QAA10236; Fri, 19 Mar 1999 16:33:26 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199903200033.QAA10236@whistle.com> Subject: Re: deadlock in 3.1-RELEASE In-Reply-To: <199903192159.QAA15741@stiegl.niksun.com> from Andrew Heybey at "Mar 19, 99 04:59:17 pm" To: ath@niksun.com (Andrew Heybey) Date: Fri, 19 Mar 1999 16:33:25 -0800 (PST) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL29 (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 Andrew Heybey writes: | When the deadlock does occur, "ps" (in ddb) says that there are many | processes in vmwait. The pagedaemon is in an inode wait. The stack | trace is in default_halt() (which I assume just means that there are | no runnable processes). The system is not short of memory (unless | "short of memory" means that it is attempting to use it all as a disk | cache). | | A search of cvs-commiters for "vmwait deadlock" did not reveal (to my | ignorant eye, anyway) any fixes to -current that would apply to this | problem. I have an environment that triggered this in less then 1/2 hour. Julian with the help of his friends (ie Matt & Alan) have brought in some changes from -current that got rid of my problem. Getting the latest RELENG_3 stuff should fix it. My processes got stuck on vmwait. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 17:35:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id EB83C15159 for ; Fri, 19 Mar 1999 17:34:59 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA08263; Fri, 19 Mar 1999 17:34:40 -0800 (PST) Date: Fri, 19 Mar 1999 17:34:40 -0800 (PST) From: "Steven P. Donegan" To: current@freebsd.org Subject: IPSEC support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any IPSEC support available for current? I've found support for 2.2.8, but not so far for current. Steven P. Donegan email: donegan@quick.net Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687 WANG Global (within 1 meter - 133 ASL) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 19:42: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from btw.plaintalk.bellevue.wa.us (btw.aa.net [206.125.75.16]) by hub.freebsd.org (Postfix) with ESMTP id 296BA15421 for ; Fri, 19 Mar 1999 19:41:34 -0800 (PST) (envelope-from dennis.glatting@software-munitions.com) Received: from imo.plaintalk.bellevue.wa.us (imo.plaintalk.bellevue.wa.us [192.168.1.7]) by btw.plaintalk.bellevue.wa.us (8.9.3/8.9.3) with ESMTP id TAA37923; Fri, 19 Mar 1999 19:41:04 -0800 (PST) Received: (from dennisg@localhost) by imo.plaintalk.bellevue.wa.us (8.8.7/8.8.7) id TAA04943; Fri, 19 Mar 1999 19:41:03 -0800 (PST) Message-Id: <199903200341.TAA04943@imo.plaintalk.bellevue.wa.us> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Dennis Glatting Date: Fri, 19 Mar 99 19:41:01 -0800 To: "Steven P. Donegan" Subject: Re: IPSEC support? Cc: current@FreeBSD.ORG Reply-To: dennis.glatting@plaintalk.bellevue.wa.us References: X-No-Archive: : yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any IPSEC support available for current? I've found > support for 2.2.8, but not so far for current. > Note: Last Thursday at the IETF SAAG the IETF turned its back on 1DES. With regard to IPsec, the appropriate RFCs will be ammended. -dpg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 21:31:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from newnet.tamu.edu (newnet.tamu.edu [128.194.177.50]) by hub.freebsd.org (Postfix) with ESMTP id B0F1A1501E for ; Fri, 19 Mar 1999 21:31:04 -0800 (PST) (envelope-from russell@newnet.tamu.edu) Received: by newnet.tamu.edu (Postfix, from userid 106) id EBC5A15882; Fri, 19 Mar 1999 23:30:44 -0600 (CST) Date: Fri, 19 Mar 1999 23:30:44 -0600 From: Russell Neeper To: Greg Lehey Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help! (was: Crash while newfs'ing innocent vinum volume on fresh system.) Message-ID: <19990319233044.A10397@net.tamu.edu> Reply-To: r-neeper@tamu.edu References: <19990317142107.A78437@matti.ee> <19990318133123.S429@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i In-Reply-To: <19990318133123.S429@lemis.com>; from Greg Lehey on Thu, Mar 18, 1999 at 01:31:23PM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I decided to give vinum a try a few days ago and ran into the same problem as Vallo - after using it for a short period of time it caused a kernel panic due to a page fault. I spent some time with kgdb today and believe that I have found the bug. On Thu, Mar 18, 1999 at 01:31:23PM +1030, Greg Lehey wrote: > This is a problem I've seen before, but it completely baffles me. The > request passed to launch_requests (frame 10) has been deallocated. > Some of the debug code I put in caught it: > > (kgdb) p freeinfo[7] > $2 = { > time = { > tv_sec = 921669613, > tv_usec = 289712 > }, > seq = 24, > size = 36, > line = 174, > address = 0xf0a3cb00 "ÞÀ­Þh\235\"ðÞÀ­ÞÀÈ£ðÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­Þ", > file = "vinuminterrupt.c" > } > > This was called from freerq, which frees the complete request. freerq > is called from only four places: one on completion of the request > (which in this case is just about to be started), one if the request > is aborted (which also sets bp->b_error, which is not set here), once > in a read context (which is not applicable here: it's a write), and > once just before the call to launch_requests in frame 11: The best that I can tell, the problem is with the first call that you listed: "on completion of the request". The function 'complete_rqe' is called asynchronously by an interrupt at the completion of the I/O request. > So where is this coming from? I'm completely baffled. It doesn't > happen to most people, though I have had reports of one or two other > cases. About the only clue is that the problem didn't occur when I > removed the debug memory allocator, but I don't know whether it went > away or into hiding. I'd really like to find out what's going on > here. I think that removing the debug memory allocator just made it go into hiding because it changed the timing of the code. Freeing the request structure in the interrupt routine is causing a race condition in the function 'launch_requests'. Interrupts must be disabled around any and all code which refers to the request chain and this wasn't being done. I have created a patch that seems to fix the problem. However, there could be other places in the code that refers to the request chain without disabling interrupts. After looking at it for only a few hours, I'm not familiar enough with it to tell. Hope this helps. Here's the patch: diff -u vinum/vinumrequest.c vinum-mod/vinumrequest.c --- vinum/vinumrequest.c Thu Mar 18 20:21:46 1999 +++ vinum-mod/vinumrequest.c Fri Mar 19 22:55:49 1999 @@ -258,13 +258,8 @@ biodone(bp); freerq(rq); return -1; - } { /* XXX */ - int result; - int s = splhigh(); - result = launch_requests(rq, reviveok); /* now start the requests if we can */ - splx(s); - return result; } + return launch_requests(rq, reviveok); /* now start the requests if we can */ } else /* * This is a write operation. We write to all @@ -366,6 +361,7 @@ if (debug & DEBUG_LASTREQS) logrq(loginfo_user_bpl, rq->bp, rq->bp); #endif + s = splbio(); for (rqg = rq->rqg; rqg != NULL; rqg = rqg->next) { /* through the whole request chain */ rqg->active = rqg->count; /* they're all active */ rq->active++; /* one more active request group */ @@ -396,13 +392,13 @@ logrq(loginfo_rqe, rqe, rq->bp); #endif /* fire off the request */ - s = splbio(); (*bdevsw[major(rqe->b.b_dev)]->d_strategy) (&rqe->b); - splx(s); } /* XXX Do we need caching? Think about this more */ } } + splx(s); + return 0; } I remove the splhigh/splx from around the first call of launch_requests because, as far as I can tell, it became redundant after adding splbio/splx around the for loop in the launch_requests function. ------ Russell Neeper Texas A&M University Russell-Neeper@tamu.edu Computing & Information Services Network Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 19 22:11:44 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 DC32F14EEB for ; Fri, 19 Mar 1999 22:11:30 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA07221; Sat, 20 Mar 1999 16:41:10 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA88279; Sat, 20 Mar 1999 16:41:08 +1030 (CST) Message-ID: <19990320164108.P429@lemis.com> Date: Sat, 20 Mar 1999 16:41:08 +1030 From: Greg Lehey To: r-neeper@tamu.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help! (was: Crash while newfs'ing innocent vinum volume on fresh system.) References: <19990317142107.A78437@matti.ee> <19990318133123.S429@lemis.com> <19990319233044.A10397@net.tamu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <19990319233044.A10397@net.tamu.edu>; from Russell Neeper on Fri, Mar 19, 1999 at 11:30:44PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 19 March 1999 at 23:30:44 -0600, Russell Neeper wrote: > I decided to give vinum a try a few days ago and ran into the same > problem as Vallo - after using it for a short period of time it caused > a kernel panic due to a page fault. > > I spent some time with kgdb today and believe that I have found the bug. This message came in literally two seconds after I send a reply to Vallo about the bug: Mar 20 16:00:54 allegro sendmail[7086]: QAA07084: to=, delay=00:00:07, xdelay=00:00:07, mailer=esmtp, relay=solaris.matti.ee. [194.126.98.135], stat=Sent (HAA07473 Message accepted for delivery) Mar 20 16:00:56 allegro sendmail[7087]: QAA07087: from=, size=5117, class=0, pri=35117, nrcpts=1, msgid=<19990319233044.A10397@net.tamu.edu>, bodytype=8BITMIME, proto=ESMTP, relay=newnet.tamu.edu [128.194.177.50] Mar 20 16:00:57 allegro sendmail[7088]: QAA07087: to=, delay=00:00:04, xdelay=00:00:01, mailer=local, stat=Sent Anyway, wonderful! Exactly right. I'm very impressed that you found it at effectively the same time as me. More comments further down. > On Thu, Mar 18, 1999 at 01:31:23PM +1030, Greg Lehey wrote: >> This is a problem I've seen before, but it completely baffles me. The >> request passed to launch_requests (frame 10) has been deallocated. >> Some of the debug code I put in caught it: >> >> (kgdb) p freeinfo[7] >> $2 = { >> time = { >> tv_sec = 921669613, >> tv_usec = 289712 >> }, >> seq = 24, >> size = 36, >> line = 174, >> address = 0xf0a3cb00 "ÞÀ­Þh\235\"ðÞÀ­ÞÀÈ£ðÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­ÞÞÀ­Þ", >> file = "vinuminterrupt.c" >> } >> >> This was called from freerq, which frees the complete request. freerq >> is called from only four places: one on completion of the request >> (which in this case is just about to be started), one if the request >> is aborted (which also sets bp->b_error, which is not set here), once >> in a read context (which is not applicable here: it's a write), and >> once just before the call to launch_requests in frame 11: > > The best that I can tell, the problem is with the first call that you > listed: "on completion of the request". The function 'complete_rqe' is > called asynchronously by an interrupt at the completion of the I/O > request. Correct. >> So where is this coming from? I'm completely baffled. It doesn't >> happen to most people, though I have had reports of one or two other >> cases. About the only clue is that the problem didn't occur when I >> removed the debug memory allocator, but I don't know whether it went >> away or into hiding. I'd really like to find out what's going on >> here. > > I think that removing the debug memory allocator just made it go into > hiding because it changed the timing of the code. Possibly. It would work in the right direction. > Freeing the request structure in the interrupt routine is causing a > race condition in the function 'launch_requests'. Interrupts must > be disabled around any and all code which refers to the request > chain and this wasn't being done. I have created a patch that seems > to fix the problem. However, there could be other places in the > code that refers to the request chain without disabling interrupts. > After looking at it for only a few hours, I'm not familiar enough > with it to tell. This is the only place. > Here's the patch: > > diff -u vinum/vinumrequest.c vinum-mod/vinumrequest.c > --- vinum/vinumrequest.c Thu Mar 18 20:21:46 1999 > +++ vinum-mod/vinumrequest.c Fri Mar 19 22:55:49 1999 > @@ -258,13 +258,8 @@ > biodone(bp); > freerq(rq); > return -1; > - } { /* XXX */ > - int result; > - int s = splhigh(); > - result = launch_requests(rq, reviveok); /* now start the requests if we can */ > - splx(s); > - return result; > } > + return launch_requests(rq, reviveok); /* now start the requests if we can */ > } else > /* > * This is a write operation. We write to all > @@ -366,6 +361,7 @@ > if (debug & DEBUG_LASTREQS) > logrq(loginfo_user_bpl, rq->bp, rq->bp); > #endif > + s = splbio(); > for (rqg = rq->rqg; rqg != NULL; rqg = rqg->next) { /* through the whole request chain */ > rqg->active = rqg->count; /* they're all active */ > rq->active++; /* one more active request group */ > @@ -396,13 +392,13 @@ > logrq(loginfo_rqe, rqe, rq->bp); > #endif > /* fire off the request */ > - s = splbio(); > (*bdevsw[major(rqe->b.b_dev)]->d_strategy) (&rqe->b); > - splx(s); > } > /* XXX Do we need caching? Think about this more */ > } > } > + splx(s); > + > return 0; > } > > I remove the splhigh/splx from around the first call of launch_requests > because, as far as I can tell, it became redundant after adding > splbio/splx around the for loop in the launch_requests function. Yup, sloppy coding on my part. I had suspected a problem in the area, so I put that in to see if it would fix it. It seemed to, but I had only protected one of the two calls (the read call). *sigh*. It's interesting to note that this happened reliably and repeatedly on a system with IDE drives; in order for it to happen, the I/O request (there was only one) had to complete before the top half got back to the calling function. I suspect there might be a problem in that area. Here's an overview of the stages of the request. The format of this list is described in vinum(8) under the info -V command, though this comes from gdb (thus the unconverted times). Time Event Buf Dev Offset Bytes SD SDoff Doffset Goffset 921802787.741353 1VS Write 0xf1569f90 0x5b00 0xe0 8192 921802787.741381 2LR Write 0xf1569f90 0x5b00 0xe0 8192 921802787.741385 3RQ Write 0xf1569f90 0xc 0x1e9 8192 0 e0 0 0 921802787.742031 4DN Write 0xf1569f90 0xc 0x1e9 8192 0 e0 0 0 In other words, the request completed after 650 µs: it was issued (3RQ) at 741385 µs past the second, and completed at 742031 µs (4DN). Still, it's puzzling to know why the IDE driver didn't return control to the caller during that time. Before you ask, yes, it was PIO, but that shouldn't cause the top half to hold on to the caller. 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 Sat Mar 20 0:11:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 58E21150CF for ; Sat, 20 Mar 1999 00:11:00 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id AAA16581; Sat, 20 Mar 1999 00:59:37 -0700 (MST) Date: Sat, 20 Mar 1999 00:59:37 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199903200759.AAA16581@narnia.plutotech.com> To: =?US-ASCII?Q?S=F8ren?= Schmidt Cc: current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? X-Newsgroups: pluto.freebsd.current In-Reply-To: <199903171205.NAA25764@freebsd.dk> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903171205.NAA25764@freebsd.dk> you wrote: > It seems David O'Brien wrote: >> > Boot from an ata disk on major# 30, device name "ad", plain and simple. >> >> Does this mean ata disks won't come under CAM/da ? > > Not if I can help it :) > It could be done by slamming a translation layer ontop of the existing > wd driver or of cause on top of the new I'm doing, but all it adds > is overhead, both performance wise and codesize wise. There is nothing > that prohibits having both of cause, but it is not a priority for me > to add more complexity into the picture before everything else is done. My main complaint so far about the new ATAPI stuff is that it duplicates or lacks (assuming it will be implemented) much of what CAM would have given for almost free: - Interrupt driven configuration - Peripheral driver to device routing - debugging/tracing facilities - an extensible error recovery framework - an understanding of command queuing (also relevant for ATAPI) - understanding of hot plug events - an aplication pass-thru interface The question about translation layers is secondary and I would likely choose to not introduce a translation at all. Issuing pure ATAPI commands to atapi devices at the peripheral driver level is somthing that CAM could easily do. I would probably choose to merge ATAPI functionality into the da driver to avoid duplicated code and to ensure that bug fixes only need to be performed in one place. After all, the machinery for talking to an ATAPI or SCSI disk is very similar (If the disk says it needs to be spun up, spin it up; if we have too many transactions outstanding and fear tag starvation, send an ordered tag; when we close the disk or panic, synchronize its cache to stable media; etc. etc.) even if the command op codes and format are slightly different. But hey, I don't have the time to work on ATAPI. Soren does, so he gets to call the shots. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 0:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 33AA814FAD for ; Sat, 20 Mar 1999 00:22:39 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id BAA21142; Sat, 20 Mar 1999 01:21:38 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903200821.BAA21142@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: "Justin T. Gibbs" , Robert Nordier , current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Fri, 19 Mar 1999 14:43:09 PST." <199903192243.OAA07306@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Mar 1999 01:12:36 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In article <199903171103.NAA13749@ceia.nordier.com> you wrote: >> > S=F8ren Schmidt wrote: >> > = >> >> OK, easy enough, this is what I want to do: >> >> = >> >> Boot from an ata disk on major# 30, device name "ad", plain and sim= ple. >> > = >> > I'd be inclined to handle this outside the boot code, by treating th= e >> > passed in major# as describing the device rather than specifying >> > the driver. >> = >> Why not have the boot blocks pass in a device 'name' rather than a >> major number. If the goal is to ditch major numbers entirely with >> a properly working DEVFS, then using major numbers in the new boot >> loader seems to be the wrong way to go. Until DEVFS is a reality, >> the kernel will still need to perform a name to major number translati= on, >> but it should be left up to the kernel. > >Because there's no way to work out a name either. If I explicitly say: 1:foobar(0,a)/kernel there certainly is a way to work out the name. Perhaps in the autoboot case you'll have to guess, but it would be nice if the current boot mechanism allowed user intervention as a way to boot a kernel with an unknown bdev. >All the loader has to go on is the BIOS unit number and the disklabel, = >the latter of which can't be relied on to be up-to-date (ie. it = >reflects what the disk was when it was laid out, not what some nominal = >kernel is going to call it). Well, the disklabel format should be revamped so that we can tag devices in a unique fashion (user's pet name for the partition plus a 128bit random number perhaps). This would allow the boot loader to alway tell the kernel unambiguously how to find the root device. It would also allow us to ensure that the attach order for all devices with a BSD label matched the BIOS probe order. I would also love to be able to mount volumes by the name that I've picked for them rather than by device node too - it would practically eliminate the need for hard wiring of devices. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 1:59:27 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 AB3FF14DD5 for ; Sat, 20 Mar 1999 01:59:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA35050; Sat, 20 Mar 1999 10:58:56 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903200958.KAA35050@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903200759.AAA16581@narnia.plutotech.com> from "Justin T. Gibbs" at "Mar 20, 1999 0:59:37 am" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Sat, 20 Mar 1999 10:58:56 +0100 (CET) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Justin T. Gibbs wrote: > In article <199903171205.NAA25764@freebsd.dk> you wrote: > > It seems David O'Brien wrote: > >> > Boot from an ata disk on major# 30, device name "ad", plain and simple. > >> > >> Does this mean ata disks won't come under CAM/da ? > > > > Not if I can help it :) > > It could be done by slamming a translation layer ontop of the existing > > wd driver or of cause on top of the new I'm doing, but all it adds > > is overhead, both performance wise and codesize wise. There is nothing > > that prohibits having both of cause, but it is not a priority for me > > to add more complexity into the picture before everything else is done. > > My main complaint so far about the new ATAPI stuff is that it duplicates > or lacks (assuming it will be implemented) much of what CAM would have > given for almost free: > > - Interrupt driven configuration That there allready, if we mean the same thing here. > - Peripheral driver to device routing Such as ? > - debugging/tracing facilities Well, there is a little of that allready, more to come. > - an extensible error recovery framework Well, here is room for improvement, I haven't put any real error checking code in there by now, it will just fail and report that for now. This is alpha level code remember. > - an understanding of command queuing (also relevant for ATAPI) Hmm, well, yes, but I'm not sure that what ATA/ATAPI has to offer here is comaptible with the CAM framwork. I plan to support tagged queueing on ATA disks though. > - understanding of hot plug events This really isn't an issue on ATA/ATAPI devices in most cases, but in the mobile world there is a need for this, but that is already being worked on. We need alot of work in other places in the kernel, before this can be really utilized though. > - an aplication pass-thru interface Hmm, what for ?? ATAPI commands could esily be passed through, but I'd like a driver to be in charge here, and besides we allready have drivers for most existing ATAPI HW. > The question about translation layers is secondary and I would likely > choose to not introduce a translation at all. Issuing pure ATAPI commands > to atapi devices at the peripheral driver level is somthing that CAM > could easily do. I would probably choose to merge ATAPI functionality > into the da driver to avoid duplicated code and to ensure that bug > fixes only need to be performed in one place. ATAPI has nothing to do in the da driver, well maybe for ZIP/LS120 drives, but disks are ATA, and that needs translation. > After all, the machinery > for talking to an ATAPI or SCSI disk is very similar (If the disk says > it needs to be spun up, spin it up; if we have too many transactions > outstanding and fear tag starvation, send an ordered tag; when we > close the disk or panic, synchronize its cache to stable media; etc. etc.) > even if the command op codes and format are slightly different. Thats correct, but there is enough differences that it still is a pain. > But hey, I don't have the time to work on ATAPI. Soren does, so he gets > to call the shots. Right :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 2: 1: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B970314CA8 for ; Sat, 20 Mar 1999 02:01:03 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id KAA35061; Sat, 20 Mar 1999 10:59:51 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903200959.KAA35061@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903200821.BAA21142@pluto.plutotech.com> from "Justin T. Gibbs" at "Mar 20, 1999 1:12:36 am" To: gibbs@plutotech.com (Justin T. Gibbs) Date: Sat, 20 Mar 1999 10:59:51 +0100 (CET) Cc: mike@smith.net.au, gibbs@plutotech.com, rnordier@nordier.com, 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 Justin T. Gibbs wrote: > >> In article <199903171103.NAA13749@ceia.nordier.com> you wrote: > >> > Søren Schmidt wrote: > >> > > >> >> OK, easy enough, this is what I want to do: > >> >> > >> >> Boot from an ata disk on major# 30, device name "ad", plain and simple. > >> > > >> > I'd be inclined to handle this outside the boot code, by treating the > >> > passed in major# as describing the device rather than specifying > >> > the driver. > >> > >> Why not have the boot blocks pass in a device 'name' rather than a > >> major number. If the goal is to ditch major numbers entirely with > >> a properly working DEVFS, then using major numbers in the new boot > >> loader seems to be the wrong way to go. Until DEVFS is a reality, > >> the kernel will still need to perform a name to major number translation, > >> but it should be left up to the kernel. > > > >Because there's no way to work out a name either. > > If I explicitly say: > > 1:foobar(0,a)/kernel > > there certainly is a way to work out the name. Perhaps in the autoboot > case you'll have to guess, but it would be nice if the current boot > mechanism allowed user intervention as a way to boot a kernel with an > unknown bdev. YES!! can we please have that ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 4:39:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-53-dbn.dial-up.net [196.34.155.117]) by hub.freebsd.org (Postfix) with ESMTP id 8B8F014F86 for ; Sat, 20 Mar 1999 04:39:44 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA22794; Sat, 20 Mar 1999 14:33:32 +0200 (SAT) From: Robert Nordier Message-Id: <199903201233.OAA22794@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903200959.KAA35061@freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 20, 99 10:59:51 am" To: sos@freebsd.dk (Søren Schmidt) Date: Sat, 20 Mar 1999 14:33:30 +0200 (SAT) Cc: gibbs@plutotech.com, mike@smith.net.au, rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Søren Schmidt wrote: > It seems Justin T. Gibbs wrote: > > >> Why not have the boot blocks pass in a device 'name' rather than a > > >> major number. If the goal is to ditch major numbers entirely with > > >> a properly working DEVFS, then using major numbers in the new boot > > >> loader seems to be the wrong way to go. Until DEVFS is a reality, > > >> the kernel will still need to perform a name to major number translation, > > >> but it should be left up to the kernel. > > > > > >Because there's no way to work out a name either. > > > > If I explicitly say: > > > > 1:foobar(0,a)/kernel > > > > there certainly is a way to work out the name. Perhaps in the autoboot > > case you'll have to guess, but it would be nice if the current boot > > mechanism allowed user intervention as a way to boot a kernel with an > > unknown bdev. > > YES!! can we please have that ?? Until DEVFS is a reality, I think it makes sense to not break compatibility with the existing boot interface. What Justin suggests seems good, but why not postpone the big change till the user has compelling reasons (like a working DEVFS) for making it, and losing ability to (a) boot 2.x and 3.x kernels; (b) use his existing bootblocks; and (c) use his existing netboot and other external (fbsdboot.exe-like) programs? For the short term, I'd suggest modifying the bootblocks to optionally accept an arbitrary major# in place of a {"wd", "da", "ad", "fd", ...} string 1:42(0,a)/kernel since that can easily be accommodated by the existing arguments passed to the kernel. While not an optimal solution, this does have the virtue of adding the ability to boot from any device not specifically provided for, and without requiring customization of the bootblocks (or any more work on the kernel than is presently required to add a device driver). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 4:45:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-53-dbn.dial-up.net [196.34.155.117]) by hub.freebsd.org (Postfix) with ESMTP id 11F2815667 for ; Sat, 20 Mar 1999 04:45:16 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA22815; Sat, 20 Mar 1999 14:39:38 +0200 (SAT) From: Robert Nordier Message-Id: <199903201239.OAA22815@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990319151430.A80525@luke.pmr.com> from Bob Willcox at "Mar 19, 99 03:14:30 pm" To: bob@pmr.com Date: Sat, 20 Mar 1999 14:39:36 +0200 (SAT) Cc: rnordier@nordier.com, sos@freebsd.dk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Willcox wrote: > I have an LS-120 and I'd be happy to test the new boot code with it. > > > Bob > Thanks very much. I'll contact you and Andrzej when the changes are made. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 4:56:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (Postfix) with ESMTP id B864814BCD for ; Sat, 20 Mar 1999 04:56:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.2/8.9.2/Netplex) with ESMTP id UAA45807; Sat, 20 Mar 1999 20:53:03 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199903201253.UAA45807@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt Cc: gibbs@narnia.plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 10:58:56 +0100." <199903200958.KAA35050@freebsd.dk> Date: Sat, 20 Mar 1999 20:53:02 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Justin T. Gibbs wrote: > > In article <199903171205.NAA25764@freebsd.dk> you wrote: > > > It seems David O'Brien wrote: > > >> > Boot from an ata disk on major# 30, device name "ad", plain and simple . > > >> > > >> Does this mean ata disks won't come under CAM/da ? > > > > > > Not if I can help it :) > > > It could be done by slamming a translation layer ontop of the existing > > > wd driver or of cause on top of the new I'm doing, but all it adds > > > is overhead, both performance wise and codesize wise. There is nothing > > > that prohibits having both of cause, but it is not a priority for me > > > to add more complexity into the picture before everything else is done. > > > > My main complaint so far about the new ATAPI stuff is that it duplicates > > or lacks (assuming it will be implemented) much of what CAM would have > > given for almost free: > > > > - Interrupt driven configuration > > That there allready, if we mean the same thing here. Exactly.. why reinvent it? It seems a little silly to reinvent the other stuff that cam provides that the ata[pi] driver hasn't finished yet. > > The question about translation layers is secondary and I would likely > > choose to not introduce a translation at all. Issuing pure ATAPI commands > > to atapi devices at the peripheral driver level is somthing that CAM > > could easily do. I would probably choose to merge ATAPI functionality > > into the da driver to avoid duplicated code and to ensure that bug > > fixes only need to be performed in one place. > > ATAPI has nothing to do in the da driver, well maybe for ZIP/LS120 > drives, but disks are ATA, and that needs translation. Yes, we know that IDE disks are ATA and not ATAPI, but the cam layer does have a lot of flexibility for dealing with differences even as large as that. You don't really need ``translation'' as such since a lot of the specifics are done by the backend driver and are a "black box" as far as the higher layers are concerned. You basically get to define the interface between cam and the drivers at your convenience. While the "da", "cd" etc upper level drivers do have scsi specific stuff in them (they are in the scsi subdir after all), they largely deal with generic CCB's (CAM Control Blocks) and send special scsi commands as required. Obviously these would need changing so they can send ATA or ATAPI commands instead. > > After all, the machinery > > for talking to an ATAPI or SCSI disk is very similar (If the disk says > > it needs to be spun up, spin it up; if we have too many transactions > > outstanding and fear tag starvation, send an ordered tag; when we > > close the disk or panic, synchronize its cache to stable media; etc. etc.) > > even if the command op codes and format are slightly different. > > Thats correct, but there is enough differences that it still is a > pain. You shouldn't ever have to "translate" a scsi CCB or SCSI command code into an ATAPI command or ATA command. A correctly functioning system would be sending the ata/atapi backend the in a form suitable for being used directly. > > But hey, I don't have the time to work on ATAPI. Soren does, so he gets > > to call the shots. > > Right :) Yes. Actually, the biggest problem wouldn't be building an ATA/ATAPI set of frontends and backends around the CAM system, I suspect it would be far harder to finish the generalization of the CAM code. There appear to be a lot of SCSI-specific things lurking in the cam* code... Things like the quirks table referring to T_DIRECT etc (which is from scsi/scsi_all.h) and so on. I half suspect that what Justin had in mind at some point was a set of common code that is either #ifdef'ed or otherwise preprocessed to produce a standalone 'SCSI-CAM' system versus an 'ATA[PI]-CAM' system. This would have the advantage of having all the common code together in one place and shared, while at compile time it built two seperate subsystems that were compiled specifically for the target peripheral bus with definitions to suit each so that "translation" was never used. > -Soren Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 5: 7:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 71EA014EAE for ; Sat, 20 Mar 1999 05:07:09 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA22172; Sat, 20 Mar 1999 14:06:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA08600; Sat, 20 Mar 1999 14:06:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Soren Schmidt , gibbs@narnia.plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 20:53:02 +0800." <199903201253.UAA45807@spinner.netplex.com.au> Date: Sat, 20 Mar 1999 14:06:48 +0100 Message-ID: <8598.921935208@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I half suspect that what Justin had in mind at some point was a set of common >code that is either #ifdef'ed or otherwise preprocessed to produce a >standalone 'SCSI-CAM' system versus an 'ATA[PI]-CAM' system. I .75 suspect that such a marriage would be caused by the second systems syndrome and carry no tangible benefits at the end of the day. I respect CAM, it seems to work out great. It also looks like sos driver does what it should so far. I don't see much point in merging the two for the benefits suggested so far. In particular I don't want to see sos and justin spend a lot of time haggeling over the issues for the rather meagre benefits cited so far. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 5:30:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.a2000.nl (farida.a2000.nl [62.108.1.19]) by hub.freebsd.org (Postfix) with ESMTP id 932C614DC7 for ; Sat, 20 Mar 1999 05:30:13 -0800 (PST) (envelope-from alexlh@funk.org) Received: from node1484.a2000.nl ([62.108.20.132] helo=funk.org) by farida.a2000.nl with esmtp (Exim 2.02 #4) id 10OLoX-0005Sy-00; Sat, 20 Mar 1999 14:29:21 +0100 Message-ID: <36F3A2B1.B9073220@funk.org> Date: Sat, 20 Mar 1999 14:29:21 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Steven P. Donegan" Cc: current@FreeBSD.ORG Subject: Re: IPSEC support? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven P. Donegan" wrote: > > Is there any IPSEC support available for current? I've found support for > 2.2.8, but not so far for current. There is support for 3.1-REL. Work is being done for -current, I believe. Keep an eye on http://www.r4k.net/ipsec Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.647' E4 51.555' | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 6:16:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 3D9C214DB8 for ; Sat, 20 Mar 1999 06:16:24 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id HAA66474; Sat, 20 Mar 1999 07:14:19 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903201414.HAA66474@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Soren Schmidt , gibbs@plutotech.com (Justin T. Gibbs), current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 20:53:02 +0800." <199903201253.UAA45807@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Mar 1999 07:05:18 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I half suspect that what Justin had in mind at some point was a set of common >code that is either #ifdef'ed or otherwise preprocessed to produce a >standalone 'SCSI-CAM' system versus an 'ATA[PI]-CAM' system. This would >have the advantage of having all the common code together in one place and >shared, while at compile time it built two seperate subsystems that were >compiled specifically for the target peripheral bus with definitions to >suit each so that "translation" was never used. The plan has always been to migrate the SCSI knowledge in the XPT layer into a 'personality' module leaving the generic portions of the CAM XPT intact. The personalities would be compiled in using the "atapibus0" and "scbus0" keywords in config. I don't think it would be that hard, but it would require time I don't have right now. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 6:32:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D115714FF7 for ; Sat, 20 Mar 1999 06:32:51 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id PAA16521; Sat, 20 Mar 1999 15:32:28 +0100 (CET) (envelope-from des) To: obrien@NUXI.com Cc: current@FreeBSD.ORG Subject: Re: panics while reading Solaris CDROM References: <19990319011117.A73322@relay.nuxi.com> From: Dag-Erling Smorgrav Date: 20 Mar 1999 15:32:28 +0100 In-Reply-To: "David O'Brien"'s message of "Fri, 19 Mar 1999 01:11:17 -0800" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > The core files from the panic seem to be useless -- I can't get anything > useful out of ``where'' with a kernel w/debugging symbols: Link CD9660 support statically, instead of using the KLD module. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 6:41:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from amethyst.bsdx.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id D103214F89; Sat, 20 Mar 1999 06:41:49 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from looksharp.net (localhost [127.0.0.1]) by amethyst.bsdx.net (8.9.3/8.9.1) with ESMTP id JAA19677; Sat, 20 Mar 1999 09:41:30 -0500 (EST) (envelope-from bsdx@looksharp.net) Message-ID: <36F3B399.59DB25A7@looksharp.net> Date: Sat, 20 Mar 1999 09:41:29 -0500 From: Adam McDougall X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: dillon@freebsd.org, current@freebsd.org Subject: reproducable panic? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to be able to reproduce a panic on my 4.0 machine (updated yesterday, kernel and world, also could crash with a somewhat older build) I have pseudo-device vn and nfs in my kernel, not as a module. When I vnconfig -c /dev/vn0c /nfsmountpoint/somefile, the system panics reliably. If there is more useful info I could give, or shell accounts, etc, please let me know. IdlePTD 3133440 initial pcb at 2701d8 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffffff68 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01af522 stack pointer = 0x10:0xc0252770 frame pointer = 0x10:0xc0252770 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01d99b0 stack pointer = 0x10:0xc02524cc frame pointer = 0x10:0xc02524d0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault dumping to dev 20401, offset 393216 dump 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:287 287 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:287 #1 0xc01486ed in panic (fmt=0xc024aad7 "page fault") at ../../kern/kern_shutdown.c:448 #2 0xc0210016 in trap_fatal (frame=0xc0252490, eva=48) at ../../i386/i386/trap.c:943 #3 0xc020fccf in trap_pfault (frame=0xc0252490, usermode=0, eva=48) at ../../i386/i386/trap.c:836 #4 0xc020f902 in trap (frame={tf_es = -1071316976, tf_ds = -1071710192, tf_edi = -1062680960, tf_esi = 0, tf_ebp = -1071307568, tf_isp = -1071307592, tf_ebx = -1071245808, tf_edx = -1073217472, tf_ecx = 0, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071801936, tf_cs = 8, tf_eflags = 66178, tf_esp = -1036656256, tf_ss = -1071307536}) at ../../i386/i386/trap.c:438 #5 0xc01d99b0 in acquire_lock (lk=0xc0261610) at ../../ufs/ffs/ffs_softdep.c:267 #6 0xc01dc827 in initiate_write_inodeblock (inodedep=0xc0a8c680, bp=0xc1e8f398) at ../../ufs/ffs/ffs_softdep.c:2827 #7 0xc01dc5cf in softdep_disk_io_initiation (bp=0xc1e8f398) at ../../ufs/ffs/ffs_softdep.c:2686 #8 0xc017992a in spec_strategy (ap=0xc0252550) at ../../miscfs/specfs/spec_vnops.c:555 #9 0xc01790bd in spec_vnoperate (ap=0xc0252550) at ../../miscfs/specfs/spec_vnops.c:129 #10 0xc01e7af5 in ufs_vnoperatespec (ap=0xc0252550) at ../../ufs/ufs/ufs_vnops.c:2327 #11 0xc0166a67 in bwrite (bp=0xc1e8f398) at vnode_if.h:891 #12 0xc016b1f6 in vop_stdbwrite (ap=0xc02525b8) at ../../kern/vfs_default.c:297 #13 0xc016b041 in vop_defaultop (ap=0xc02525b8) at ../../kern/vfs_default.c:131 #14 0xc01790bd in spec_vnoperate (ap=0xc02525b8) at ../../miscfs/specfs/spec_vnops.c:129 #15 0xc01e7af5 in ufs_vnoperatespec (ap=0xc02525b8) at ../../ufs/ufs/ufs_vnops.c:2327 #16 0xc01674c7 in vfs_bio_awrite (bp=0xc1e8f398) at vnode_if.h:1145 #17 0xc01e1b46 in ffs_fsync (ap=0xc0252640) at ../../ufs/ffs/ffs_vnops.c:205 #18 0xc01dffe7 in ffs_sync (mp=0xc0a04a00, waitfor=2, cred=0xc0a1ff00, p=0xc028c8e0) at vnode_if.h:499 #19 0xc016fc2b in sync (p=0xc028c8e0, uap=0x0) at ../../kern/vfs_syscalls.c:542 #20 0xc0148299 in boot (howto=256) at ../../kern/kern_shutdown.c:205 #21 0xc01486ed in panic (fmt=0xc024aad7 "page fault") at ../../kern/kern_shutdown.c:448 #22 0xc0210016 in trap_fatal (frame=0xc0252734, eva=4294967144) at ../../i386/i386/trap.c:943 #23 0xc020fccf in trap_pfault (frame=0xc0252734, usermode=0, eva=4294967144) at ../../i386/i386/trap.c:836 #24 0xc020f902 in trap (frame={tf_es = -989003760, tf_ds = 528089104, tf_edi = -1073741824, tf_esi = -982050144, tf_ebp = -1071306896, tf_isp = -1071306916, tf_ebx = -1062665024, tf_edx = -152, tf_ecx = -982050144, tf_eax = -2147483648, tf_trapno = 12, tf_err = 0, tf_eip = -1071975134, tf_cs = 8, tf_eflags = 66182, tf_esp = -1071306860, tf_ss = -1071975907}) at ../../i386/i386/trap.c:438 #25 0xc01af522 in nfs_sigintr (nmp=0xc5771aa0, rep=0xc0a904c0, p=0xc0133634) at ../../nfs/nfs_socket.c:1479 #26 0xc01af21d in nfs_timer (arg=0x0) at ../../nfs/nfs_socket.c:1355 #27 0xc014cb8e in softclock () at ../../kern/kern_timeout.c:132 (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 7:41: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from cartman.weeble.nws.net (ubppp233-249.dialin.buffalo.edu [128.205.233.249]) by hub.freebsd.org (Postfix) with ESMTP id 7F57414C37; Sat, 20 Mar 1999 07:41:04 -0800 (PST) (envelope-from cjm2@earthling.net) Received: from maxpower (ip-10.dynip.weeble.nws.net [10.0.0.10]) by cartman.weeble.nws.net (8.8.8/8.8.8) with SMTP id KAA00463; Sat, 20 Mar 1999 10:40:45 -0500 (EST) (envelope-from cjm2@earthling.net) From: "Christopher J. Michaels" To: "'FreeBSD Mailing List (E-mail)'" Cc: "'Alexander N Shulyak'" , Subject: RE: unable to use cdrecord on an ATAPI CD-R under 2.2.8. Date: Sat, 20 Mar 1999 10:40:45 -0500 Message-ID: <000101be72e8$061d1160$0a00000a@maxpower.weeble.nws.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <000001be72e1$e98ea3c0$0a00000a@maxpower.weeble.nws.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I'm sorry to say that it looks like I've found the answer to my own question. I found after this posting (by looking at dmesg) that I was getting the following error. acd0: rezero failed I did some searching and found several postings in -current that said my drive, a MITSUMI CR-2600TE, does not support the REZERO command and is therefore not going to work, at least with the acd driver I have running now. Now my question is, and this is why I'm cc:ing this to -current is, has this particular problem been addressed in the current release(s) of FreeBSD. The thread that addressed this particular issue (in -current) was about 5 months old. Incase anyone was interested the URL to that thread is.. http://www.freebsd.org/cgi/getmsg.cgi?fetch=1249191+1251848+/usr/local/www/d b/text/1998/freebsd-current/19981108.freebsd-current Thanks again, guess I'll be putting the burner back in the winblowz 98 machine unless someone can help me out with a fix. -Chris -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Christopher J. Michaels Sent: Saturday, March 20, 1999 9:57 AM To: FreeBSD Mailing List (E-mail) Subject: unable to use cdrecord on an ATAPI CD-R under 2.2.8. Hello, I'm trying to use my ATAPI cd-r on my 2.2.8 box and am having no success at all. I have the acd device in my kernel and it detects just fine upone startup. And I can mount /dev/wcd0c just fine. acd0: drive speed 1377KB/sec, 2048KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: supported write types: CD-R, test write acd0: Audio: play, 2 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked I have tried to use the cdrecord's -scanbus option to try and get starting and what I get is the following... Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jörg Schilling cdrecord: No such file or directory. Cannot open SCSI driver. Ok, it uses /dev/scgx, so I did 'ln -s /dev/rcd0.ctl /dev/scgx' and I still get the above error. So NOW i'm trying to specify the device name on the command line, as it says on the man page I can do. 'cdrecord -scanbus dev=/dev/rcd0.ctl:0,4,0' Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jörg Schilling scsidev: '/dev/rcd0.ctl:0,4,0' devname: '/dev/rcd0.ctl' scsibus: 0 target: 4 lun: 0 cdrecord: Device not configured. Cannot open SCSI driver. If i try similar things such as /dev/rcd0a, /dev/rcd0c, I get the same above error. I've tried MAKEDEV wcd0, acd0, rcd0. With no luck.. MAKEDEV doesn't even recognize acd0. SO, I'm out of ideas, I know others out there are using this thing because I see enough traffic on the mailing list. But does anyone out there know how to help me with this issue? -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 7:58:33 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 1CE0214FAD for ; Sat, 20 Mar 1999 07:58:27 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA20796; Sun, 21 Mar 1999 00:55:30 +0900 (JST) Message-ID: <36F3C0D9.5ED2C3F4@newsguy.com> Date: Sun, 21 Mar 1999 00:38:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: =?iso-8859-1?Q?S=F8ren?= Schmidt Cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <199903200959.KAA35061@freebsd.dk> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "S=F8ren Schmidt" wrote: > = > > there certainly is a way to work out the name. Perhaps in the autobo= ot > > case you'll have to guess, but it would be nice if the current boot > > mechanism allowed user intervention as a way to boot a kernel with an= > > unknown bdev. > = > YES!! can we please have that ?? As I said before, loader can pass arbitrary parameters to the kernel. I did not answer to the jab you replied with before because I was waiting for Mike's comments. In any case, all environment strings defined in the loader are (for now) copied so kernel can use them. Pick a name, and DTRT in the kernel. Alternatively, arguments to either "boot" or "load kernel" commands are passed on to the kernel. Again, it's just a matter of you using it. The major number passed to the kernel is a product of a lot of guesswork, because the loader has simply not enough information. I have added a bit of code to my version of loader so you can use the variable root_device_major_number to override the major number to be passed to the kernel. I'm inclined to commit it, but I expect strong objections from Mike, who wants the right thing done before we go too far with these hacks. (I can send this patch to you as soon as you answer to my message concerning the problems I'm having with the ad stuff... :) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 8:19:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id DBC28150FF for ; Sat, 20 Mar 1999 08:19:17 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id QAA78820; Sat, 20 Mar 1999 16:18:51 GMT (envelope-from green@zone.syracuse.net) Date: Sat, 20 Mar 1999 16:18:50 +0000 (GMT) From: Brian Feldman To: Brian Feldman Cc: Thomas Dean , current@FreeBSD.ORG Subject: Re: fd broken [!!!] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been a couple more weeks, anyone now know why fd(4) is broken? It's really not a good thing :( Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ On Tue, 9 Mar 1999, Brian Feldman wrote: > On Sat, 6 Mar 1999, Thomas Dean wrote: > So Does anyone have an idea why the hell fd(4) broke?! > > > I have the same problem on 4.0-current SMP of Mon Feb 15 03:34:29 PST > > 1999. > > > > tomdean > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 8:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5AA0414DD6 for ; Sat, 20 Mar 1999 08:55:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id IAA31293; Sat, 20 Mar 1999 08:55:08 -0800 (PST) (envelope-from obrien) Date: Sat, 20 Mar 1999 08:55:08 -0800 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: panics while reading Solaris CDROM Message-ID: <19990320085508.A81369@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <19990319011117.A73322@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, Mar 20, 1999 at 03:32:28PM +0100 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The core files from the panic seem to be useless -- I can't get anything > > useful out of ``where'' with a kernel w/debugging symbols: > > Link CD9660 support statically, instead of using the KLD module. First thing I tried. :-) Bruce's vfs_bio.c fix was the trick. -- -- 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 Sat Mar 20 9: 5: 4 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 B709614FD1 for ; Sat, 20 Mar 1999 09:05:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA06958; Sat, 20 Mar 1999 09:04:30 -0800 (PST) (envelope-from dillon) Date: Sat, 20 Mar 1999 09:04:30 -0800 (PST) From: Matthew Dillon Message-Id: <199903201704.JAA06958@apollo.backplane.com> To: Adam McDougall Cc: current@FreeBSD.ORG Subject: Re: reproducable panic? References: <36F3B399.59DB25A7@looksharp.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I seem to be able to reproduce a panic on my 4.0 machine (updated :yesterday, kernel and world, also could crash with a somewhat older :build) : :I have pseudo-device vn and nfs in my kernel, not as a module. : :When I vnconfig -c /dev/vn0c /nfsmountpoint/somefile, the system panics :reliably. : :If there is more useful info I could give, or shell accounts, etc, :please let me know. test2:/home/dillon# ls -la /var/tmp/ff/test -rw-r--r-- 1 root wheel 33554432 Mar 20 09:01 /var/tmp/ff/test test2:/home/dillon# vnconfig -c /dev/vn2c /var/tmp/ff/test test2:/home/dillon# df apollo:/images/remote.src 1397423 970331 315299 75% /var/tmp/ff Works for me. If you have the latest updated yesterday you should be in good shape. See if you can narrow down why it is crashing... try different file sizes for your /nfsmountpoint/somefile, and so forth. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 10:22: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (sil-wa15-07.ix.netcom.com [207.93.148.7]) by hub.freebsd.org (Postfix) with ESMTP id 322A1150C5 for ; Sat, 20 Mar 1999 10:22:04 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id KAA04931; Sat, 20 Mar 1999 10:21:49 -0800 (PST) (envelope-from tomdean) Date: Sat, 20 Mar 1999 10:21:49 -0800 (PST) Message-Id: <199903201821.KAA04931@ix.netcom.com> From: Thomas Dean To: green@unixhelp.org, current@FreeBSD.ORG In-reply-to: (message from Brian Feldman on Sat, 20 Mar 1999 16:18:50 +0000 (GMT)) Subject: Re: fd broken [!!!] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I submitted a PR. This is not a show-stopper. I have a system running 2.2.7. fd works on that one. So, I read/write floppies there. It is a pain, though. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 10:49:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from ruby.bsdx.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 8115E14DA3 for ; Sat, 20 Mar 1999 10:49:56 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by ruby.bsdx.net (8.9.3/8.9.1) with SMTP id NAA98203; Sat, 20 Mar 1999 13:49:37 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Sat, 20 Mar 1999 13:49:36 -0500 (EST) From: Adam X-Sender: bsdx@ruby To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: reproducable panic? In-Reply-To: <199903201704.JAA06958@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 Ok I've been playing around a bit, an iso sized file (500-600mb) seems to trigger it, and a quite small file seemed to do it too but I forgot which one, but just now I made a one byte file and vnconfig'ed it and that paniced. Please try that if you can :) btw I tried a 32mb file like you, also a 16mb one, and neither made it crash. Thanks On Sat, 20 Mar 1999, Matthew Dillon wrote: > :I seem to be able to reproduce a panic on my 4.0 machine (updated > :yesterday, kernel and world, also could crash with a somewhat older > :build) > : > :I have pseudo-device vn and nfs in my kernel, not as a module. > : > :When I vnconfig -c /dev/vn0c /nfsmountpoint/somefile, the system panics > :reliably. > : > :If there is more useful info I could give, or shell accounts, etc, > :please let me know. > > > test2:/home/dillon# ls -la /var/tmp/ff/test > -rw-r--r-- 1 root wheel 33554432 Mar 20 09:01 /var/tmp/ff/test > test2:/home/dillon# vnconfig -c /dev/vn2c /var/tmp/ff/test > test2:/home/dillon# df > apollo:/images/remote.src 1397423 970331 315299 75% /var/tmp/ff > > Works for me. If you have the latest updated yesterday you should be > in good shape. See if you can narrow down why it is crashing... try > different file sizes for your /nfsmountpoint/somefile, and so forth. > > -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 Sat Mar 20 11: 6:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 6AC9A14F7F for ; Sat, 20 Mar 1999 11:06:18 -0800 (PST) (envelope-from green@zone.syracuse.net) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id TAA82221; Sat, 20 Mar 1999 19:05:28 GMT (envelope-from green@zone.syracuse.net) Date: Sat, 20 Mar 1999 19:05:28 +0000 (GMT) From: Brian Feldman To: Thomas Dean Cc: green@unixhelp.org, current@FreeBSD.ORG Subject: Re: fd broken [!!!] In-Reply-To: <199903201821.KAA04931@ix.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aye, and my LS-120 works great too :) So, que sera sera. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ On Sat, 20 Mar 1999, Thomas Dean wrote: > I submitted a PR. > > This is not a show-stopper. I have a system running 2.2.7. fd works > on that one. So, I read/write floppies there. It is a pain, though. > > tomdean > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 11:37:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles95.castles.com [208.214.165.95]) by hub.freebsd.org (Postfix) with ESMTP id 5BC9514F93 for ; Sat, 20 Mar 1999 11:36:33 -0800 (PST) (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 LAA12494 for ; Sat, 20 Mar 1999 11:30:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903201930.LAA12494@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 10:58:56 +0100." <199903200958.KAA35050@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Mar 1999 11:30:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But hey, I don't have the time to work on ATAPI. Soren does, so he g= ets > > to call the shots. > = > Right :) =2E.. so we lose. 8( Soren, please take a little time to understand what Justin is talking = about. The parts of CAM that are relevant to you are the queueing = support, infrastructure, and the separation between the "interface = controller" and the "peripheral driver", something that you've = indicated to me several times that you simply don't grasp. Taking advantage of all the code and design that's already been = implemented in the CAM framework will make your life easier, not = harder. It's not necessary to write a translation layer at all, if = such a thing offends your sensibilities. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 11:52:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles95.castles.com [208.214.165.95]) by hub.freebsd.org (Postfix) with ESMTP id AA79D14C2F for ; Sat, 20 Mar 1999 11:52:11 -0800 (PST) (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 LAA12569; Sat, 20 Mar 1999 11:44:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903201944.LAA12569@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: =?iso-8859-1?Q?S=F8ren?= Schmidt , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sun, 21 Mar 1999 00:38:01 +0900." <36F3C0D9.5ED2C3F4@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Mar 1999 11:44:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The major number passed to the kernel is a product of a lot of > guesswork, because the loader has simply not enough information. I > have added a bit of code to my version of loader so you can use the > variable root_device_major_number to override the major number to be > passed to the kernel. I'm inclined to commit it, but I expect strong > objections from Mike, who wants the right thing done before we go > too far with these hacks. Correct. I'm currently leaning heavily towards a tunable which can be set to = explicitly control the device the root filesystem is loaded from, eg. set kern.rootdev.device=3Dda0s1a However Justin's random number comment speaks back to a technique I was = working on earlier, where such a number would be secreted in the = disklabel of the disk to be booted. This number would have to be = generated in a fairly unique fashion (I planned to use the TOD to try = to keep it from wrapping), and it'd then be passed in in the = environment or as an argument to the kernel. Bruce really doesn't like the environment, preferring instead arguments = to modules. This breaks down as soon as you try to set things = automatically (which module needs which arguments?) or load things = automatically as a result of dependancies (how do you pass arguments to = something that's loaded invisibly?). So in this case the code would set kern.rootdev.brand to the magic = number, and the kernel would then search for it. However, there's another technique which would work quite well, and one = I'm actually moderately enamoured of (modulo it's ability to confuse = the heck out of people). Use the "last mounted on" field to find and mount filesystems. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 12:21:17 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 B149314CE4 for ; Sat, 20 Mar 1999 12:21:15 -0800 (PST) (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.1/8.9.1) with ESMTP id PAA08940; Sat, 20 Mar 1999 15:19:08 -0500 (EST) Message-Id: <199903202019.PAA08940@cs.rpi.edu> To: Mike Smith Cc: "Daniel C. Sobral" , =?iso-8859-1?Q?S=F8ren?= Schmidt , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: Message from Mike Smith of "Sat, 20 Mar 1999 11:44:20 PST." <199903201944.LAA12569@dingo.cdrom.com> Date: Sat, 20 Mar 1999 15:19:07 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The major number passed to the kernel is a product of a lot of > > guesswork, because the loader has simply not enough information. I > > have added a bit of code to my version of loader so you can use the > > variable root_device_major_number to override the major number to be > > passed to the kernel. I'm inclined to commit it, but I expect strong > > objections from Mike, who wants the right thing done before we go > > too far with these hacks. > > Correct. > > I'm currently leaning heavily towards a tunable which can be set to > explicitly control the device the root filesystem is loaded from, eg. > > set kern.rootdev.device=da0s1a How hard would it be to have /boot/loader get the major number from the filesystem itself? Just have it read the node entry for /dev/$rootdev (or similiar). -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 12:26:40 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 305EC14C10 for ; Sat, 20 Mar 1999 12:26:37 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA07600; Sun, 21 Mar 1999 05:23:49 +0900 (JST) Message-ID: <36F40375.624C03D0@newsguy.com> Date: Sun, 21 Mar 1999 05:22:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: =?iso-8859-1?Q?S=F8ren?= Schmidt , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? References: <199903201944.LAA12569@dingo.cdrom.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 Mike Smith wrote: > > > The major number passed to the kernel is a product of a lot of > > guesswork, because the loader has simply not enough information. I > > have added a bit of code to my version of loader so you can use the > > variable root_device_major_number to override the major number to be > > passed to the kernel. I'm inclined to commit it, but I expect strong > > objections from Mike, who wants the right thing done before we go > > too far with these hacks. > > Correct. On both accounts, I suppose... :-) > However Justin's random number comment speaks back to a technique I was > working on earlier, where such a number would be secreted in the > disklabel of the disk to be booted. This number would have to be > generated in a fairly unique fashion (I planned to use the TOD to try > to keep it from wrapping), and it'd then be passed in in the > environment or as an argument to the kernel. How would that work with netboot or booting from foreign fs, such as FAT? If we restrict ourselves to disklabel-carrying fs, an alternative would be writing the date&time plus a semi-random number (such as time down to ms) on the disklabel of the disk selected, and passing this number to the kernel. [reads what you said again] Unless, of course, that's precisely what you are talking about... :-) I'm not sure if you are talking about a pre-generated label, or one written at boot time. It all rests on the meaning of TOD (tentatively translated as Time Of Day... :). > However, there's another technique which would work quite well, and one > I'm actually moderately enamoured of (modulo it's ability to confuse > the heck out of people). > > Use the "last mounted on" field to find and mount filesystems. Again, same objections... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 12:28:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles95.castles.com [208.214.165.95]) by hub.freebsd.org (Postfix) with ESMTP id A98E91530D for ; Sat, 20 Mar 1999 12:28:34 -0800 (PST) (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 MAA12835; Sat, 20 Mar 1999 12:20:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903202020.MAA12835@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: Mike Smith , "Daniel C. Sobral" , =?iso-8859-1?Q?S=F8ren?= Schmidt , current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 15:19:07 EST." <199903202019.PAA08940@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Mar 1999 12:20:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The major number passed to the kernel is a product of a lot of > > > guesswork, because the loader has simply not enough information. I > > > have added a bit of code to my version of loader so you can use the > > > variable root_device_major_number to override the major number to be > > > passed to the kernel. I'm inclined to commit it, but I expect strong > > > objections from Mike, who wants the right thing done before we go > > > too far with these hacks. > > > > Correct. > > > > I'm currently leaning heavily towards a tunable which can be set to > > explicitly control the device the root filesystem is loaded from, eg. > > > > set kern.rootdev.device=da0s1a > > How hard would it be to have /boot/loader get the major number from the > filesystem itself? Just have it read the node entry for /dev/$rootdev > (or similiar). This doesn't solve the BIOS : FreeBSD unit numbering problem, unfortunately, and it would make moving from one driver to another very difficult (you'd have to override the search). It's a neat idea and one I hadn't thought of, but it doesn't solve enough of the problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 12:43:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from kong.dorms.spbu.ru (kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (Postfix) with ESMTP id 8A2B714C08 for ; Sat, 20 Mar 1999 12:43:25 -0800 (PST) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.9.3/0.0.1/kong) with ESMTP id XAA41953 for ; Sat, 20 Mar 1999 23:41:19 +0300 (MSK) (envelope-from kong@kong.dorms.spbu.ru) Date: Sat, 20 Mar 1999 23:41:18 +0300 (MSK) From: Hostas Red To: current@freebsd.org Subject: broken world 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! For a couple weeks for now i have a broken world with following reason: ===> usr.sbin/i4b/isdnd cc -O -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor -I/usr/src/usr.sbin/i4b/isdnd/../isdntel -I/usr/obj/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES -I/usr/obj/usr/src/tmp/usr/include -c rc_scan.c /usr/src/usr.sbin/i4b/isdnd/rc_scan.l: In function `yylex': /usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: `BEEPCONNECT' undeclared (first use this function) /usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: (Each undeclared identifier is reported only once /usr/src/usr.sbin/i4b/isdnd/rc_scan.l:95: for each function it appears in.) /usr/src/usr.sbin/i4b/isdnd/rc_scan.l:111: `IDLE_ALG_OUT' undeclared (first use this function) *** Error code 1 Cleaning obj tree doesn't helps. Nothing helps, so. Anybody have similar problems? Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 15:51:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 499D215181 for ; Sat, 20 Mar 1999 15:51:05 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id RAA04895 for ; Sat, 20 Mar 1999 17:50:46 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <004001be732c$7960e0e0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "FreeBSD-Current" Subject: Possible fix for rc.conf Date: Sat, 20 Mar 1999 17:50:46 -0600 Organization: West Bend Internet 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 What does everyone think about using this at the end of /etc/defaults/rc.conf? for i in ${rc_conf_files}; do if [ $0 != $i ]; then if [ -f $i ]; then . $i fi else echo "Error: $0 isn't allowed to re-load $i." echo "Error: Please do not copy /etc/defaults/rc.conf to /etc/rc.conf" fi done If someone does copy the /etc/defaults/rc.conf to /etc/rc.conf, /etc/rc.conf will not reload it's self, thus it will never get stuck in an endless loop. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 16:52:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 8FFD614F8A for ; Sat, 20 Mar 1999 16:52:15 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from waltz.rahul.net by bolero-x.rahul.net with SMTP id AA14345 (5.67b8/IDA-1.5 for ); Sat, 20 Mar 1999 16:51:54 -0800 From: Rahul Dhesi Received: by waltz.rahul.net (5.67b8/jive-a2i-1.0) id AA04294; Sat, 20 Mar 1999 16:51:53 -0800 Date: Sat, 20 Mar 1999 16:51:53 -0800 Message-Id: <199903210051.AA04294@waltz.rahul.net> To: freebsd-current@freebsd.org Subject: Re: Possible fix for rc.conf Newsgroups: a2i.lists.freebsd-current References: X-Newsreader: NN version 6.5.1 (NOV) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Scot W. Hetzel" writes: > if [ $0 != $i ]; then A more generic fix is for each script to set an environment variable, and check to make sure that variable was not set already. Analogous to how C include files prevent recursive inclusion. -- Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 17:11:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 48BBD14E26 for ; Sat, 20 Mar 1999 17:11:08 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id SAA77557; Sat, 20 Mar 1999 18:09:46 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903210109.SAA77557@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: S ren Schmidt Cc: gibbs@plutotech.com (Justin T. Gibbs), current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Sat, 20 Mar 1999 10:58:56 +0100." <199903200958.KAA35050@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sat, 20 Mar 1999 18:00:45 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My main complaint so far about the new ATAPI stuff is that it duplicat= es >> or lacks (assuming it will be implemented) much of what CAM would have= >> given for almost free: >> = >> - Interrupt driven configuration > >That there allready, if we mean the same thing here. Right. Its duplicated functionality. >> - Peripheral driver to device routing > >Such as ? Such as the ability to have more than one driver share the same device, command generation counts and priority queuing to allow correct 'replay' of overlapped commands when an error occurs, etc. See: http://www.freebsd.org/~gibbs/cam.html for the start of a discussion of these features and why transaction routing was implemented this way. >> - debugging/tracing facilities >Well, there is a little of that allready, more to come. Right. Its duplicated functionality. >> - an extensible error recovery framework > >Well, here is room for improvement, I haven't put any real error >checking code in there by now, it will just fail and report that >for now. This is alpha level code remember. But how will you deal with errors especially when there are overlapped commands? CAM already deals with this in a very clean way. When an error= occurs, the controller driver freezes the queue of commands to the erring= device, notifies the peripheral driver of the error, and allows the drive= r to insert error recovery actions before any other commands are ever released to the device. This even allows you to toss back unexecuted but= queued commands at the controller level to be reinserted into the transpo= rt layer's command queue to ensure proper ordering. This all plays off of t= he priority features inherent in how transactions are queued. Command queuing was a major factor in why I wrote the CAM code. Solving these issues is not trivial. >> - an understanding of command queuing (also relevant for ATAPI) > >Hmm, well, yes, but I'm not sure that what ATA/ATAPI has to offer = >here is comaptible with the CAM framwork. I plan to support tagged >queueing on ATA disks though. CAM only knows that multiple commands may be outstanding at a time and that they must be marked with serial numbers for proper replay when an error occurs. The specifics of how multiple transactions are specified is something that can be completely isolated into the 'personality' module and as a protocol between the peripheral drivers and the controller drivers. >> - understanding of hot plug events > >This really isn't an issue on ATA/ATAPI devices in most cases, >but in the mobile world there is a need for this, but that is >already being worked on. We need alot of work in other places >in the kernel, before this can be really utilized though. So why invent a new notification and cleanup strategy when the CAM one has already been developed and tested in the SCSI world? >> - an aplication pass-thru interface > >Hmm, what for ?? cdrecord, a userland disk format utility, camcontrol functionality, etc. etc. >ATAPI commands could esily be passed through, but I'd like a >driver to be in charge here, and besides we allready have drivers >for most existing ATAPI HW. The pass-thru driver is in charge in the CAM world. Is this not sufficient? Sure, there needs to be locking primitives so that drivers competing for the same device do not step on each others toes, but this is already specified by CAM and should be only a day or so of effort to implement. >ATAPI has nothing to do in the da driver, well maybe for ZIP/LS120 >drives, but disks are ATA, and that needs translation. Why does it need translation? Why not simply issue ATA commands right through the CAM Transport layer. Perhaps you use a function table in you= r peripheral driver to build the right CAM Control Blocks to send for a particular device. Perhaps you have a completely different peripheral driver for ATA and SCSI devices. That is up to the implementor. My choi= ce would be to have one peripheral driver here, but CAM doesn't tie your han= ds one way or the other. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 19:55:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id E798F14E69 for ; Sat, 20 Mar 1999 19:55:24 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 ([207.164.233.99]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id AAA14821 for ; Sun, 21 Mar 1999 00:11:35 -0500 Message-ID: <000101be734e$00eb0c40$63e9a4cf@a35.my.intranet> From: "RT" To: Subject: NetBoot & 3Com card. Date: Sat, 20 Mar 1999 22:50:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a couple of 905B 3com cards. I'm interested in running diskless (especially since a harddisk in the one machine just died). After reading the handbook, I found the diskless information to be extreamly outdated. Does netboot now support the 905 line of 3com cards? (Any test drivers out there for it?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 19:56:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-9.ppp.wenet.net [206.15.85.9]) by hub.freebsd.org (Postfix) with ESMTP id 47D0B1503C for ; Sat, 20 Mar 1999 19:55:34 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id TAA65514; Sat, 20 Mar 1999 19:55:03 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 20 Mar 1999 19:55:02 -0800 (PST) From: Alex Zepeda To: "Scot W. Hetzel" Cc: FreeBSD-Current Subject: Re: Possible fix for rc.conf In-Reply-To: <004001be732c$7960e0e0$8dfee0d1@westbend.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 Sat, 20 Mar 1999, Scot W. Hetzel wrote: > If someone does copy the /etc/defaults/rc.conf to /etc/rc.conf, /etc/rc.conf > will not reload it's self, thus it will never get stuck in an endless loop. Oh it's too late for that. :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 20: 5:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 5E5E214C92; Sat, 20 Mar 1999 20:05:13 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts4-11-ppp.ipass.net [207.120.205.11]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id XAA28893; Sat, 20 Mar 1999 23:04:50 -0500 (EST) Message-ID: <36F4707E.E7A6D897@ipass.net> Date: Sat, 20 Mar 1999 23:07:27 -0500 From: "Michael E. Mercer" Reply-To: samit@usa.ltindia.com X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: rfork() Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, This was posted to freebsd-questions with no reply. I tried this and the child process created a core file. I also tried the other options and they seem to work. Just RFPROC and RFMEM DON'T! Thanks, Michael Mercer -------------------- Can any one suggest how to use rfork( RFPROC | RFMEM ); according to the manual, freeBSD supports this and it should create a new process which will share the address space. But what I'm getting is a) It returns only to the parent process with a childID. b) It doesn't go into child part c) 'PS' shows that a child process is active. Code: #include main() { int childId; printf("Parent Process start \n"); if ( (childId = rfork(RFMEM | RFPROC) ) == 0 ) { printf("In Child childId(%d) PId(%d)\n", childId,getpid() ); sleep(4); exit(0); } { char buf[10] = "Samit"; int nRet; printf("Parent process continues with childId(%d) %s,PID(%d)\n", childId, buf,getpid()); sleep(5); } } Output: $ cc test.c $ a.out & $ Parent Process start Parent process continues with childId(10759) Samit,PID(10758) ps PID TT STAT TIME COMMAND 10697 p2 Ss 0:00.07 -sh (sh) 10758 p2 S 0:00.00 a.out 10759 p2 Z 0:00.00 (a.out) 10760 p2 R+ 0:00.00 ps why it is created zombie and it does not execute the code ? --Samit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 20:13: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id F31A1150FF for ; Sat, 20 Mar 1999 20:12:57 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 1530 invoked from network); 21 Mar 1999 04:12:36 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 21 Mar 1999 04:12:36 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.3/8.9.1) id XAA04326; Sat, 20 Mar 1999 23:12:35 -0500 (EST) Message-Id: <199903210412.XAA04326@y.dyson.net> Subject: Re: rfork() In-Reply-To: <36F4707E.E7A6D897@ipass.net> from "Michael E. Mercer" at "Mar 20, 99 11:07:27 pm" To: samit@usa.ltindia.com Date: Sat, 20 Mar 1999 23:12:35 -0500 (EST) Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael E. Mercer said: > Hello, > > This was posted to freebsd-questions with no reply. > I tried this and the child process created a core file. > I also tried the other options and they seem to work. > Just RFPROC and RFMEM DON'T! > rfork(RFMEM) doesn't easily work from C. You need to create an assembly stub. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 20:21:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 60BCB14C92; Sat, 20 Mar 1999 20:21:29 -0800 (PST) (envelope-from mmercer@ipass.net) Received: from ipass.net (ts4-11-ppp.ipass.net [207.120.205.11]) by pluto.ipass.net (8.9.1a/8.9.1) with ESMTP id XAA00437; Sat, 20 Mar 1999 23:20:58 -0500 (EST) Message-ID: <36F47446.E67A7602@ipass.net> Date: Sat, 20 Mar 1999 23:23:34 -0500 From: "Michael E. Mercer" Reply-To: mmercer@ipass.net X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: dyson@iquest.net Cc: samit@usa.ltindia.com, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: rfork() References: <199903210412.XAA04326@y.dyson.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, With very little experience in assembly, could you or someone else give me a small example? Thanks in advance, Michael Mercer "John S. Dyson" wrote: > > Michael E. Mercer said: > > Hello, > > > > This was posted to freebsd-questions with no reply. > > I tried this and the child process created a core file. > > I also tried the other options and they seem to work. > > Just RFPROC and RFMEM DON'T! > > > rfork(RFMEM) doesn't easily work from C. You need to > create an assembly stub. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 21: 0: 5 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 6C8F114D17; Sat, 20 Mar 1999 21:00:02 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id AAA03934; Sun, 21 Mar 1999 00:04:21 -0500 (EST) Date: Sun, 21 Mar 1999 00:04:20 -0500 (EST) From: Alfred Perlstein To: "John S. Dyson" Cc: samit@usa.ltindia.com, commiters@freebsd.org, freebsd-current@freebsd.org Subject: Re: rfork() In-Reply-To: <199903210412.XAA04326@y.dyson.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 Mar 1999, John S. Dyson wrote: > Michael E. Mercer said: > > Hello, > > > > This was posted to freebsd-questions with no reply. > > I tried this and the child process created a core file. > > I also tried the other options and they seem to work. > > Just RFPROC and RFMEM DON'T! > > > rfork(RFMEM) doesn't easily work from C. You need to > create an assembly stub. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. > I've seen about 6 people ask about this because the manual lies about what is done. I asked a while back about it, and John was kind enough to dig up some code that used rfork to properly split the stack should I try to dig it up? In the meantime, can someone commit this or suggest something? thanks, -Alfred Index: rfork.2 =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/rfork.2,v retrieving revision 1.8 diff -u -r1.8 rfork.2 --- rfork.2 1999/01/26 02:38:09 1.8 +++ rfork.2 1999/03/21 04:49:10 @@ -54,7 +54,8 @@ will then inherit all the shared segments the parent process owns. Other segment types will be unaffected. Subsequent forks by the parent will then propagate the shared data and bss between children. The stack segment -is always split. May be set only with +is not split and must be allocated manually via an assembler subroutine. +May be set only with .Dv RFPROC . .It RFSIGSHARE If set, the kernel will force sharing the sigacts structure between the To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 21: 5: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 2DA0D14DA5 for ; Sat, 20 Mar 1999 21:04:59 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (qmail 21354 invoked from network); 21 Mar 1999 05:04:38 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 21 Mar 1999 05:04:38 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id AAA03667; Sun, 21 Mar 1999 00:04:37 -0500 (EST) From: "John S. Dyson" Message-Id: <199903210504.AAA03667@dyson.iquest.net> Subject: Re: rfork() In-Reply-To: from Alfred Perlstein at "Mar 21, 99 00:04:20 am" To: bright@rush.net (Alfred Perlstein) Date: Sun, 21 Mar 1999 00:04:37 -0500 (EST) Cc: dyson@iquest.net, samit@usa.ltindia.com, commiters@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 20 Mar 1999, John S. Dyson wrote: > > > Michael E. Mercer said: > > > Hello, > > > > > > This was posted to freebsd-questions with no reply. > > > I tried this and the child process created a core file. > > > I also tried the other options and they seem to work. > > > Just RFPROC and RFMEM DON'T! > > > > > rfork(RFMEM) doesn't easily work from C. You need to > > create an assembly stub. > > > > -- > > John | Never try to teach a pig to sing, > > dyson@iquest.net | it makes one look stupid > > jdyson@nc.com | and it irritates the pig. > > > > I've seen about 6 people ask about this because the manual lies about > what is done. I asked a while back about it, and John was kind enough > to dig up some code that used rfork to properly split the stack should > I try to dig it up? > I suggest trying to find the example. I might have it sitting around here also. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 21:19:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (Postfix) with ESMTP id AE67D14E20 for ; Sat, 20 Mar 1999 21:19:08 -0800 (PST) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.2/8.9.1) with ESMTP id VAA62032; Sat, 20 Mar 1999 21:18:49 -0800 (PST) (envelope-from ejs@bfd.com) Date: Sat, 20 Mar 1999 21:18:49 -0800 (PST) From: "Eric J. Schwertfeger" To: current@FreeBSD.ORG Cc: donegan@quick.net Subject: Re: IPSEC support? 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 > Is there any IPSEC support available for current? I've found support for > 2.2.8, but not so far for current. KAME has support for 3.1-RELEASE. I don't know how far -current has diverged, but you might want to try www.kame.net. KAME is IP6 and IPSEC, but you can compile it with only IPSEC. You should note that KAME and the IPDIVERT option are mutually exclusive, unless they've fixed it in the last week (snaps come out Sunday/Monday and I haven't had the chance to test the last snap). If all else fails, you can hack up something using IPDIVERT that does ESP transport in userspace (not full IPSEC) in a weekend. At least that's how long it took me. The code is not ready to be released, and I'm not sure I want to go through the hassle of trying to export-control it at any rate (US citizen vs government stupidity). (ref the not full IPSEC, RFC2401 just came out a few months ago, is three times the size of the previous IPSEC RFC (1825), and mandates a lot of things that I'm not ready to start coding). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 21:31:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from zone.syracuse.net (zone.syracuse.net [209.2.141.6]) by hub.freebsd.org (Postfix) with ESMTP id 7C08F15082; Sat, 20 Mar 1999 21:31:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.9.2/8.9.2) with ESMTP id FAA97744; Sun, 21 Mar 1999 05:29:35 GMT (envelope-from green@unixhelp.org) Date: Sun, 21 Mar 1999 05:29:35 +0000 (GMT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Alfred Perlstein Cc: "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() 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, 21 Mar 1999, Alfred Perlstein wrote: > On Sat, 20 Mar 1999, John S. Dyson wrote: > > > Michael E. Mercer said: > > > Hello, > > > > > > This was posted to freebsd-questions with no reply. > > > I tried this and the child process created a core file. > > > I also tried the other options and they seem to work. > > > Just RFPROC and RFMEM DON'T! > > > > > rfork(RFMEM) doesn't easily work from C. You need to > > create an assembly stub. > > > > -- > > John | Never try to teach a pig to sing, > > dyson@iquest.net | it makes one look stupid > > jdyson@nc.com | and it irritates the pig. > > > > I've seen about 6 people ask about this because the manual lies about > what is done. I asked a while back about it, and John was kind enough > to dig up some code that used rfork to properly split the stack should > I try to dig it up? > > In the meantime, can someone commit this or suggest something? For the suggest something, you realize that with Richard's VM_STACK code it should be relatively trivial to make this automatic (suggestion: add RFSTACK flag). > > thanks, > -Alfred > > Index: rfork.2 > =================================================================== > RCS file: /home/ncvs/src/lib/libc/sys/rfork.2,v > retrieving revision 1.8 > diff -u -r1.8 rfork.2 > --- rfork.2 1999/01/26 02:38:09 1.8 > +++ rfork.2 1999/03/21 04:49:10 > @@ -54,7 +54,8 @@ > will then inherit all the shared segments the parent process owns. Other segment > types will be unaffected. Subsequent forks by the parent will then > propagate the shared data and bss between children. The stack segment > -is always split. May be set only with > +is not split and must be allocated manually via an assembler subroutine. > +May be set only with > .Dv RFPROC . > .It RFSIGSHARE > If set, the kernel will force sharing the sigacts structure between the > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 20 23:44: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 158E6151BC; Sat, 20 Mar 1999 23:44:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA09505; Sat, 20 Mar 1999 23:43:14 -0800 (PST) (envelope-from dillon) Date: Sat, 20 Mar 1999 23:43:14 -0800 (PST) From: Matthew Dillon Message-Id: <199903210743.XAA09505@apollo.backplane.com> To: Brian Feldman Cc: Alfred Perlstein , "John S. Dyson" , samit@usa.ltindia.com, commiters@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rfork() References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > rfork(RFMEM) doesn't easily work from C. You need to :> > create an assembly stub. :> > :> > -- :> > John | Never try to teach a pig to sing, :> > dyson@iquest.net | it makes one look stupid :> > jdyson@nc.com | and it irritates the pig. :> > :> :> I've seen about 6 people ask about this because the manual lies about :> what is done. I asked a while back about it, and John was kind enough :> to dig up some code that used rfork to properly split the stack should :> I try to dig it up? :> :> In the meantime, can someone commit this or suggest something? : :For the suggest something, you realize that with Richard's VM_STACK code it :should be relatively trivial to make this automatic (suggestion: add :RFSTACK flag). : : Brian Feldman _ __ ___ ___ ___ : green@unixhelp.org _ __ ___ | _ ) __| \ : http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ If the goal is to completely share the address space, which RFMEM does, you can't split anything, not even the stack. It sure would be useful if there were a standard clib call adequate for calling rfork() and calling a function in the child w/ a new stack. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message