From owner-freebsd-scsi Tue Aug 18 09:16:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10900 for freebsd-scsi-outgoing; Tue, 18 Aug 1998 09:16:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from jane.lfn.org (ops.lfn.org [209.16.92.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09643 for ; Tue, 18 Aug 1998 09:07:37 -0700 (PDT) (envelope-from caj@lfn.org) Received: (qmail 14127 invoked by uid 100); 18 Aug 1998 16:05:47 -0000 Date: Tue, 18 Aug 1998 11:05:47 -0500 (CDT) From: Craig Johnston To: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: panic in -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a stable kernel, cvsupped a couple of days ago. The system is a K6-133 on an ASUS HX mobo, with an NCR53c810 and an IBM DCAS-32160 drive. It seems that /usr/bin/install is the only program that causes this to happen. It causes a panic pretty regularly. (preventing me from doing a 'make installworld' and bringing the binaries up to date.) Otherwise, the machine has long uptimes serving out ethertalk for a bunch of macs. Here's the error I got yesterday: Data buffered space not in kernel context sd0: oops not queued panic: biodone: buffer not busy I can provide more info, but I was hoping this was something that has been seen before. I have enabled all the debugging I could find, and will no doubt have more to report presently. I have 'FAILSAFE' defined in the kernel config file. I'll probably poke around in the kernel later today, and look at /usr/bin/install to see if I can figure out why it might be exercising this. Any ideas before I do? thanks, -Craig PS -- please advise if I should have targetted different lists. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message