Date: Thu, 2 Jun 2005 09:48:55 +0100 From: Tony Byrne <freebsd-current@byrnehq.com> To: Tony Byrne <freebsd-current@byrnehq.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Tony Byrne <freebsd@byrnehq.com>, Martin <nakal@nurfuerspam.de> Subject: Re[3]: ATA DMA timeouts Message-ID: <1436791778.20050602094855@byrnehq.com> In-Reply-To: <1148797372.20050601182156@byrnehq.com> References: <1117573047.3095.24.camel@klotz.local> <1684114034.20050601135752@byrnehq.com> <1117645070.1846.8.camel@klotz.local> <1148797372.20050601182156@byrnehq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin, TB> We're now at 2 hours uptime and there is no sign of the ATA TB> timeouts. With the newer kernels the first timeout would appear TB> within 5 to 10 minutes of rebooting. I can't see any changes to TB> the ATA code in the interim so I'm curious as to what could have TB> caused this issue. TB> My hardware is Intel ICH5 based with a Western Digital SATA hard-disk. Well it was too good to last. I came in this morning to find a handful of "ad0: TIMEOUT - ..." in the messages file. It looks like the nightly cron jobs trigger it even for kernel and world prior to May 9th. I get the sense that there are less timeouts with the older kernel, but it could be wishful thinking. If your timeouts have really gone away then it's possible that our problem has a different cause to yours. Can anyone else shed some light on this issue? Regards, Tony. -- Tony Byrne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1436791778.20050602094855>