From owner-freebsd-current@FreeBSD.ORG Sun Sep 9 11:10:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E72A916A469 for ; Sun, 9 Sep 2007 11:10:31 +0000 (UTC) (envelope-from marinosi@diogenis.ceid.upatras.gr) Received: from poseidon.ceid.upatras.gr (poseidon.ceid.upatras.gr [150.140.141.169]) by mx1.freebsd.org (Postfix) with ESMTP id 7FAA113C468 for ; Sun, 9 Sep 2007 11:10:30 +0000 (UTC) (envelope-from marinosi@diogenis.ceid.upatras.gr) Received: from mail.ceid.upatras.gr (unknown [10.1.0.143]) by poseidon.ceid.upatras.gr (Postfix) with ESMTP id A466FEB496C for ; Sun, 9 Sep 2007 14:10:08 +0300 (EEST) Received: from localhost (europa.ceid.upatras.gr [127.0.0.1]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 43CD9158828 for ; Sun, 9 Sep 2007 14:10:08 +0300 (EEST) X-Virus-Scanned: amavisd-new at ceid.upatras.gr Received: from mail.ceid.upatras.gr ([127.0.0.1]) by localhost (europa.ceid.upatras.gr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q315Rpk0phLN for ; Sun, 9 Sep 2007 14:10:08 +0300 (EEST) Received: from diogenis.ceid.upatras.gr (unknown [10.1.0.181]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 1AA1715880B for ; Sun, 9 Sep 2007 14:10:08 +0300 (EEST) Received: by diogenis.ceid.upatras.gr (Postfix, from userid 3149) id 5E1438FF18; Sun, 9 Sep 2007 14:10:06 +0300 (EEST) Date: Sun, 9 Sep 2007 14:10:06 +0300 From: Marinos Ilias To: freebsd-current@freebsd.org Message-ID: <20070909111006.GA5499@ceid.upatras.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: Re: SATA DMA errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Sep 2007 11:10:32 -0000 Hello Andrew, When I had the problem , about 3 days ago , I've boot an older current , fscked the (very) corrupted file systems and then I 've built the latest current , which I have about 3 or 4 days now.It seemed to work well without any problems with my SATA disks , but there wasn't any heavy I/O to the disks to let me know. Today , I 've tried to concatenate 2 dvd images , about 2 G each and I saw again those READ_DMA errors for my SATA disk, hearing it spinning, and my whole system stuck .Now again , the same scenario , I've boot my old working current (and I won't try any heavy I/O at all :-P ) . Is something new commited and breaks SATA? For my system ( dmesg | grep -i sata ) : atapci0: port 0xdf00-0xdf3f,0xdfa0-0xdfaf,0xd880-0xd8ff mem 0xfeafe000-0xfeafefff,0xfeac0000-0xfeadffff irq 23 at device 4.0 on pci3 atapci2: port 0xefe0-0xefe7,0xefac-0xefaf,0xefa0-0xefa7,0xefa8-0xefab,0xef60-0xef6f irq 18 at device 31.2 on pci0 ad10: 76293MB at ata5-master SATA150 ad12: 76319MB at ata6-master SATA150 atapci0: port 0xdf00-0xdf3f,0xdfa0-0xdfaf,0xd880-0xd8ff mem 0xfeafe000-0xfeafefff,0xfeac0000-0xfeadffff irq 23 at device 4.0 on pci3 atapci2: port 0xefe0-0xefe7,0xefac-0xefaf,0xefa0-0xefa7,0xefa8-0xefab,0xef60-0xef6f irq 18 at device 31.2 on pci0 ad10: 76293MB at ata5-master SATA150 ad12: 76319MB at ata6-master SATA150 atapci0: port 0xdf00-0xdf3f,0xdfa0-0xdfaf,0xd880-0xd8ff mem 0xfeafe000-0xfeafefff,0xfeac0000-0xfeadffff irq 23 at device 4.0 on pci3 atapci2: port 0xefe0-0xefe7,0xefac-0xefaf,0xefa0-0xefa7,0xefa8-0xefab,0xef60-0xef6f irq 18 at device 31.2 on pci0 ad10: 76293MB at ata5-master SATA150 ad12: 76319MB at ata6-master SATA150 Thank you