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 Message-ID: <Pine.BSI.3.92.960414000753.14402C-100000@freebsd.ki.net> In-Reply-To: <199604140329.MAA11898@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.92.960414000753.14402C-100000>