From owner-freebsd-stable  Sat Apr 13 21:09:39 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA20968
          for stable-outgoing; Sat, 13 Apr 1996 21:09:39 -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 VAA20960
          Sat, 13 Apr 1996 21:09:35 -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 AAA08237; Sun, 14 Apr 1996 00:09:33 -0400 (EDT)
Received: from localhost (scrappy@localhost) by freebsd.ki.net (8.7.5/8.7.5) with SMTP id AAA14448; Sun, 14 Apr 1996 00:09:32 -0400 (EDT)
X-Authentication-Warning: freebsd.ki.net: scrappy owned process doing -bs
Date: Sun, 14 Apr 1996 00:09:32 -0400 (EDT)
From: "Marc G. Fournier" <scrappy@ki.net>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: se@freebsd.org, stable@freebsd.org
Subject: Re: Current -Stable less stable then that of March 26
In-Reply-To: <199604140329.MAA11898@genesis.atrad.adelaide.edu.au>
Message-ID: <Pine.BSI.3.92.960414000753.14402C-100000@freebsd.ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 14 Apr 1996, Michael Smith wrote:

> Marc G. Fournier stands accused of saying:
> >
> > 	Well, I just upgraded my -stable source tree last night, installed
> > a new kernel early this morning, and so far I've had two panic's, so I've
> > plugged back in my March 26th kernel that was substantially more -stable.
> >
> > 	Latest panic:
> >
> > ncr_start+0x4a7: movl _APTD+0xfe4(%ebp,%eax)
>
> 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*

> > 	There is *no* trace available on this, and when I panic, I get a
> > dump device not ready, so no core dump.
>
> It sounds like your disk controller is provoking you into the panic,
> so it's hardly likely that you're going to be able to use it for a dump.
>
> You _really_ need to talk to Stefan about this.
>
	Stefan...are you out there?

Marc G. Fournier                                  scrappy@ki.net
Systems Administrator @ ki.net               scrappy@freebsd.org