Date: Wed, 13 Oct 2004 15:51:49 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: miha@ghuug.org Cc: freebsd-hackers@freebsd.org Subject: Re: ad0: FAILURE - WRITE_DMA Message-ID: <416D32F5.1090401@DeepCore.dk> In-Reply-To: <200410131303.35695.miha@ghuug.org> References: <200410081937.15068.miha@ghuug.org> <200410091701.01987.miha@ghuug.org> <200410102330.26228.miha@ghuug.org> <200410131303.35695.miha@ghuug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mikhail P. wrote: > On Sunday 10 October 2004 23:30, Mikhail P. wrote: >=20 >>On Saturday 09 October 2004 17:01, Mikhail P. wrote: >> >>>I also got another message off-list, where author suggested to play wi= th >>>UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12 >>>hours, and no timeouts so far.. but I'm quite sure they will get back = in >>>few days. >> >>1.5 days of uptime, running in UDMA66 changes nothing. Still getting >=20 >=20 > Well, now those timeouts popped up on 5.3-BETA7 system with 4 IDE drive= s..=20 > They start appearing with high disk activity. > System had FreeBSD-4.7 prior to that, and has been rock solid for almos= t a=20 > year. Drives have no problems, that's for sure (4.7 did not show up any= =20 > timeouts, with uptime for months).. >=20 > I don't know what to think - is ATA driver horribly broken in 5.x? Well, thats not up to me to judge I guess, but have you tried to change=20 the tripping point for using 48Bit addressing as I suggested earlier ? I cant reproduce this problem with any of the shelfmeters of ATA gear I=20 have here, so your help is needed or it will stay horribly broken :) --=20 -S=F8ren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?416D32F5.1090401>