Date: Sun, 24 Feb 2002 13:31:47 -0500 From: "Joe & Fhe Barbish" <barbish@a1poweruser.com> To: "Jan Srzednicki" <winfried@student.uci.agh.edu.pl> Cc: "FBSDQ" <questions@FreeBSD.ORG> Subject: RE: CMD 649 UDMA problem Message-ID: <LPBBIGIAAKKEOEJOLEGOGELACIAA.barbish@a1poweruser.com> In-Reply-To: <Pine.GSO.4.44.0202241857090.20099-100000@student.uci.agh.edu.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <CMD 649 ATA100 controller> port 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 irq 11 at device 4.0 on pci0 ad4: 19470MB <QUANTUM FIREBALLlct20 20> [39560/16/63] at ata2-master UDMA100 ad6: 19536MB <ST320423A> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LPBBIGIAAKKEOEJOLEGOGELACIAA.barbish>