From owner-freebsd-current Wed Oct 30 16:05:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA11035 for current-outgoing; Wed, 30 Oct 1996 16:05:45 -0800 (PST) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA11030 for ; Wed, 30 Oct 1996 16:05:41 -0800 (PST) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.8.2/8.7.5) with SMTP id TAA11075 for ; Wed, 30 Oct 1996 19:05:46 -0500 (EST) Date: Wed, 30 Oct 1996 19:05:46 -0500 (EST) From: "Marc G. Fournier" To: current@freebsd.org Subject: SCSI Hangs...possible to reset? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... This afternoon, after 3+ days of uptime, my news server had what appears to be a SCSI bus hang...I'm not *too* concerned about it, but have noticed something "neat" about Solaris. In the same office, we have a Sparc20 running Solaris, and every once in a while, we seem to get a SCSI bus hang there as well, but after Xsecs (seems like about a minute, might be less), the system seems to send a reset and continues on its way. What I'm seeing might not be what I think it is (ie. might not be a SCSI bus hang), but its what it feels like... Now, under BSDi, when I used to run it, the newer versions would actually put out a message to the console when the bus hung, so that you knew what was wrong...so it seems that in the PC world, there is a way to detect a hang... ...the question is, is there no way of issuing a RESET so that the deadlock causing the hang is cleared? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org