From owner-freebsd-questions Fri Nov 5 15: 7:39 1999 Delivered-To: freebsd-questions@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [207.249.162.252]) by hub.freebsd.org (Postfix) with ESMTP id 108CA14CF3 for ; Fri, 5 Nov 1999 15:07:30 -0800 (PST) (envelope-from ales@megared.net.mx) Received: from ales (pix.megared.net.mx [207.249.162.253] (may be forged)) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id RAA28334; Fri, 5 Nov 1999 17:08:45 -0600 (CST) (envelope-from ales@megared.net.mx) Message-ID: <016c01bf27e2$590ed660$dbdffea9@megared.net.mx> Reply-To: "Alejandro Ramirez" From: "Alejandro Ramirez" To: , References: Subject: RE: RAID/FreeBSD Date: Fri, 5 Nov 1999 17:06:05 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I saw this post a few days ago, it may help you: On Sat, 30 Oct 1999, Mike wrote: > Hi all! > > It seems once awhile the FreeBSD-3.3-Release system hangs with the > following message: > > /kernel: (da0:dpt0:0:0:0) : CCB 0xc550807c - timeout. > /kernel: (da0:dpt0:0:0:0) : CCB 0xc5508744 - timeout. You probably want to put the "DPT_VERIFY_HINTR" and "DPT_LOST_IRQ" options into your kernel config file. Tom I Hope this Helps... Ales ----- Original Message ----- From: To: Sent: Thursday, November 04, 1999 2:58 PM Subject: RAID/FreeBSD > DPT 3334UW with baracuda drives, FreeBSD 3.2-Release > Machine stays up for a day or two then just locks with > this message for no aparent reason. > > da1:dpt:1:10:0 CCB 0xc7f3cb24 -- Timed out. > > I happen to notice while it was showing this that > one drive in the array was being accessed. Then this > message after hanging for about a minute on the previous > message > > Syncing disks 3 3 111111111111111111 -Giving up > > Then it reboots the machine and fsck can't fix it. > Spent a good couple hours on the phone with DPT and > they offered no real fixes. This is the 3rd time this > has happened. No logs at all on the system as to what > is going wrong. > Bad Controler? Bad OS? Bad me? > > > Keith.... > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message