From owner-freebsd-scsi Tue Aug 19 21:08:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26510 for freebsd-scsi-outgoing; Tue, 19 Aug 1997 21:08:00 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26503 for ; Tue, 19 Aug 1997 21:07:56 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id WAA09344; Tue, 19 Aug 1997 22:07:46 -0600 (MDT) Message-Id: <199708200407.WAA09344@pluto.plutotech.com> To: Raul Zighelboim cc: "'Justin T. Gibbs'" , Greg Lehey , FreeBSD SCSI Mailing List Subject: Re: Bus resets. Grrrr. In-reply-to: Your message of "Tue, 19 Aug 1997 23:04:57 CDT." Date: Tue, 19 Aug 1997 22:07:07 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> The system hung solid with no kernel messages or were you in X so >> you couldn't see them? There is no guarantee that driver messages >> will make it into the log file if the SCSI bus is wedged. I wasn't >> aware of any problems with SCB paging, so I'd be very interrested >> in any information you can provide on this problem. In most cases, >> BTW, SCB paging isn't a win unless you are also using tagged queuing >> (option AHC_TAGENABLE). >> >> > [Raul Zighelboim] MMM... I set options AHC_SCBPAGING_ENABLE on >the kernel a few days ago, and the system hanged solid while running the >'bytebench' benchmark. Removed the option, and run bytebench clean: > > This under 2.2.2-RELEASE with 2 AHC cards and some quantum >viking drives: 2.2.2-RELEASE doesn't have the latest aic7xxx driver. Try running 2.2-stable or current instead. I'll try to repro this tomorrow using bytebech tomorrow as well. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================