Date: Wed, 08 Dec 1999 17:24:19 +0100 From: "D. Rock" <rock@dead-end.net> To: Doug Ambrisko <ambrisko@whistle.com> Cc: <current@FreeBSD.ORG> Subject: Re: ATA driver as the default Message-ID: <384E8633.BD23E6CC@dead-end.net> References: <199912071957.LAA31946@whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Ambrisko schrieb: > > D. Rock writes: > | I just re-enabled the ATA driver again after reading the change log > | of better error handling and automatic falldown DMA->PIO under specific > | circumstances. > | But a few days later, while making world (with the ata driver), the > | system > | crashed quite heavily. The file system was totally screwed up afterwards > | (I found my /usr/local after some heavy searching: It magically > | moved to /usr/obj/usr/src/tmp/usr/share/zoneinfo (!) and got tons of > | fsck > | messages). The file system had softupdates enabled. I don't know the > | last kernel messages before the crash (was running X at that time). > > You might want to look at ata-disk.c and the timeout value around line > 438: > > /* start timeout for this transfer */ > if (panicstr) > request->timeout_handle.callout = NULL; > else > request->timeout_handle = > timeout((timeout_t*)ad_timeout, request, 5*hz); > > Originally it was 3s and recently increased to 5s. Personally > I switched it to 30s after it trashed my filesystem when it was 3s. > The issue was that 3s, is that it is to short to wait for my laptop's > drive to spin back up. Sometimes I would get a corrupted read sometimes on > a write it would trash things. I noticed in the old wd driver that > it tried 10s first then a couple 3s timeouts. After making this > change my system has been rock solid when the drive spins down. > Note I haven't tried to tune this value since trashing a 14G filesystem > is pain full. I don't think I have the same problem. My drive definitely doesn't spin down. It sometimes occurs during heavy usage, so the drive should still be very alive. With PIO mode I also don't have any timeout problems. I also had the same DMA problems with the old wd driver and under Windows. The problem is, that the new driver doesn't allow to selectively turn off DMA for problematic devices. I now had commented out the DMA activation code in ata-disk.c (DMA is still activited on the CD-ROM drive though) and I will see how the system behaves. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?384E8633.BD23E6CC>