Date: Mon, 7 Sep 1998 19:39:02 -0700 (PDT) From: FreeBSD <freebsd@theprisoner.net> To: freebsd-hardware@FreeBSD.ORG Subject: IDE TIMEOUTS and other MISC problems Message-ID: <Pine.BSF.3.96.980907185934.25735E-100000@theprisoner.net>
next in thread | raw e-mail | index | archive | help
Hi, I've been noticing some "errors" for the last few months with my drives. I am going to try to provide as much information as I can so that I don't bother you with any stupid questions. First, if the drives partition have no been accessed in a while (minutes/hours), it takes about 5 seconds to get an access performed. For instance, /saved/system1/ has not been accessed, and an "ls /saved/system1/log.4" would hang for quite awhile, and finally report its results. My first assumption is that it has to do with the timeout messages I've been getting in my syslog. > wd2: interrupt timeout: > wd2: status 50<rdy,seekdone> error 1<no_dam> I looked on the documentation on www.freebsd.org and searched for ide timeouts, and found some information about a workaround for a CMD640 timeout problem dealing with not being able to handle both channels as once. 4.4. What's up with this CMD640 IDE controller? It's broken. It cannot handle commands on both channels simultaneously. There's a workaround available now and it is enabled automatically if your system uses this chip. For the details refer to the manual page of the disk driver (man 4 wd). If you're already running FreeBSD 2.2.1 or 2.2.2 with a CMD640 IDE controller and you want to use the second channel, build a new kernel with options "CMD640" enabled. This is the default for 2.2.5 and later. Now, I looked into my kernel config from the last time I compiled it, and I do have that enabled. bash# grep CMD640 KNIGHT options "CMD640" # work around CMD640 chip deficiency So what could be causing this problem, and is there another resource with information about this specific problem? I've done quite a bit searching, and I'm sorry if I overlooked something that was obvious. Knight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980907185934.25735E-100000>