From owner-freebsd-hackers@FreeBSD.ORG Wed Oct 13 13:59:55 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CA1B16A4CE for ; Wed, 13 Oct 2004 13:59:55 +0000 (GMT) Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id B117F43D1D for ; Wed, 13 Oct 2004 13:59:53 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id 5A32637FCF; Wed, 13 Oct 2004 15:59:52 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 482A737E7B; Wed, 13 Oct 2004 15:59:52 +0200 (CEST) Received: from [192.168.2.10] (h118n1fls31o985.telia.com [213.65.16.118]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 251FD37E4B; Wed, 13 Oct 2004 15:59:51 +0200 (CEST) Message-ID: <416D34D8.9050804@gneto.com> Date: Wed, 13 Oct 2004 15:59:52 +0200 From: Martin Nilsson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: sv, en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <200410081937.15068.miha@ghuug.org> <200410091701.01987.miha@ghuug.org> <200410102330.26228.miha@ghuug.org> <200410131303.35695.miha@ghuug.org> In-Reply-To: <200410131303.35695.miha@ghuug.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: sos@DeepCore.dk Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2004 13:59:55 -0000 Mikhail P. wrote: > Well, now those timeouts popped up on 5.3-BETA7 system with 4 IDE drives.. > They start appearing with high disk activity. > System had FreeBSD-4.7 prior to that, and has been rock solid for almost a > year. Drives have no problems, that's for sure (4.7 did not show up any > timeouts, with uptime for months).. > > I don't know what to think - is ATA driver horribly broken in 5.x? Something is rotten with ATA on 5.x (or I have a rotten motherboard!) I have an E7320 "Lindenhurst VS ICH5R box" with 2*3GHz EM64T Xeons and 2*80GB Seagate SATA disks. Sometimes when booting the whole ATA/SATA system hangs after two READ_DMA or WRITE_DMA timeout errors. This seems to more common when running as AMD64 than i386. I can't remember any hangs after the machine have been up nicely for a couple of min. The 1U box is so noisy that I can't be in the apartment at the same time without going crazy, this and that I can't reproduce it reliably effectively prevents most debugging attempts. /Martin