From owner-freebsd-stable Sun Jan 21 06:42:01 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA18320 for stable-outgoing; Sun, 21 Jan 1996 06:42:01 -0800 (PST) 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 SMTP id GAA18311 for ; Sun, 21 Jan 1996 06:41:56 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id BAA14306; Mon, 22 Jan 1996 01:41:13 +1100 From: michael butler Message-Id: <199601211441.BAA14306@asstdc.scgt.oz.au> Subject: Re: spontaneous reboot with -stable To: tom@uniserve.com (Tom Samplonius) Date: Mon, 22 Jan 1996 01:41:09 +1100 (EST) Cc: rlenk@widget.xmission.com, stable@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jan 20, 96 09:39:45 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG Precedence: bulk I wrote: > I finally caught the error message from my 2842-fitted -stable machine that > gives me so much trouble (reboots more than once a day :-(). It says .. > panic: getnewbuf: inconsistent LRU queue, qindex=0 > syncing ... Ron Lenk wrote: > > Yeah, don't run -stable. :-D > > I started running -stable again after Justin Gibbs commited the new ahc > > driver, and I have been unable to get a kernel to run for more than 5 > > minutes. Tom Samplonius writes: > Not if you have a 2940. The new ahc driver is really, really nice in > comparison to the old one. I'm now seeing record uptime's on a -stable > system. I certainly agree that, when the machine is running with the new driver, particularly with tagged-queueing, it *screams* :-) but it only lasts a few hours for me :-(. Having reverted to a -release kernel, the same machine, in the same configuration has not failed once. However, with "-stable", it reboots within about 4 hours. It was doing the same things as it's always done, a *very* light load with Apache and sup file-serving. It's a UMC491C motherboard with an Intel 486DX2/66, 16 meg of RAM, IBM 1 gig SCSI-II attached to a recent Adaptec 2842. It has no serial or parallel ports. Up until a minute ago I had a WD8003-EBT as -stable had also complained of too many stray irq 7s with the 3C509 installed. I had temporarily replaced it thinking that this may have been related to the reboot problem. It did not and, I should add, the -release kernel also complains of too many stray irq 7s when I reinstalled the 3C509. This problem is not specific to either -release or -stable but simply to the presence/activation of the ep0 driver. This is stupid, the 3C509's on irq 10! Selecting "-1" in the boot-time config menu correctly reads irq 10 from the card's eeprom and then proceeds to complain about stray ints :-(. This latter problem, however, has nothing at all to do with the machine's (in)stability which, at this stage, I can only conclude is related to some change between -release and -stable and is possibly the latest ahc driver. I've tried disabling either or both caches. Enabling and disabling tagged-queueing and the full queueing extension slowing the RAM timing down and speeding it up .. nothing I do to the machine with -stable running will make it "live" more than a few hours, michael From owner-freebsd-stable Sun Jan 21 10:27:57 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA29053 for stable-outgoing; Sun, 21 Jan 1996 10:27:57 -0800 (PST) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id KAA29047 Sun, 21 Jan 1996 10:27:52 -0800 (PST) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id MAA26034; Sun, 21 Jan 1996 12:27:14 -0600 From: Joe Greco Message-Id: <199601211827.MAA26034@brasil.moneng.mei.com> Subject: Re: ccd driver or 2.1R available To: tom@uniserve.com (Tom Samplonius) Date: Sun, 21 Jan 1996 12:27:13 -0600 (CST) Cc: jgreco@brasil.moneng.mei.com, hackers@freebsd.org, stable@freebsd.org In-Reply-To: from "Tom Samplonius" at Jan 19, 96 02:25:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk > As far as I can tell from the manpage, the reason is that the ccd > disklabel could be mistaken by the system as the disk's label, because > they are in the same spot. The first bit of every partition has space > reserved for the label, but ccd will not reserve space. > > I believe swap will not work as the first partition on a disk for the > same reason, except that swap will overwrite the label! Well, I left the first cylinder empty and I've been running for 22 hours now having striped two disks for a new alt.binaries partition on news.sol.net. My only "gotcha" was that ccd insists on the component partitions being of type "4.2BSD" which I wasn't quite expecting. It might be better to have a different partition type ("CCD"?) to avoid confusion. The error message given by ccdcontrol was hideously vague, of course it only took a minute or two to go grepping for the errno in the driver and inspect the relevant code, and then it made sense. Anyways, we have ways to exercise the code :-) and it appears to be working just great! I have a six-drive array that's just begging for ccd. Somebody please fold this into -current! It's exactly what we need... nifty things like this are great selling points for FreeBSD. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 From owner-freebsd-stable Sun Jan 21 16:58:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA21891 for stable-outgoing; Sun, 21 Jan 1996 16:58:56 -0800 (PST) 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 QAA21856 Sun, 21 Jan 1996 16:58:31 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA16810; Mon, 22 Jan 1996 11:35:33 +1030 From: Michael Smith Message-Id: <199601220105.LAA16810@genesis.atrad.adelaide.edu.au> Subject: Re: spontaneous reboot with -stable To: imb@scgt.oz.au (michael butler) Date: Mon, 22 Jan 1996 11:35:32 +1030 (CST) Cc: gibbs@freefall.freebsd.org, rlenk@widget.xmission.com, stable@freebsd.org, hackers@freebsd.org In-Reply-To: <199601200721.SAA18912@asstdc.scgt.oz.au> from "michael butler" at Jan 20, 96 06:21:15 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk michael butler stands accused of saying: > > That cured my other problem of "stray irq 7" but I haven't yet tried this The 'stray IRQ 7' message is alarming; if you don't have anything driving IRQ 7 it means that the interrupt controller is seeing edges on an interrupt line but isn't catching the source of the interrupt. This is _bad_news_. > michael -- ]] 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 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-stable Mon Jan 22 12:52:20 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12706 for stable-outgoing; Mon, 22 Jan 1996 12:52:20 -0800 (PST) Received: from snert.pilhuhn.de (snert.pilhuhn.de [193.141.89.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12698 for ; Mon, 22 Jan 1996 12:52:14 -0800 (PST) Received: by snert.pilhuhn.de id ; Mon, 22 Jan 96 21:50 MET To: stable@freebsd.org Path: hwr From: hwr@pilhuhn.de (Heiko W.Rupp) Newsgroups: pilhuhn.freebsd.stable Subject: Re: spontaneous reboot with -stable Date: 22 Jan 1996 20:50:48 GMT Organization: The Home Of The Pilhuhn Lines: 12 Message-ID: References: Reply-To: hwr@pilhuhn.de NNTP-Posting-Host: snert.pilhuhn.de X-Newsreader: slrn (0.8.4) Sender: owner-stable@freebsd.org Precedence: bulk In article , Tom Samplonius wrote: > Not if you have a 2940. The new ahc driver is really, really nice in >comparison to the old one. I'm now seeing record uptime's on a -stable >system. I guess that is what really worries me .. the new driver is not out for a longe time yet ... -- Heiko W.Rupp hwr@pilhhuhn.de INN FAQ can be found in ftp://ftp.xlink.net/pub/news/docs/ From owner-freebsd-stable Mon Jan 22 13:17:09 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA13902 for stable-outgoing; Mon, 22 Jan 1996 13:17:09 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA13874 Mon, 22 Jan 1996 13:16:58 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <54048(15)>; Mon, 22 Jan 1996 12:54:35 PST Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177478>; Mon, 22 Jan 1996 10:17:29 -0800 X-Mailer: exmh version 1.6.4 10/10/95 To: Nate Williams cc: stable@freebsd.org, current@freebsd.org, hackers@freebsd.org Subject: Re: Possible solution to the Proxy-ARP bug enclosed In-reply-to: Your message of "Fri, 19 Jan 1996 20:50:27 PST." <199601200450.VAA17390@rocky.sri.MT.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jan 1996 10:17:17 PST From: Bill Fenner Message-Id: <96Jan22.101729pst.177478@crevenia.parc.xerox.com> Sender: owner-stable@freebsd.org Precedence: bulk For those reviewing my patch that Nate sent out, I plan to remove the final piece of the new if (the requirement that it's an -unresolved- ARP entry); a host route should always override an ARP cache entry (think about a mobilip proxy thingy; a machine is on the net one second and the next it's mobile but you still have an ARP cache entry for it). The user-space arp program also needs some fixes to make it harder to create strange proxy entries. It's still possible to have three different ARP table entries for the same host if you are sufficiently confused about it, and /usr/sbin/arp can make things pretty confusing =) Bill From owner-freebsd-stable Mon Jan 22 14:17:45 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA21418 for stable-outgoing; Mon, 22 Jan 1996 14:17:45 -0800 (PST) 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 OAA21401 Mon, 22 Jan 1996 14:17:40 -0800 (PST) Message-Id: <199601222217.OAA21401@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: hwr@pilhuhn.de cc: stable@freebsd.org Subject: Re: spontaneous reboot with -stable In-reply-to: Your message of "22 Jan 1996 20:50:48 GMT." Date: Mon, 22 Jan 1996 14:17:40 -0800 From: "Justin T. Gibbs" Sender: owner-stable@freebsd.org Precedence: bulk >In article , Tom S >amplonius wrote: >> Not if you have a 2940. The new ahc driver is really, really nice in >>comparison to the old one. I'm now seeing record uptime's on a -stable >>system. > >I guess that is what really worries me .. the new driver is not out for >a longe time yet ... > >-- >Heiko W.Rupp hwr@pilhhuhn.de >INN FAQ can be found in ftp://ftp.xlink.net/pub/news/docs/ > I wouldn't touch the old driver with a 10 foot pole. Most of the stability problems I've seen have a conection to the ep driver or the reordering of probes (ISA comes last). I haven't had time to look into these problem yet, but I will after USENIX. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Mon Jan 22 22:18:31 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA03676 for stable-outgoing; Mon, 22 Jan 1996 22:18:31 -0800 (PST) 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 WAA03663 for ; Mon, 22 Jan 1996 22:18:18 -0800 (PST) Received: by haven.uniserve.com id <30773-4>; Mon, 22 Jan 1996 22:20:38 -0000 Date: Mon, 22 Jan 1996 22:20:36 -0800 (PST) From: Tom Samplonius To: "Justin T. Gibbs" cc: hwr@pilhuhn.de, stable@FreeBSD.org Subject: Re: spontaneous reboot with -stable In-Reply-To: <199601222217.OAA21401@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org Precedence: bulk On Mon, 22 Jan 1996, Justin T. Gibbs wrote: > >In article , Tom S > >amplonius wrote: > >> Not if you have a 2940. The new ahc driver is really, really nice in > >>comparison to the old one. I'm now seeing record uptime's on a -stable > >>system. > > > >I guess that is what really worries me .. the new driver is not out for > >a longe time yet ... > > > >-- > >Heiko W.Rupp hwr@pilhhuhn.de > >INN FAQ can be found in ftp://ftp.xlink.net/pub/news/docs/ > > > > I wouldn't touch the old driver with a 10 foot pole. Most > of the stability problems I've seen have a conection to the ep driver > or the reordering of probes (ISA comes last). I haven't had > time to look into these problem yet, but I will after USENIX. > -- > Justin T. Gibbs I agree completely. Although, I'm still using a preliminary version of the new driver, I'm seeing a record uptime of 14 days and counting. Previously, the record was 10 days, followed by 3 days. Every other time it would crash consistently every two days. Tom From owner-freebsd-stable Mon Jan 22 23:57:56 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA12647 for stable-outgoing; Mon, 22 Jan 1996 23:57:56 -0800 (PST) Received: from snert.pilhuhn.de (snert.pilhuhn.de [193.141.89.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA12642 for ; Mon, 22 Jan 1996 23:57:52 -0800 (PST) Received: by snert.pilhuhn.de id ; Tue, 23 Jan 96 08:56 MET Message-Id: From: hwr@snert.pilhuhn.de (Heiko W.Rupp) Subject: Re: spontaneous reboot with -stable To: tom@uniserve.com (Tom Samplonius) Date: Tue, 23 Jan 1996 08:56:16 -40962758 (MET) Cc: gibbs@freefall.freebsd.org, hwr@pilhuhn.de, stable@FreeBSD.org In-Reply-To: from "Tom Samplonius" at Jan 22, 96 10:20:36 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Sender: owner-stable@FreeBSD.org Precedence: bulk Tom Samplonious: > I agree completely. Although, I'm still using a preliminary version of > the new driver, I'm seeing a record uptime of 14 days and counting. I still have the old driver and my uptimes were 21 and 14 days. Yesterday it crashed two times within an hour and one time it was within close() ... > Previously, the record was 10 days, followed by 3 days. Every other time it > would crash consistently every two days. Hm? Has your computer been stable before? From owner-freebsd-stable Tue Jan 23 01:59:39 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA21862 for stable-outgoing; Tue, 23 Jan 1996 01:59:39 -0800 (PST) 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 SMTP id BAA21852 for ; Tue, 23 Jan 1996 01:59:34 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id UAA06156 for stable@freebsd.org; Tue, 23 Jan 1996 20:59:12 +1100 From: michael butler Message-Id: <199601230959.UAA06156@asstdc.scgt.oz.au> Subject: Re: spontaneous reboot with -stable To: stable@freebsd.org Date: Tue, 23 Jan 1996 20:59:09 +1100 (EST) In-Reply-To: from "Heiko W.Rupp" at Jan 23, 96 08:56:16 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk [ cc's trimmed ] Heiko W.Rupp writes: > I still have the old driver and my uptimes were 21 and 14 days. > Yesterday it crashed two times within an hour and one time it was > within close() ... This is similar to my experience .. 73 days uptime and the only reason it didn't go further was that I installed -stable and ceased to be so :-( michael From owner-freebsd-stable Tue Jan 23 09:11:02 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA02826 for stable-outgoing; Tue, 23 Jan 1996 09:11:02 -0800 (PST) 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 JAA02798 for ; Tue, 23 Jan 1996 09:10:54 -0800 (PST) Received: by haven.uniserve.com id <30747-3>; Tue, 23 Jan 1996 09:13:32 -0000 Date: Tue, 23 Jan 1996 09:13:31 -0800 (PST) From: Tom Samplonius To: "Heiko W.Rupp" cc: gibbs@freefall.freebsd.org, hwr@pilhuhn.de, stable@FreeBSD.ORG Subject: Re: spontaneous reboot with -stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG Precedence: bulk On Tue, 23 Jan 1996, Heiko W.Rupp wrote: > Tom Samplonious: > > > I agree completely. Although, I'm still using a preliminary version of > > the new driver, I'm seeing a record uptime of 14 days and counting. > > I still have the old driver and my uptimes were 21 and 14 days. > Yesterday it crashed two times within an hour and one time it was > within close() ... > > > Previously, the record was 10 days, followed by 3 days. Every other time it > > would crash consistently every two days. > > Hm? Has your computer been stable before? Not with a 2940 in it. Disk hangs and total lockups were common under the old driver. Problems were also experienced with wcarchive, which is why a lot of the changes were made. It seems that only users with 2842's (and maybe 2742's) seem to have a problem with the new driver. Tom From owner-freebsd-stable Tue Jan 23 09:44:59 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA05483 for stable-outgoing; Tue, 23 Jan 1996 09:44:59 -0800 (PST) Received: from snert.pilhuhn.de (snert.pilhuhn.de [193.141.89.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA05475 for ; Tue, 23 Jan 1996 09:44:53 -0800 (PST) Received: by snert.pilhuhn.de id ; Tue, 23 Jan 96 18:42 MET Message-Id: From: hwr@snert.pilhuhn.de (Heiko W.Rupp) Subject: Re: spontaneous reboot with -stable To: tom@uniserve.com (Tom Samplonius) Date: Tue, 23 Jan 1996 18:42:17 -40962758 (MET) Cc: stable@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jan 23, 96 09:13:31 am X-Mailer: ELM [version 2.4 PL20] Content-Type: text Sender: owner-stable@FreeBSD.ORG Precedence: bulk Tom Samplonious: > > Hm? Has your computer been stable before? > > Not with a 2940 in it. Disk hangs and total lockups were common under Interesting .. I found the old driver only slow (maximum half speed of the bt946c), but I had that 21+14 days uptime with the old one. > the old driver. Problems were also experienced with wcarchive, which is > why a lot of the changes were made. > It seems that only users with 2842's (and maybe 2742's) seem to have a > problem with the new driver. Perhaps I should try it out ... I am still a bit afraid that the box might loos stability; better only 7 oder 14 days of uptime than only 2 days and a little bit faster ... From owner-freebsd-stable Tue Jan 23 10:21:25 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA07811 for stable-outgoing; Tue, 23 Jan 1996 10:21:25 -0800 (PST) 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 KAA07798 Tue, 23 Jan 1996 10:21:23 -0800 (PST) Message-Id: <199601231821.KAA07798@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol To: Tom Samplonius cc: "Heiko W.Rupp" , hwr@pilhuhn.de, stable@FreeBSD.ORG Subject: Re: spontaneous reboot with -stable In-reply-to: Your message of "Tue, 23 Jan 1996 09:13:31 PST." Date: Tue, 23 Jan 1996 10:21:23 -0800 From: "Justin T. Gibbs" Sender: owner-stable@FreeBSD.ORG Precedence: bulk > >On Tue, 23 Jan 1996, Heiko W.Rupp wrote: > >> Hm? Has your computer been stable before? > > Not with a 2940 in it. Disk hangs and total lockups were common under >the old driver. Problems were also experienced with wcarchive, which is >why a lot of the changes were made. > > It seems that only users with 2842's (and maybe 2742's) seem to have a >problem with the new driver. > >Tom People experiencing problems with eisa devices (or "eisa like" devices such as the 2842) under -stable should change the probe order in i386/i386/autoconf.c to see if it increases stability. Simply put the eisa_configure() call after the call to isa_configure(). I believe there to be a conflict between the two bus probes or between eisa and isa drivers that were masked by the old probe order. I'm still investigating. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-stable Wed Jan 24 00:33:34 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA10149 for stable-outgoing; Wed, 24 Jan 1996 00:33:34 -0800 (PST) Received: from snert.pilhuhn.de (snert.pilhuhn.de [193.141.89.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA10110 for ; Wed, 24 Jan 1996 00:33:17 -0800 (PST) Received: by snert.pilhuhn.de id ; Tue, 23 Jan 96 20:17 MET Message-Id: From: hwr@snert.pilhuhn.de (Heiko W.Rupp) Subject: Crash in close() with stable .. To: stable@FreeBSD.ORG Date: Tue, 23 Jan 1996 20:17:10 -40962758 (MET) X-Mailer: ELM [version 2.4 PL20] Content-Type: text Sender: owner-stable@FreeBSD.ORG Precedence: bulk Hi, as mentionned in another post I had two crashes yesterday. Of one I have the panic message along with a trace from ddb. As I recorded them by hand, you have to imagine the missing things youself ... Trap 12 page fault while in kernel mode fra = 0xf172c1a4 fc = supervisor write, page not present ip = 0x8:0xf0160546 cs (unreadable) bag 0x lim 0xffff hg 0x1b DPL 0 pres 1 def 32 1 , (unreadble) grac 1 proc ef = interupts enabled, resume, iopl=0 current process : innd imask = kernle trap 12 trap , code 0 Stopped at _vm_object_remove + 0x52 >trace _vm_object_remove +0x52 _vm_object_deallocate +0x174 _pager_cache + 0x2a _vm_object_cache_trim +0x30 _vm_object_deallocate_ +0x15c _vn_close + 0x70 _vn_closefile + 0x19 _closef + 0x12c _close + 0x83 (not shure here ..) _syscall(27,27,5, ..) + 0x157 From owner-freebsd-stable Thu Jan 25 03:58:29 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA18972 for stable-outgoing; Thu, 25 Jan 1996 03:58:29 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA18965 for ; Thu, 25 Jan 1996 03:58:24 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.3/8.6.9) id DAA00767; Thu, 25 Jan 1996 03:58:18 -0800 (PST) Date: Thu, 25 Jan 1996 03:58:18 -0800 (PST) Message-Id: <199601251158.DAA00767@silvia.HIP.Berkeley.EDU> To: stable@freebsd.org CC: ccd@forgery.cs.Berkeley.EDU Subject: ccd results? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-stable@freebsd.org Precedence: bulk Has anyone tried the ccd kit? I see that many people got it (and grabbed kp-0.95 too while you were here :) but haven't heard much about how it's working. For us, we put together a modest (5 x 2GB DEC RZ28) system and started using it as an NFS server. Nothing has changed in the FreeBSD ccd driver lately. I recommend moving ccdcontrol to /sbin though, that way you can run it from /etc/rc before mounting local filesystems and use it just like a regular disk. By the way, we found that some of the Adaptec 2940UW's don't seem to work well with striped disks. Look at your card with the external connector to your left, and if the small chip on your right says "Rev. A", that's the one we're having troubles with. We can't get more than 7MB/s no matter how many Wide-SCSI disks we connect to them. The ones that say "Rev. B" are ok, i.e., we can get around 13MB/s for reads. If someone else can verify this, it is most appreciated. Satoshi From owner-freebsd-stable Thu Jan 25 09:40:47 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA03951 for stable-outgoing; Thu, 25 Jan 1996 09:40:47 -0800 (PST) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA03946 for ; Thu, 25 Jan 1996 09:40:45 -0800 (PST) Received: from lily.csl.sri.com (lily.csl.sri.com [192.12.33.201]) by csla.csl.sri.com (8.7.3/8.7.3) with ESMTP id JAA05466 for ; Thu, 25 Jan 1996 09:40:14 -0800 (PST) Received: from localhost.csl.sri.com (localhost.csl.sri.com [127.0.0.1]) by lily.csl.sri.com (8.7.3/8.7.3) with SMTP id JAA14870 for ; Thu, 25 Jan 1996 09:40:13 -0800 (PST) Message-Id: <199601251740.JAA14870@lily.csl.sri.com> X-Authentication-Warning: lily.csl.sri.com: Host localhost.csl.sri.com [127.0.0.1] didn't use HELO protocol To: freebsd-stable@freebsd.org Subject: Probe order in FreeBSD-stable Date: Thu, 25 Jan 1996 09:40:12 -0800 From: Fred Gilham Sender: owner-stable@freebsd.org Precedence: bulk Hello, In FreeBSD-stable, the probe-order changed so that the PCI bus is probed before the ISA bus. In the 2.1 release it was the opposite. The above change makes FreeBSD-stable kernels not boot on my machines. Changing the probe-order back in autoconf.c makes everything work fine. I'm just posting this to 1) make people aware that at least one user gets broken by this and 2) to find out if it was an intentional change with other repercussions or just an inadvertent change. -Fred Gilham gilham@csl.sri.com From owner-freebsd-stable Fri Jan 26 17:12:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA11435 for stable-outgoing; Fri, 26 Jan 1996 17:12:43 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA11430 for ; Fri, 26 Jan 1996 17:12:40 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.6.12/8.6.9) id RAA00258 for freebsd-stable@freebsd.org; Fri, 26 Jan 1996 17:08:51 -0800 From: "Steven G. Kargl" Message-Id: <199601270108.RAA00258@troutmask.apl.washington.edu> Subject: -stable instablities continue To: freebsd-stable@freebsd.org Date: Fri, 26 Jan 1996 17:08:51 -0800 (PST) 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 Precedence: bulk Well, I tried Justin Gibbs' suggestion of moving eisa_configure() to after the call to isa_configure() in i386/i386/autoconfig. The strip-down kernel (i.e., only essential devices) still hangs on my EISA system with AHA 1742 adaptor. Note: the system did not panic and drop me into DDB. It became unresponsive to any input. To recreate the problem, run iozone with a file size of 32 MB. -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.x-stable | Seattle, WA 98105 |---------------------|