From owner-freebsd-scsi@FreeBSD.ORG Mon Mar 6 23:30:33 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E21F16A420 for ; Mon, 6 Mar 2006 23:30:33 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDB243D45 for ; Mon, 6 Mar 2006 23:30:32 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k26NUUTM076837; Mon, 6 Mar 2006 20:30:30 -0300 (BRT) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-scsi@freebsd.org Date: Mon, 6 Mar 2006 20:30:22 -0300 User-Agent: KMail/1.9.1 References: <20060306162407.Q5393@daemon.mistermishap.net> In-Reply-To: <20060306162407.Q5393@daemon.mistermishap.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603062030.22894.asstec@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: Rob Watt Subject: Re: SCB timeout and other errors + system hang with adaptec/seagate X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2006 23:30:33 -0000 On Monday 06 March 2006 18:58, Rob Watt wrote: > Our machines are all dual dual-core opterons with hot-swap backplanes, > Tyan K8SR motherboards with onboard Adaptec 7902 controllers. The drives > are Seagate ST3146707LC U320. > > We have a number of these machines, and we have experienced this problem > on almost half of them (but never on the other half - all with the same > exact hardware). During high disk usage times they start generating scsi > errors and card state dumps. Eventually the machine will hang (not panic, > not reboot) and will have to be power cycled to reboot. We can't seem to > force it to happen predictably, but with usage they will eventaully hang > after 1 hour to 2 days. Hi I like to suggest you to check two points =2D powersupply =2D irq conflict I had similar scsi problems and the above problems where the cause Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br