From owner-freebsd-stable Sun Apr 21 08:41:06 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23094 for stable-outgoing; Sun, 21 Apr 1996 08:41:06 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23080 Sun, 21 Apr 1996 08:41:05 -0700 (PDT) Message-Id: <199604211541.IAA23080@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Paulo Menezes cc: stable@FreeBSD.org Subject: Re: Another problem with Adaptec 2940 and S3TRIO64 In-reply-to: Your message of "Sun, 21 Apr 1996 16:31:27 BST." Date: Sun, 21 Apr 1996 08:41:04 -0700 From: "Justin T. Gibbs" Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Moved to -stable. >On Sun, 14 Apr 1996, Justin T. Gibbs wrote: > >> The aic7xxx driver in 2.1R has problems. Upgrade to 2.1-STABLE and >> see if your problems go away. >> > >Well, I did... and it still shows the same problem :( >I installed the stable-kernel and started a "make world"... and after >installing the libs, it hang, with lots of messages related with the scsi >controller. >One of the messages was :"BUS DEVICE RESET message queued" As a first step, remove the entries for every device in your kernel config file that you do not need, and recompile your kernel. As a second step, make sure that the termination on your hard drive is active and powered from the drive (not the SCSI bus), use a short cable, and ensure that termination is turned on with your 2940. >Thanks again > >Paulo >---- -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Mon Apr 22 06:04:46 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA03456 for stable-outgoing; Mon, 22 Apr 1996 06:04:46 -0700 (PDT) Received: from hawk.gnome.co.uk (gnome.intecc.co.uk [194.72.95.90]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA03449 for ; Mon, 22 Apr 1996 06:04:38 -0700 (PDT) Received: (from jacs@localhost) by hawk.gnome.co.uk (8.7.5/8.7.3) id OAA00682; Mon, 22 Apr 1996 14:04:26 +0100 (BST) Date: Mon, 22 Apr 1996 14:04:26 +0100 (BST) From: Chris Stenton Subject: Stable 2.1 -> Stable 2.2 when? To: stable@freebsd.org Message-Id: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering when the stable source tree will have a minor revision number change and what source changes can be expected at that time? Chris From owner-freebsd-stable Mon Apr 22 08:57:35 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA13686 for stable-outgoing; Mon, 22 Apr 1996 08:57:35 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA13678 for ; Mon, 22 Apr 1996 08:57:30 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.5/BSD4.4) id BAA23774 for stable@freebsd.org; Tue, 23 Apr 1996 01:57:26 +1000 (EST) From: michael butler Message-Id: <199604221557.BAA23774@asstdc.scgt.oz.au> Subject: what's this ? SCSI bus hung ? To: stable@freebsd.org Date: Tue, 23 Apr 1996 01:57:25 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just curious as to what causes (and can be done to fix) this .. sd1(ahc0:1:0): timed out in datain phase, SCSISIGI == 0x44 sd2(ahc0:3:0): asserted ATN - device reset in message buffer sd2(ahc0:3:0): timed out in datain phase, SCSISIGI == 0x54 ahc0: Issued Channel A Bus Reset #1. 4 SCBs aborted sd2(ahc0:3:0): UNIT ATTENTION asc:29,2 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:3 tagged queueing enabled with "full queue supported". It doesn't /seem/ to do anything really nasty, just stops for a few seconds and then continues on it's way. Any suggestions ? michael From owner-freebsd-stable Mon Apr 22 09:07:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA14231 for stable-outgoing; Mon, 22 Apr 1996 09:07:04 -0700 (PDT) Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA14223 for ; Mon, 22 Apr 1996 09:07:01 -0700 (PDT) Received: by haven.uniserve.com id <30986-144>; Mon, 22 Apr 1996 09:10:20 -0800 Date: Mon, 22 Apr 1996 09:10:16 -0700 (PDT) From: Tom Samplonius To: Chris Stenton cc: stable@freebsd.org Subject: Re: Stable 2.1 -> Stable 2.2 when? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Chris Stenton wrote: > > > I was wondering when the stable source tree will have a minor revision > number change and what source changes can be expected at that time? > It will be 2.1 -> 2.1.1, so there won't be many changes. Basically, once -stable is ready, it will be bumped to 2.1.1 and released. > Chris > > > Tom From owner-freebsd-stable Mon Apr 22 09:29:27 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA15648 for stable-outgoing; Mon, 22 Apr 1996 09:29:27 -0700 (PDT) Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA15643 Mon, 22 Apr 1996 09:29:26 -0700 (PDT) Message-Id: <199604221629.JAA15643@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: michael butler cc: stable@freebsd.org Subject: Re: what's this ? SCSI bus hung ? In-reply-to: Your message of "Tue, 23 Apr 1996 01:57:25 +1000." <199604221557.BAA23774@asstdc.scgt.oz.au> Date: Mon, 22 Apr 1996 09:29:25 -0700 From: "Justin T. Gibbs" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just curious as to what causes (and can be done to fix) this .. Check your cables and termination. If you wedge in a data phase it usually means that the drive missed an ACK on the bus and is waiting to transmit one or more additional bytes of data. I think I might be able to get the sequencer to dump additional data to the bit bucket and simply report an error. I'll look into it. >It doesn't /seem/ to do anything really nasty, just stops for a few seconds >and then continues on it's way. Any suggestions ? Nice to know that the recovery code seems to be working. > michael -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Mon Apr 22 09:38:58 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA16215 for stable-outgoing; Mon, 22 Apr 1996 09:38:58 -0700 (PDT) Received: from Nurse.RedBrick.DCU.IE (Nurse.RedBrick.DCU.IE [136.206.15.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA16202 for ; Mon, 22 Apr 1996 09:38:51 -0700 (PDT) Received: (from drjolt@localhost) by Nurse.RedBrick.DCU.IE (StealthMTA) id RAA17342 for freebsd-stable@freebsd.org; Mon, 22 Apr 1996 17:39:21 +0100 (BST) From: "Dave Murphy - Dr. Jolt" Message-Id: <199604221639.RAA17342@Nurse.RedBrick.DCU.IE> Subject: PTY limit broken in stable To: freebsd-stable@freebsd.org Date: Mon, 22 Apr 1996 17:39:21 +0100 (BST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quickie Question: Does the 2.1.0-RELEASE limit of 64 ptys still exist in FreeBSD-stable ? -- Dave Murphy - (co)System Administrator - DCU Networking Society http://WWW.RedBrick.DCU.IE/~drjolt From owner-freebsd-stable Mon Apr 22 09:52:11 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA17105 for stable-outgoing; Mon, 22 Apr 1996 09:52:11 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA17100 for ; Mon, 22 Apr 1996 09:52:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id JAA08406; Mon, 22 Apr 1996 09:51:31 -0700 (PDT) To: Chris Stenton cc: stable@freebsd.org Subject: Re: Stable 2.1 -> Stable 2.2 when? In-reply-to: Your message of "Mon, 22 Apr 1996 14:04:26 BST." Date: Mon, 22 Apr 1996 09:51:31 -0700 Message-ID: <8404.830191891@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This will only happen sometime after the 2.2->2.1 merge and 2.1.x release efforts have taken place. Jordan > > > I was wondering when the stable source tree will have a minor revision > number change and what source changes can be expected at that time? > > > > Chris > > From owner-freebsd-stable Mon Apr 22 10:42:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21569 for stable-outgoing; Mon, 22 Apr 1996 10:42:28 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA21560 for ; Mon, 22 Apr 1996 10:42:13 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id NAA17728; Mon, 22 Apr 1996 13:41:36 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id NAA15835; Mon, 22 Apr 1996 13:41:57 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 13:41:53 -0400 (EDT) From: "Marc G. Fournier" To: Chris Stenton cc: stable@freebsd.org Subject: Re: Stable 2.1 -> Stable 2.2 when? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Chris Stenton wrote: > > > I was wondering when the stable source tree will have a minor revision > number change and what source changes can be expected at that time? > 2.2-stable won't be until after 2.2-current has been released... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Apr 22 10:43:35 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA21620 for stable-outgoing; Mon, 22 Apr 1996 10:43:35 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA21610 for ; Mon, 22 Apr 1996 10:43:31 -0700 (PDT) Received: from dingo.enc.edu (dingo.enc.edu [199.93.252.229]) by itsdsv1.enc.edu (8.6.12/8.6.9) with SMTP id NAA19061 for ; Mon, 22 Apr 1996 13:43:00 -0400 Date: Mon, 22 Apr 1996 13:43:20 -0400 (EDT) From: Charles Owens To: stable@freebsd.org Subject: Docs on SCSI tagged queuing, other options? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From time to time I see people mention that they have their SCSI sytem configured to use "tagged queuing" and other options. I've not, however, run accross any documentation of these features. Is there any? Where? thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Mon Apr 22 11:12:06 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA24042 for stable-outgoing; Mon, 22 Apr 1996 11:12:06 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA24026 for ; Mon, 22 Apr 1996 11:12:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id LAA11001; Mon, 22 Apr 1996 11:11:07 -0700 (PDT) To: "Marc G. Fournier" cc: Chris Stenton , stable@freebsd.org Subject: Re: Stable 2.1 -> Stable 2.2 when? In-reply-to: Your message of "Mon, 22 Apr 1996 13:41:53 EDT." Date: Mon, 22 Apr 1996 11:11:07 -0700 Message-ID: <10999.830196667@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Mon, 22 Apr 1996, Chris Stenton wrote: > > > > > > > I was wondering when the stable source tree will have a minor revision > > number change and what source changes can be expected at that time? > > > 2.2-stable won't be until after 2.2-current has been released... That's true too. Jordan From owner-freebsd-stable Mon Apr 22 12:29:07 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA28575 for stable-outgoing; Mon, 22 Apr 1996 12:29:07 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA28566 Mon, 22 Apr 1996 12:29:01 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id PAA19763; Mon, 22 Apr 1996 15:28:51 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id PAA16118; Mon, 22 Apr 1996 15:29:14 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 15:29:14 -0400 (EDT) From: "Marc G. Fournier" To: Gary Palmer cc: stable@FreeBSD.ORG Subject: Re: clean install won't boot from hard drive... In-Reply-To: <2465.829890091@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Apr 1996, Gary Palmer wrote: > "Marc G. Fournier" wrote in message ID > : > > On Thu, 18 Apr 1996, Gary Palmer wrote: > > Nope, doesn't even reach the boot prompt, which is why I > > think I might have screwed up the Boot Mgr somehow :( > > > > Root is 30meg, like the rest of my machines. > > > > Don't sure if it makes any difference, but its a 1522 controller > > that I'm using... > > >From the handbook: > > o Adaptec AIC-6360 based boards, which includes the AHA-152x and > SoundBlaster SCSI cards. > > Note: You cannot boot from the SoundBlaster cards as they have no > on-board BIOS, which is necessary for mapping the boot device into > the system BIOS I/O vectors. They are perfectly usable for > external tapes, CDROMs, etc, however. The same goes for any other > AIC-6x60 based card without a boot ROM. Some systems DO have a > boot ROM, which is generally indicated by some sort of message when > the system is first powered up or reset. Check your system/board > documentation for more details. > > Does it have a boot ROM? > *groan* old hardware laying around...:( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Apr 22 13:26:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA05027 for stable-outgoing; Mon, 22 Apr 1996 13:26:31 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA05002 Mon, 22 Apr 1996 13:26:18 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA00276; Mon, 22 Apr 1996 16:26:02 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id QAA16309; Mon, 22 Apr 1996 16:26:33 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 16:26:32 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: stable@freebsd.org Subject: request for a new "feature" as regards DDB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... After *almost* 10 days uptime, my system just died. That fact, in itself, doesn't bother me *too* much, or at least, not as much as the fact that I don't know why :( I happened to be off of vt0 when it died, with no way to switch to vt0 and see what ddb was showing, and since I had to cold boot the machine as a result, couldn't even get a core dump :( So...any way of having an auto-switch to vt0 if the system crashes with DDB enabled? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Apr 22 14:24:16 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA13250 for stable-outgoing; Mon, 22 Apr 1996 14:24:16 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA13220 Mon, 22 Apr 1996 14:24:08 -0700 (PDT) Received: from dingo.enc.edu (dingo.enc.edu [199.93.252.229]) by itsdsv1.enc.edu (8.6.12/8.6.9) with SMTP id RAA25886; Mon, 22 Apr 1996 17:23:35 -0400 Date: Mon, 22 Apr 1996 17:23:58 -0400 (EDT) From: Charles Owens To: stable@freebsd.org cc: questions list FreeBSD Subject: printcap 'sh' flag doesn't seem to work Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have the 'sh' (suppress headers) flag in my printcap queue definitions, but I'm still getting headers. I didn't get headers with 2.0.5-RELEASE. I'm not sure if this behavior started with my move to 2.1 or to 2.1-stable. Anyone else seeing this? (or is it just me :) thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X ------------------------------------------------------------------------- From owner-freebsd-stable Mon Apr 22 16:42:03 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28867 for stable-outgoing; Mon, 22 Apr 1996 16:42:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28852 Mon, 22 Apr 1996 16:41:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA18168; Mon, 22 Apr 1996 16:37:52 -0700 From: Terry Lambert Message-Id: <199604222337.QAA18168@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 22 Apr 1996 16:37:52 -0700 (MST) Cc: current@FreeBSD.org, stable@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 22, 96 04:26:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > So...any way of having an auto-switch to vt0 if the system > crashes with DDB enabled? Assuming you aren't in X, yes, it's possible. If you are in X, after the panic, the console driver would need to send a signal to the X server process to get it to restore the console state. Obviously, the X server process can't run if your machine has paniced. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Mon Apr 22 17:14:11 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA02615 for stable-outgoing; Mon, 22 Apr 1996 17:14:11 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA02588 Mon, 22 Apr 1996 17:14:04 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id UAA03984; Mon, 22 Apr 1996 20:14:00 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id UAA17374; Mon, 22 Apr 1996 20:14:33 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 20:14:33 -0400 (EDT) From: "Marc G. Fournier" To: Terry Lambert cc: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604222337.QAA18168@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Terry Lambert wrote: > > So...any way of having an auto-switch to vt0 if the system > > crashes with DDB enabled? > > Assuming you aren't in X, yes, it's possible. > Is this one of those "do it yourself if you want it" sort of "possibles"? *grin* Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Apr 22 17:49:54 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA05950 for stable-outgoing; Mon, 22 Apr 1996 17:49:54 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA05925 Mon, 22 Apr 1996 17:49:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA18373; Mon, 22 Apr 1996 17:45:34 -0700 From: Terry Lambert Message-Id: <199604230045.RAA18373@phaeton.artisoft.com> Subject: Re: request for a new "feature" as regards DDB To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 22 Apr 1996 17:45:34 -0700 (MST) Cc: terry@lambert.org, current@FreeBSD.org, stable@FreeBSD.org In-Reply-To: from "Marc G. Fournier" at Apr 22, 96 08:14:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > So...any way of having an auto-switch to vt0 if the system > > > crashes with DDB enabled? > > > > Assuming you aren't in X, yes, it's possible. > > > Is this one of those "do it yourself if you want it" sort > of "possibles"? *grin* Possible, but not yet implemented by a cheerful volunteer. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-stable Mon Apr 22 19:55:41 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA21395 for stable-outgoing; Mon, 22 Apr 1996 19:55:41 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA21366 Mon, 22 Apr 1996 19:55:34 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id WAA05890; Mon, 22 Apr 1996 22:55:34 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id WAA17688; Mon, 22 Apr 1996 22:56:08 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Mon, 22 Apr 1996 22:56:07 -0400 (EDT) From: "Marc G. Fournier" To: Terry Lambert cc: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: request for a new "feature" as regards DDB In-Reply-To: <199604230045.RAA18373@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 22 Apr 1996, Terry Lambert wrote: > > > > So...any way of having an auto-switch to vt0 if the system > > > > crashes with DDB enabled? > > > > > > Assuming you aren't in X, yes, it's possible. > > > > > Is this one of those "do it yourself if you want it" sort > > of "possibles"? *grin* > > Possible, but not yet implemented by a cheerful volunteer. > Urmm...guess I'll volunteer then...*gets chainsaw tuned up* *laughs maniacally* Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Mon Apr 22 21:05:29 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA29758 for stable-outgoing; Mon, 22 Apr 1996 21:05:29 -0700 (PDT) Received: from obie.softweyr.com (slcmodem1-p2-12.intele.net [206.29.206.127]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA29741 for ; Mon, 22 Apr 1996 21:05:26 -0700 (PDT) Received: (from wes@localhost) by obie.softweyr.com (8.7.5/8.6.12) id WAA01307; Mon, 22 Apr 1996 22:05:54 -0600 (MDT) Date: Mon, 22 Apr 1996 22:05:54 -0600 (MDT) Message-Id: <199604230405.WAA01307@obie.softweyr.com> From: wes@intele.net To: stable@freebsd.org Subject: How often does the -stable tree get updated? Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've recently (Friday 4/20) updated to 2.1-STABLE, and quite like it. Congratulations! How often does the -stable tree get updated? I would like to keep up to date now that I've taken the plunge, and I'm wondering how often I should sup in my crontab. -- Wes Peters | Yes I am a pirate, two hundred years too late Softweyr | The cannons don't thunder, there's nothing to plunder Consulting | I'm an over forty victim of fate... wes@intele.net | Jimmy Buffett From owner-freebsd-stable Tue Apr 23 00:26:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11904 for stable-outgoing; Tue, 23 Apr 1996 00:26:31 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id AAA11898 for ; Tue, 23 Apr 1996 00:26:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id AAA03596; Tue, 23 Apr 1996 00:26:20 -0700 (PDT) To: wes@intele.net cc: stable@FreeBSD.org Subject: Re: How often does the -stable tree get updated? In-reply-to: Your message of "Mon, 22 Apr 1996 22:05:54 MDT." <199604230405.WAA01307@obie.softweyr.com> Date: Tue, 23 Apr 1996 00:26:20 -0700 Message-ID: <3594.830244380@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk supping once a day should catch all the changes - it's hard to say how often it gets updated since that varies widely. Jordan > I've recently (Friday 4/20) updated to 2.1-STABLE, and quite like > it. Congratulations! > > How often does the -stable tree get updated? I would like to keep up > to date now that I've taken the plunge, and I'm wondering how often I > should sup in my crontab. > > -- > Wes Peters | Yes I am a pirate, two hundred years too late > Softweyr | The cannons don't thunder, there's nothing to plunder > Consulting | I'm an over forty victim of fate... > wes@intele.net | Jimmy Buffett From owner-freebsd-stable Tue Apr 23 03:06:04 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA22259 for stable-outgoing; Tue, 23 Apr 1996 03:06:04 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA22254 for ; Tue, 23 Apr 1996 03:05:54 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Tue, 23 Apr 1996 05:05:45 -0600 Message-ID: Date: 23 Apr 1996 04:55:37 -0500 From: "Richard Wackerbarth" Subject: Re: How often does the -stable tree get updated? To: "stable@FreeBSD.org" , "wes@intele.net" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > How often does the -stable tree get updated? I would like to keep up > to date now that I've taken the plunge, and I'm wondering how often I > should sup in my crontab. There are updates applied in a near daily manner. However, so days there are no changes. Since you intend to perform these updates on a regular basis, you might consider using the CTM distribution instead. By subscribing to this distribution, you will receive an e-mail update each day that there are any changes. This reduces the load on the demand servers and allows you to stay up-to-date without worrying whether or not there was an update any given day. From owner-freebsd-stable Tue Apr 23 06:32:20 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA02622 for stable-outgoing; Tue, 23 Apr 1996 06:32:20 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA02616 Tue, 23 Apr 1996 06:32:17 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id JAA00943; Tue, 23 Apr 1996 09:32:08 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id JAA20951; Tue, 23 Apr 1996 09:32:23 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Tue, 23 Apr 1996 09:32:22 -0400 (EDT) From: "Marc G. Fournier" To: stable@freebsd.org cc: current@freebsd.org Subject: vm_page_alloc panic, followed by... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Morning... Well, after running nicely for over 9 days straight, my -stable machine has gone down three times in 24hrs :( this morning at approx. 2:30, she went down with in vm_page_alloc(). As per usual, no core dump is possible with this machine, it just locks up, so a DDB trace is the only thing available: vm_page_alloc+0x1b3 vm_hold_load_pages+0x40 allocbuf+0x8a getblk bread ffs_blkatoff ufs_lookup lookup namei vn_open open syscall Xsyscall --- syscall 5, eip = 0x8081465, ebp = 0xefbfd0c4 --- Current process was listed as innd...I believe someone else reported a vm_page_alloc() panic recently with innd also being current process? Then, after resetting the machine after it hung trying to dump, it got to the point of starting up the the system daemons (mountd was being started), when it panic'd again with: panic: pmap_zero_page: CMAP busy Unfortunately, unless there is paging capabilities in ddb that I couldn't find, trace traces right off the screen, so getting anything out of that is near to impossible without a larger screen :( I'm going to sup in a new kernel for this machine today, as the one I have is dated March 26th, but I haven't seen much in the way of commits for the -stable kernel that seems related... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Tue Apr 23 21:28:11 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14782 for stable-outgoing; Tue, 23 Apr 1996 21:28:11 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA14777 for ; Tue, 23 Apr 1996 21:28:08 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id AAA00847 for ; Wed, 24 Apr 1996 00:27:57 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id AAA06148 for ; Wed, 24 Apr 1996 00:28:09 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 00:28:09 -0400 (EDT) From: "Marc G. Fournier" To: stable@freebsd.org Subject: 9 makes + 1 caused panic... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just want to verify that this to is a hardware problem vs a software one. I just started up 9 make processes in /usr/src/lib, and had just started up a 10th on /usr/src/gnu/lib when it panic'd. I'm using -O2 -m486 -pipe, since someone mentioned that -pipe is a *really* good way to brutalize the system... The panic: Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x700c fault code = supervisor write, protection violation instruction pointer = 0x8:0xf0106ae1 current process = 4244 (sh) interrupt mask = kernel: type 12 trap, code=0 Stopped at _closef+0x85: decw 0xc(%esi) And "trace" shows: closef+0x85 close+0x83 syscall Xsyscall --- syscall 6, eip = 0x42e45, ebp = 0xefbfdcfc --- Now, the machine has 16Meg of RAM and was, the last time I checked for it panic'd, using around 25% of the swap (60Meg/218Meg) If this looks like a hardware issue again, no probs, I'll keep beating that horse, but this one I haven't seen before, so figured it wouldn't hurt to ask. And, of course, no core dump :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Tue Apr 23 22:49:52 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA20110 for stable-outgoing; Tue, 23 Apr 1996 22:49:52 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA20104 for ; Tue, 23 Apr 1996 22:49:50 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA16508; Wed, 24 Apr 1996 15:16:11 +0930 From: Michael Smith Message-Id: <199604240546.PAA16508@genesis.atrad.adelaide.edu.au> Subject: Re: 9 makes + 1 caused panic... To: scrappy@ki.net (Marc G. Fournier) Date: Wed, 24 Apr 1996 15:16:10 +0930 (CST) Cc: stable@freebsd.org In-Reply-To: from "Marc G. Fournier" at Apr 24, 96 00:28:09 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > I just started up 9 make processes in /usr/src/lib, and > had just started up a 10th on /usr/src/gnu/lib when it panic'd. > I'm using -O2 -m486 -pipe, since someone mentioned that -pipe is > a *really* good way to brutalize the system... > > The panic: > > Fatal Trap 12: page fault while in kernel mode > fault virtual address = 0x700c > fault code = supervisor write, protection violation > instruction pointer = 0x8:0xf0106ae1 > current process = 4244 (sh) > interrupt mask = > kernel: type 12 trap, code=0 > Stopped at _closef+0x85: decw 0xc(%esi) Hmm. Looking at closef(), the most likely candidate for this would be if (--fp->f_count > 0) return (0); fp is dereferenced a few lines above, and I can't imagine how the structure would have become write-protected by accident... > And, of course, no core dump :( This one's fairly straightforward. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-stable Wed Apr 24 06:50:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA15789 for stable-outgoing; Wed, 24 Apr 1996 06:50:28 -0700 (PDT) Received: from babba.cu-online.com (somebody@babba.cu-online.com [205.198.248.21]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA15762 Wed, 24 Apr 1996 06:50:22 -0700 (PDT) Received: from localhost (somebody@localhost) by babba.cu-online.com (8.7.5/8.7.3) with SMTP id IAA16630; Wed, 24 Apr 1996 08:49:55 -0500 (CDT) Date: Wed, 24 Apr 1996 08:49:54 -0500 (CDT) From: Somebody To: stable@freefall.freebsd.org cc: questions@freefall.freebsd.org, isp@freefall.freebsd.org Subject: config.data for inn1.4unoff4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am wondering if any can provide me with a config.data for INN1.4unoff4 Inn does come with one but I am not sure as to how current or correct it is. And therefore wanting to verify with others on it. Thank You Carlos From owner-freebsd-stable Wed Apr 24 11:54:24 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA09833 for stable-outgoing; Wed, 24 Apr 1996 11:54:24 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA09823 for ; Wed, 24 Apr 1996 11:54:21 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA15944; Wed, 24 Apr 1996 12:52:50 -0600 Date: Wed, 24 Apr 1996 12:52:50 -0600 From: Nate Williams Message-Id: <199604241852.MAA15944@rocky.sri.MT.net> To: "Marc G. Fournier" Cc: stable@freebsd.org Subject: Re: 9 makes + 1 caused panic... In-Reply-To: References: Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just want to verify that this to is a hardware problem vs > a software one. [ Panic stuff deleted ] > And, of course, no core dump :( Just as a data point, I'm messing with adding PCCARD support to some of our device drivers in -stable. I've gotten some really old patches I'm trying to apply, but the driver has changed alot, so I'm getting (expected) kernel panics. On my laptop, if DDB isn't configured I don't get a core dump because of WD DRQ() request timeout, but with DDB configured and multiple 'panic''panic' messages, I get a core dump written. However, savecore won't recognize it unless I boot from the same kernel that generated it. Suffice it to say that with a -stable machine as of this morning (including David's pmap.c patch) I'm getting a core dump. Machine is a P/75 laptop 24MB memory 810 MB IDE disk PS/2 mouse X running (but on another console) Nate From owner-freebsd-stable Wed Apr 24 13:42:38 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA21241 for stable-outgoing; Wed, 24 Apr 1996 13:42:38 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA21219 for ; Wed, 24 Apr 1996 13:42:31 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id QAA04997; Wed, 24 Apr 1996 16:42:24 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id OAA07257; Wed, 24 Apr 1996 14:42:58 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Wed, 24 Apr 1996 14:42:57 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: stable@freebsd.org Subject: Re: 9 makes + 1 caused panic... In-Reply-To: <199604240546.PAA16508@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > I just started up 9 make processes in /usr/src/lib, and > > had just started up a 10th on /usr/src/gnu/lib when it panic'd. > > I'm using -O2 -m486 -pipe, since someone mentioned that -pipe is > > a *really* good way to brutalize the system... > > > > The panic: > > > > Fatal Trap 12: page fault while in kernel mode > > fault virtual address = 0x700c > > fault code = supervisor write, protection violation > > instruction pointer = 0x8:0xf0106ae1 > > current process = 4244 (sh) > > interrupt mask = > > kernel: type 12 trap, code=0 > > Stopped at _closef+0x85: decw 0xc(%esi) > > Hmm. Looking at closef(), the most likely candidate for this would be > > if (--fp->f_count > 0) > return (0); > > fp is dereferenced a few lines above, and I can't imagine how the structure > would have become write-protected by accident... > hardware or software bug then? :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Wed Apr 24 20:24:42 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA08476 for stable-outgoing; Wed, 24 Apr 1996 20:24:42 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA08467 for ; Wed, 24 Apr 1996 20:24:25 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id MAA22274; Thu, 25 Apr 1996 12:50:36 +0930 From: Michael Smith Message-Id: <199604250320.MAA22274@genesis.atrad.adelaide.edu.au> Subject: Re: 9 makes + 1 caused panic... To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 25 Apr 1996 12:50:35 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, stable@freebsd.org In-Reply-To: from "Marc G. Fournier" at Apr 24, 96 02:42:57 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Marc G. Fournier stands accused of saying: > > > > fp is dereferenced a few lines above, and I can't imagine how the structure > > would have become write-protected by accident... > > > > hardware or software bug then? :( Almost certainly hardware; modulo any judgement by John wrt. the changes he's made in the VM area in the last few days. Most of them had to do with accidentally unmapping more than was apprpriate, which would have given you a 'page not present' fault, not a 'write protect' fault. > Marc G. Fournier scrappy@ki.net -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-stable Wed Apr 24 22:05:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA15622 for stable-outgoing; Wed, 24 Apr 1996 22:05:47 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA15615 for ; Wed, 24 Apr 1996 22:05:44 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id BAA02773; Thu, 25 Apr 1996 01:05:43 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id BAA01545; Thu, 25 Apr 1996 01:05:42 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Thu, 25 Apr 1996 01:05:41 -0400 (EDT) From: "Marc G. Fournier" To: Michael Smith cc: stable@freebsd.org Subject: Re: 9 makes + 1 caused panic... In-Reply-To: <199604250320.MAA22274@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Apr 1996, Michael Smith wrote: > Marc G. Fournier stands accused of saying: > > > > > > fp is dereferenced a few lines above, and I can't imagine how the structure > > > would have become write-protected by accident... > > > > > > > hardware or software bug then? :( > > Almost certainly hardware; modulo any judgement by John wrt. the changes > he's made in the VM area in the last few days. Most of them had to do > with accidentally unmapping more than was apprpriate, which would > have given you a 'page not present' fault, not a 'write protect' fault. > Okay, I have the new pmap code in place, and a fresh kernel...tomorrow I'll try once more to force the machine to panic...I'm working at getting a new "simple" machine put together that I can pressure test and put online, but its goingn to take a couple of weeks, so have to make due with what I have now :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Thu Apr 25 14:49:39 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12943 for stable-outgoing; Thu, 25 Apr 1996 14:49:39 -0700 (PDT) Received: from center.c-edv.de ([194.112.64.254]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA12924 for ; Thu, 25 Apr 1996 14:49:27 -0700 (PDT) Received: (from tc@localhost) by center.c-edv.de (8.6.12/8.6.12) id XAA10595; Thu, 25 Apr 1996 23:51:48 +0200 Date: Thu, 25 Apr 1996 23:51:48 +0200 (MET DST) From: Thomas Christel To: stable@FreeBSD.org cc: stable@FreeBSD.org Subject: Re: 9 makes + 1 caused panic... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk unsuscriebe From owner-freebsd-stable Thu Apr 25 15:55:29 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17589 for stable-outgoing; Thu, 25 Apr 1996 15:55:29 -0700 (PDT) Received: from firewall.pyxis.com (pyxs.com [206.5.144.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA17583 for ; Thu, 25 Apr 1996 15:55:25 -0700 (PDT) Received: (from firemail@localhost) by firewall.pyxis.com (8.6.11/8.6.9) id PAA29558 for ; Thu, 25 Apr 1996 15:55:23 -0700 Message-Id: <199604252255.PAA29558@firewall.pyxis.com> Received: from pyux1.pyxis.com(192.9.200.3) by firewall.pyxis.com via smap (V1.3) id sma029552; Thu Apr 25 15:54:53 1996 Received: from nick_markiw.pyxis.com by pyux1.pyxis.com with SMTP (1.37.109.16/16.2) id AA280502748; Thu, 25 Apr 1996 15:52:28 -0700 Date: Thu, 25 Apr 1996 15:52:28 -0700 X-Sender: nmarkiw@mail.pyxis.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: stable@freebsd.org From: "Nicholas M. Markiw" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe ------------------------------------------------------------------------------- Nicholas M. Markiw nick.markiw@pyxs.com UNIX System Admin/Network Admin voice (619) 635-6961 Pyxis Corporation fax (619) 635-6941 From owner-freebsd-stable Fri Apr 26 10:07:28 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA19150 for stable-outgoing; Fri, 26 Apr 1996 10:07:28 -0700 (PDT) Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA19139 for ; Fri, 26 Apr 1996 10:07:11 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.5/BSD4.4) id DAA10877 for stable@freebsd.org; Sat, 27 Apr 1996 03:05:11 +1000 (EST) From: michael butler Message-Id: <199604261705.DAA10877@asstdc.scgt.oz.au> Subject: top-level makefile ? To: stable@freebsd.org Date: Sat, 27 Apr 1996 03:05:09 +1000 (EST) X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there supposed to be a top-level makefile at the moment ? sup quite happily removed it :-( michael From owner-freebsd-stable Fri Apr 26 11:51:32 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA25322 for stable-outgoing; Fri, 26 Apr 1996 11:51:32 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA25316 for ; Fri, 26 Apr 1996 11:51:28 -0700 (PDT) Received: from freebsd.ki.net (root@freebsd.ki.net [205.150.102.51]) by ki.net (8.7.4/8.7.4) with ESMTP id OAA11798 for ; Fri, 26 Apr 1996 14:51:25 -0400 (EDT) Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id OAA11020 for ; Fri, 26 Apr 1996 14:51:43 -0400 (EDT) X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs Date: Fri, 26 Apr 1996 14:51:39 -0400 (EDT) From: "Marc G. Fournier" To: stable@freebsd.org Subject: bad dir panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... On a different machine then the usual panics, I yesterday totally blew up the machine, and am wondering if this is a hardware issue (like the other machine), or possibly a software one. The machine is a DX33 w/ 8Meg of RAM, and I tried to do a make world to bring it up to date with stable. Before the panic, I got: free inode /usr/obj/29376 had 2013265776 blocks flash on the screen, and then several minutes later it panic'd with: /usr: bad dir ino 11725 at offset 12: mangled entry panic: bad dir Stopped at +0x2b: movb $0,_in_Debugger.110 If you get this far and feel its a hardware problem, then don't read any further (but do send me a quick email telling me so?), as its just more details from what I could dig out of a core dump and a DDB trace...the corruption that this caused was so extensive that I had to effectively rebuild my /etc directory... Trace showed: () at +0x2b _panic+0x3b _ufs_dirbad+0x37 _ufs_lookup+0x4f5 _lookup+0x2c5 _namei+0xfd _vn_open+0x183 _open+0x97 _syscall+0xf3 _Xsyscall+0x2b --- syscall 5, eip = 0x8070d15, ebp = 0xefbfcb68 Dmesg of the system: FreeBSD 2.1-STABLE #0: Fri Apr 26 00:14:42 EDT 1996 scrappy@ki.net:/usr/src/sys/compile/thrawn CPU: i486DX (486-class CPU) real memory = 8388608 (8192K bytes) avail memory = 6717440 (6560K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:0:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd0(aic0:0:0): Direct-Access 515MB (1056708 512 byte sectors) fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 765 fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/bnc[*BNC*] address 00:a0:24:0a:5a:fenpx0 on motherboard npx0: INT 16 interface Bits of a gdb of the core dump follow: panic: bad dir #0 boot (howto=260) at ../../i386/i386/machdep.c:911 911 dumppcb.pcb_ptd = rcr3(); (kgdb) where #0 boot (howto=260) at ../../i386/i386/machdep.c:911 #1 0xf0111225 in panic (fmt=0xf0101258 "from debugger") at ../../kern/subr_prf.c:116 #2 0xf0101275 in db_panic (dummy1=-266858973, dummy2=0, dummy3=-1, dummy4=0xefbffb40 "") at ../../ddb/db_command.c:397 #3 0xf010115e in db_command (last_cmdp=0xf01a0af4, cmd_table=0xf01a0954) at ../../ddb/db_command.c:281 #4 0xf01012dd in db_command_loop () at ../../ddb/db_command.c:419 #5 0xf0103c78 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:72 #6 0xf0180bfa in kdb_trap (type=3, code=0, regs=0xefbffc30) at ../../i386/i386/db_interface.c:120 #7 0xf01883b0 in trap (frame={tf_es = 16, tf_ds = -262602736, tf_edi = -262542592, tf_esi = 8191, tf_ebp = -272630668, tf_isp = -272630696, tf_ebx = 256, tf_edx = -266859019, tf_ecx = 2000, tf_eax = -1, tf_trapno = 3, tf_err = 0, tf_eip = -266858973, tf_cs = -272695288, tf_eflags = 582, tf_esp = -266859035, tf_ss = -267316773}) at ../../i386/i386/trap.c:388 #8 0xf0181461 in calltrap () #9 0xf011121f in panic (fmt=0xf016b82d "bad dir") at ../../kern/subr_prf.c:114 #10 0xf016b86f in ufs_dirbad (ip=0xf059eb00, offset=12, how=0xf016ab80 "mangled entry") at ../../ufs/ufs/ufs_lookup.c:590 #11 0xf016b095 in ufs_lookup (ap=0xefbffd88) at ../../ufs/ufs/ufs_lookup.c:285 #12 0xf0125f1d in lookup (ndp=0xefbffefc) at ./vnode_if.h:27 #13 0xf0125a6d in namei (ndp=0xefbffefc) at ../../kern/vfs_lookup.c:147 #14 0xf012b323 in vn_open (ndp=0xefbffefc, fmode=5, cmode=1445) at ../../kern/vfs_vnops.c:113 #15 0xf0128a9f in open (p=0xf0591200, uap=0xefbfff94, retval=0xefbfff8c) at ../../kern/vfs_syscalls.c:646 #16 0xf0188dbb in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 87960, tf_esi = -272640916, tf_ebp = -272643224, tf_isp = -272629788, tf_ebx = 134766688, tf_edx = 0, tf_ecx = 46, tf_eax = 5, tf_trapno = 534, tf_err = 534, tf_eip = 134679829, tf_cs = 31, tf_eflags = 534, tf_esp = -272643348, tf_ss = 39}) at ../../i386/i386/trap.c:906 #17 0xf01814ab in Xsyscall () #18 0x534b in ?? () #19 0xcb14 in ?? () #20 0x94ea in ?? () #21 0x10d3 in ?? () (kgdb) up 10 #10 0xf016b86f in ufs_dirbad (ip=0xf059eb00, offset=12, how=0xf016ab80 "mangled entry") at ../../ufs/ufs/ufs_lookup.c:590 590 panic("bad dir"); (kgdb) list 585 586 mp = ITOV(ip)->v_mount; 587 (void)printf("%s: bad dir ino %ld at offset %ld: %s\n", 588 mp->mnt_stat.f_mntonname, ip->i_number, offset, how); 589 if ((mp->mnt_stat.f_flags & MNT_RDONLY) == 0) 590 panic("bad dir"); 591 } 592 593 /* 594 * Do consistency checking on a directory entry: (kgdb) print mp->mnt_stat.f_flags $1 = 4096 (kgdb) up #11 0xf016b095 in ufs_lookup (ap=0xefbffd88) at ../../ufs/ufs/ufs_lookup.c:285 285 ufs_dirbad(dp, dp->i_offset, "mangled entry"); (kgdb) list 280 ep = (struct direct *)((char *)bp->b_data + entryoffsetinblock); 281 if (ep->d_reclen == 0 || 282 (dirchk && ufs_dirbadentry(vdp, ep, entryoffsetinblock))) { 283 int i; 284 285 ufs_dirbad(dp, dp->i_offset, "mangled entry"); 286 i = DIRBLKSIZ - (entryoffsetinblock & (DIRBLKSIZ - 1)); 287 dp->i_offset += i; 288 entryoffsetinblock += i; 289 continue; (kgdb) quit ki# Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-stable Sat Apr 27 06:28:44 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA16899 for stable-outgoing; Sat, 27 Apr 1996 06:28:44 -0700 (PDT) Received: from zen.nash.org (nash.pr.mcs.net [204.95.47.72]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA16894 for ; Sat, 27 Apr 1996 06:28:41 -0700 (PDT) Received: (from alex@localhost) by zen.nash.org (8.7.5/8.6.12) id IAA19054; Sat, 27 Apr 1996 08:30:41 -0500 (CDT) Date: Sat, 27 Apr 1996 08:30:41 -0500 (CDT) Message-Id: <199604271330.IAA19054@zen.nash.org> From: Alex Nash To: stable@freebsd.org Subject: vnode_pager_output: attempt to write meta-data Reply-to: nash@mcs.com Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message popped up this morning in my syslog: vnode_pager_output: attempt to write meta-data!!! -- 0xfffe8000(ff) Which comes from vnode_pager_output (vm/vnode_pager.c): if ((int) m[0]->offset < 0) { printf("vnode_pager_output: attempt to write meta-data!!! -- 0x%x(%x)\n", m[0]->offset, m[0]->dirty); rtvals[0] = VM_PAGER_BAD; return VM_PAGER_BAD; } Do I assume correctly that the system is in an unstable state and I should now reboot? This is 2.1-STABLE supped Apr 18/Apr 19 (don't laugh, I supped with a 14.4 modem :). Alex From owner-freebsd-stable Sat Apr 27 08:10:46 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA20505 for stable-outgoing; Sat, 27 Apr 1996 08:10:46 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA20499 for ; Sat, 27 Apr 1996 08:10:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id IAA02693; Sat, 27 Apr 1996 08:10:46 -0700 (PDT) Message-Id: <199604271510.IAA02693@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: nash@mcs.com cc: stable@freebsd.org Subject: Re: vnode_pager_output: attempt to write meta-data In-reply-to: Your message of "Sat, 27 Apr 1996 08:30:41 CDT." <199604271330.IAA19054@zen.nash.org> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 27 Apr 1996 08:10:45 -0700 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >This message popped up this morning in my syslog: > > vnode_pager_output: attempt to write meta-data!!! -- 0xfffe8000(ff) > >Which comes from vnode_pager_output (vm/vnode_pager.c): > > if ((int) m[0]->offset < 0) { > printf("vnode_pager_output: attempt to write meta-data!!! -- 0x%x(%x)\n", m[0]->offset, m[0]->dirty); > rtvals[0] = VM_PAGER_BAD; > return VM_PAGER_BAD; > } > >Do I assume correctly that the system is in an unstable state and I >should now reboot? No, it simply indicates that we somehow detected that a meta-data page was modified. It's a fairly benign bug that is believed to be fixed in the latest changes to pmap.c. I do recommend re-supping -stable, however, to pick up the fixes. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Sat Apr 27 16:26:27 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA15322 for stable-outgoing; Sat, 27 Apr 1996 16:26:27 -0700 (PDT) Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA15317 Sat, 27 Apr 1996 16:26:21 -0700 (PDT) Received: (from jc@localhost) by irbs.irbs.com (8.7.5/8.6.6) id TAA00521; Sat, 27 Apr 1996 19:25:47 -0400 (EDT) From: John Capo Message-Id: <199604272325.TAA00521@irbs.irbs.com> Subject: Re: kern/1159: NFS Client hangs in vm_object_terminate() - objtrm To: FreeBSD-gnats-submit@freebsd.org Date: Sat, 27 Apr 1996 19:25:46 -0400 (EDT) Cc: FreeBSD-stable@freebsd.org In-Reply-To: <199604271545.LAA24735@irbs.irbs.com> from John Capo at "Apr 27, 96 11:45:48 am" X-Mailer: ELM [version 2.4ME+ PL11 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nfs/nfs_bio.c: 241 bp = nfs_getcacheblk(vp, lbn, bufsize, p); if (!bp) return (EINTR); if ((bp->b_flags & B_CACHE) == 0) { bp->b_flags |= B_READ; not_readin = 0; vfs_busy_pages(bp, 0); error = nfs_doio(bp, cred, p); if (error) { brelse(bp); return (error); } } The buffer returned from nfs_getcacheblk() has B_DONE set in b_flags. nfs_doio() goes off and does its thing but biodone fails with "biodone: buffer already done". bread()/brwrite() always clear (B_DONE | B_ERROR | B_INVAL). They both obtain a buffer from getblk() as does nfs_getcacheblk(). Should nfs_doio() also clear (B_DONE | B_ERROR | B_INVAL)? John Capo jc@irbs.com IRBS Engineering FreeBSD Servers and Workstations (954) 792-9551 Unix/Internet Consulting - ISP Solutions John Capo writes: > > >Number: 1159 > >Category: kern > >Synopsis: NFS Client hangs in vm_object_terminate() - objtrm > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sat Apr 27 08:50:01 PDT 1996 > >Last-Modified: > >Originator: John Capo > >Organization: > IRBS Engineering > >Release: FreeBSD 2.1-STABLE i386 > >Environment: > > FreeBSD 2.1-stable client and server both built with NFS_ASYNC from > sup around 4/18/96. > > >Description: > > Client hangs while building TeX on an NFS mounted /usr/ports tree: > 0 19496 1 46 -18 0 172 12 objtrm D p1 0:02.91 ../web2c/splitup mf > > Restarting make hangs with this status: > 0 19609 1 41 -18 0 164 12 vodead D p1 0:00.07 ../web2c/splitup mf > > >How-To-Repeat: > > mount server:/usr/ports /usr/ports or somesuch > cd /usr/ports/print/tex > make > > Hangs at: > > cd mf; make SHELL='/bin/sh' CC='gcc' CFLAGS='-g ' RANLIB='ranlib' LN='ln -s' DEFS='' CCLD='gcc' LDFLAGS='-g ' LIBS='' x_extra_libs='' x_include_flags='-I/usr/X11R6/include' x_lib_flags='-L/usr/X11R6/lib' triptrap > /bin/sh ./../mf/convert > > >Fix: > > > > >Audit-Trail: > >Unformatted: > From owner-freebsd-stable Sat Apr 27 21:21:46 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA03586 for stable-outgoing; Sat, 27 Apr 1996 21:21:46 -0700 (PDT) Received: from nic.ott.hookup.net (uucp@nic.ott.hookup.net [165.154.5.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA03581 for ; Sat, 27 Apr 1996 21:21:41 -0700 (PDT) Received: (uucp@localhost) by nic.ott.hookup.net (8.7.5/1.169) with UUCP id AAA08616; Sun, 28 Apr 1996 00:21:30 -0400 (EDT) Received: from cc:Mail UUCPLINK 2.0 by ccigate.acdi-cida.gc.ca id 9603288306.AA830675254 Sun, 28 Apr 96 00:07:34 Date: Sun, 28 Apr 96 00:07:34 From: administrator@ccigate.acdi-cida.gc.ca Message-Id: <9603288306.AA830675254@ccigate.acdi-cida.gc.ca> To: stable@FreeBSD.org Subject: ccd for 2.1-stable Subject: cc:Mail UUCPLINK 2.0 Undeliverable Message Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk User ccigate!ccigate.acdi-cida.gc.ca!louis_gaulin@ccigate.acdi-cida.gc.ca is not defined Original text follows ----------------------------------------- Received: by ccmail Received: from hookup by acdi-cida.gc.ca (UUPC/extended 1.11) with UUCP; Sun, 28 Apr 1996 00:06:13 EDT Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.4]) by nic.ott.hookup.net (8.7.5/1.169) with ESMTP id XAA23172 for ; Sat, 27 Apr 1996 23:23:32 -0400 (EDT) Received: from localhost (daemon@localhost) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA28928 Sat, 27 Apr 1996 20:01:49 -0700 (PDT) Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28920 for freebsd-announce-outgoing; Sat, 27 Apr 1996 20:01:48 -0700 (PDT) Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28914 for freebsd-announce; Sat, 27 Apr 1996 20:01:44 -0700 (PDT) Date: Sat, 27 Apr 1996 20:01:44 -0700 (PDT) Message-Id: <199604280301.UAA28914@freefall.freebsd.org> Reply-to: stable@FreeBSD.org Subject: ccd for 2.1-stable From: asami@freefall.freebsd.org (Satoshi Asami) X-ccAdmin: postmaster@hookup To: announce@FreeBSD.org Sender: owner-freebsd-announce@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hello the disk world, I ported the 2.2-current version of ccd back to 2.1-stable. There is no change in functionality from the previous version. (It's just that it compiles now on your 2.1-stable machine. :) Satoshi P.S. Please check out "http://stampede.cs.berkeley.edu/ccd/" and "README-s.html" in that directory! ------- $Id: ccd.README,v 1.9.2.1 1996/04/27 07:08:43 asami Exp $ ********************************************************** * The FreeBSD ccd driver (beta) * * for 2.1-stable users * * by Satoshi Asami * * and Nisha Talagala * * version of 96/04/27 * ********************************************************** (0) Changes from previous versions (Jan/14, Jan/31, Mar/20, Mar/25) Jan/14 -> Jan/31: . There is mirroring support . ccdcontrol is renamed ccdconfig (back to original NetBSD name) . ccdconfig is now in /sbin (so you can call it from rc -- a patch to rc is also included) Jan/31 -> Mar/20: . It now runs under -current . ccd.c is moved from sys/ccd to sys/dev/ccd (like NetBSD) . The driver is now a proper pseudo-device (unlike the isa device like before, see below for kernel config file changes) Mar/20 -> Mar/25: . Mirror handling code is cleaner, and doesn't kludge around b_resid's anymore. For the implementation, read note near top of ccd.c. Mar/25 -> Apr/27: . Ported back from 2.2-current to 2.1-stable. No change in functionality. (1) Introduction This is a port of NetBSD's ccd (concatenated disk) driver. It is not a complete work in any way, but seems to be working fairly ok here, so we decided to make it available so that people can test it and even fix some bugs. :) (2) Warning As the title above says, this is beta software and is therefore VERY GREEN. You should not expect this to work. It may eat your system disk for lunch. It may even fry your microwave in the process. Make sure you have backed up all your data and locked your children in the basement before you attempt to try this. (3) What it does In case you don't know what it is, ccd is a disk array driver. You can combine several disk partitions into one "virtual disk". Then you can partition it or use the whole thing or add some pepper and salt or whatever you want. (4) What it does not There is no parity support yet. That's why its name doesn't resemble RAID in any form. However, there is mirroring available starting from the Jan/31 version. (4a) Cool, how do I use mirroring? Add CCDF_MIRROR to the list of flags (third field in /etc/ccd.conf), and your disk space will magically shrink into half. The writes go to all disks, while the reads will all come from the first n/2 disks. If one of the disk goes "poof", you can reconfigure the ccd to use only half the disks without mirroring. That should keep your users happy until you get the chance to put in the replacement disk. When the new disk is installed, use the ccd recovery program called `dd' (which mysteriously made its way into the release even before we put out an alpha version of ccd), e.g., to copy sd1g to sd4g, dd if=/dev/rsd1g of=/dev/rsd4g bs=1048576 (5) How to compile Note this package is for FreeBSD-current (aka 2.2-current). It probably won't work right away for 2.1R or 2.1-stable. It even may not work for your version of -current (depending on what date you got your source). Ok, first you need to unpack the distribution. It contains the following files: sys/dev/ccd/ccd.README (this file) sys/dev/ccd/ccd.PLIST sys/dev/ccd/ccd.4 sys/dev/ccd/ccd.c sys/sys/ccdvar.h sbin/ccdconfig/Makefile sbin/ccdconfig/ccdconfig.8 sbin/ccdconfig/ccdconfig.c sbin/ccdconfig/pathnames.h ccd.patch You can unpack them in your /usr/src directory. After that, apply the ccd.patch. It makes several changes to the header files and such. You can use the following command to apply the patch: patch -p < ccd.patch (On a separate line for your triple-clicking pleasure.) There is a patch to rc in there, so take a look at your /etc/rc and install the new one. If you have changed your /etc/rc, either cut & paste the relevant lines or take out the hunk pertaining rc and apply it to your /etc/rc. Then add the following to your kernel configuration file: pseudo-device ccd 4 (You can have as many of them as you want, or fewer than four, of course.) We recommend you to add "options DDB" too. This will make the kernel go into a debugger in case of a panic. That will make it easier for you to send us a complete bug report. (Note this will disable auto-rebooting after a panic, so don't do this on a machine that has to run unattended.) (6) How to use ccd Wait, you need to compile ccdconfig too! Go in there, do "make depend all install". If install complains about missing directories and such, make sure you have the correct Makefile.inc in the parent (/usr/src/sbin) directory. If you don't have one (like, you don't have the sbin source tree), just editing the ccdconfig Makefile and adding "BINDIR=/sbin" and "NOSHARED=YES" by hand should do. Also, you will need to create the device files. There is a patch to MAKEDEV included in ccd.patch, so go into etc/etc.i386 and install the new MAKEDEV into /dev. Then you can, say, "cd /dev; sh MAKEDEV ccd0" to create the appropriate device files for your first ccd devices, etc. Now, go and read the man pages. ccdconfig.8 should be installed by now; ccd.4 is still sitting in the source directory so go read it there. (Try "nroff -man ccd.4 | less -s".) Assuming you've read them, here is an example, if you have four partitions (sd1g, sd2g, sd3g, sd4g) you want to combine into one: echo "ccd0 16 none /dev/sd1g /dev/sd2g /dev/sd3g /dev/sd4g" > /etc/ccd.conf ccdconfig -Cv (to configure; you'll see a message here) disklabel ccd0 (just to make sure there is a valid disklabel) newfs /dev/rccd0c mount /dev/ccd0c /mnt (play with /mnt) umount /mnt ccdconfig -U (to unconfigure) (7) What's the second field in /etc/ccd.conf? That's the "interleave size". Basically, the ccd driver will write this many sectors (usually 512 bytes) to one disk before it moves to the next disk. As a special case, a zero here means no interleave, i.e., to concatenate disks serially. We have found that in FFS, a value of 16 usually optimizes read performance, while the write peaks with a much larger value (like 512). This probably has to do with cluster_write() thinking it's writing to a single disk when it's actually not. This is one of the things we are planning to fix. (8) Are there any caveats? Oh sure. One of them is "don't use a partition that starts at a beginning of the slice". So please leave some space at the beginning of the slice in the partitions you are combining (sd[1-4]g in the above example). Of course, if someone can figure out why and fix it, that will be great. Another is that if you specify odd numbers of disks for mirroring, it will say it's not going to use the last disk, but doesn't release the disk properly so you won't be able to use it elsewhere. We'll fix this soon. (9) My disk is totally hosed. It's all your fault! See (2). (10) Anything I can help? Well, any bug fix is welcome. In addition to the stuff mentioned above, we are aware of at least the following: a. The disklabel support is still old (pre-2.x FreeBSD style). We should be including instead of in ccd.c. Can someone take a look at this? b. On a similar note, if I do "disklabel -e ccdX" immediately after configuring the disk, it won't let me write it with the error: disklabel: ioctl DIOCWDINFO: No disk label on disk; use "disklabel -r" to install initial label It works if I do a "disklabel -w -r ccdX " first and then edit that label. I don't know if fixing the above will take care of this too. c. I'm not exactly sure what the "geometry" of this pseudo-disk means. If it doesn't matter, it's ok; if newfs (for instance) cares, we should give it a better set of default values. d. Someone please tell me how to create an lkm out of this. (11) Where should I send bug reports/fixes? Please send them to ccd@stampede.cs.berkeley.edu. This will reach the two primary developers (Satoshi and Nisha), as well as other interested parties. If you want to be added to this list, please send mail to Satoshi (asami@cs.berkeley.edu). (12) Where do I get new versions? They will be made available as ftp://stampede.cs.berkeley.edu/pub/ccd/ccd-.tar.gz so check this site regularly. Also, you can browse at http://stampede/cs.berkeley.edu/ccd/ which contains the latest development news and links to various tarballs. (13) I'm tired Yeah, I'm tired too. Well go to sleep now then, and try it tomorrow! Good night! Satoshi