Date: Fri, 25 Jun 1999 13:30:01 -0700 (PDT) From: jim@web-ex.com To: freebsd-gnats-submit@freebsd.org Subject: kern/12395: Buslogic SCSI cards (BT948) time out under light loads on several different servers Message-ID: <19990625203001.CF1BA15442@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 12395 >Category: kern >Synopsis: Buslogic SCSI cards (BT948) time out under light loads on several different servers >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 25 13:40:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Jim Cassata >Release: FreeBSD 3.2, problem started with 3.0-REL >Organization: Web Express, Inc. >Environment: FreeBSD homer.web-ex.com 3.2-RELEASE FreeBSD 3.2-RELEASE #1: Thu May 27 11:32:09 GMT 1999 root@homer.web-ex.com:/usr/src/sys/compile/Homer i386 >Description: With the upgrades to 3.0-REL, the scsi cards (Buslogic BT948s) started to hang and report timeouts in the kernel on all (3) of the machines with the combination of BT948 cards and 3.0-REL or newer (up to 3.2) Here is a kernel message: (da0:bt0:0:0:0): CCB 0xc5548500 - timed out (da0:bt0:0:0:0): CCB 0xc5548500 - timed out bt0: No longer in timeout (da0:bt0:0:0:0): CCB 0xc55487c0 - timed out (da0:bt0:0:0:0): CCB 0xc55487c0 - timed out bt0: No longer in timeout (da0:bt0:0:0:0): CCB 0xc5549840 - timed out (da0:bt0:0:0:0): CCB 0xc5549840 - timed out bt0: No longer in timeout (da0:bt0:0:0:0): CCB 0xc5548a80 - timed out (da0:bt0:0:0:0): CCB 0xc5548a80 - timed out bt0: No longer in timeout (da0:bt0:0:0:0): CCB 0xc554a1c0 - timed out (da0:bt0:0:0:0): CCB 0xc554a1c0 - timed out bt0: No longer in timeout During the timeout no disk access is available, and timeouts last from 10 to 30 seconds, during which keyboard and mouse inputs are queued up and all execute upon disk being available again. I posted this problem in December?? when 3.0-REL was out and was told to install a newer SNAP as it was a recognized problem and the newer code fixed it., problem persists to this day on some very current 3.2 machines. >How-To-Repeat: do something with a fair amount of disk access (download the ports collection, serve content, etc.) >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990625203001.CF1BA15442>