From owner-freebsd-questions Sun Feb 24 10:32: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.mango-bay.com (mail.mango-bay.com [208.206.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 219FF37B405 for ; Sun, 24 Feb 2002 10:31:50 -0800 (PST) Received: from barbish ([63.70.155.115]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Sun, 24 Feb 2002 13:36:17 -0500 From: "Joe & Fhe Barbish" To: "Jan Srzednicki" Cc: "FBSDQ" Subject: RE: CMD 649 UDMA problem Date: Sun, 24 Feb 2002 13:31:47 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You were unclear about how many HD you have on the expansion controller. But if you have a UDMA100 & UDMA66 HD on the same ribbon then the problem is the controller has stepped down to the lowest speed device on the ribbon. Only put like speed HD on same ribbon. Or another area to check is PC hardware bios, verify HD expansion card is not sharing irq with some other device, this is very very important. -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jan Srzednicki Sent: Sunday, February 24, 2002 1:17 PM To: freebsd-questions@freebsd.org Subject: CMD 649 UDMA problem Hello, I put the Winfast CMD 649 UDMA100 controler to my server. After boot everything seems to be fine: atapci0: port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 irq 11 at device 4.0 on pci0 ad4: 19470MB [39560/16/63] at ata2-master UDMA100 ad6: 19536MB [39693/16/63] at ata3-master UDMA66 But, after 4 days the system stopped, flooding the console with messages saying "timeout for command something, resetting, timeout.. on device /dev/ad4". I can't paste it from logfiles, as the disk was not working. All I could do is reset it. The curious thing is that a soft reset didn't help, the controler's BIOS hung on detecting devices. I turned power off and on and it worked. Does that mean that this controler is certainly broken? Ir could it be the hard disk (maybe it doesn't like UDMA100?). Is there any way to force UDMA66 mode on that first drive? System version is 4.5-STABLE built about 2 weeks ago. Before installing that controller I had no problems with this system. What is the best way to track the problem? -- Winfried mail: winfried@dream.vg http://violent.dream.vg JS500-RIPE Warning: Never underestimate the power of stupid people in large numbers. 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