From owner-freebsd-stable Sat Apr 13 21:38:13 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA22475 for stable-outgoing; Sat, 13 Apr 1996 21:38:13 -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 VAA22459 Sat, 13 Apr 1996 21:38:03 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA12068; Sun, 14 Apr 1996 14:37:49 +0930 From: Michael Smith Message-Id: <199604140507.OAA12068@genesis.atrad.adelaide.edu.au> Subject: Re: Current -Stable less stable then that of March 26 To: scrappy@ki.net (Marc G. Fournier) Date: Sun, 14 Apr 1996 14:37:49 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, se@freebsd.org, stable@freebsd.org In-Reply-To: from "Marc G. Fournier" at Apr 14, 96 00:09:32 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: > > > > Unh? I have four NCR-using machines at -stable, and they all work jus' > > fine. Have you perhaps wound out the PCI bus latency timer beyond 32, > > or do you have some other PCI hardware in this box that's griefing you? > > > -stable as of Friday night? As I stated above, my March 26th kernel > didn't exhibit this problem, which I'm currently running without any problems > *knock on wood* Hmm. The most recent one was worlded last thursday, ie. the 11th. It's still up, but admittedly not very busy just now. > 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 [[