From owner-freebsd-current@FreeBSD.ORG Fri Sep 7 21:25:55 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 3F6DA16A417 for ; Fri, 7 Sep 2007 21:25:55 +0000 (UTC) (envelope-from andrew_terekhov@yahoo.com) Received: from web54407.mail.yahoo.com (web54407.mail.yahoo.com [206.190.49.137]) by mx1.freebsd.org (Postfix) with SMTP id DF9EA13C45B for ; Fri, 7 Sep 2007 21:25:54 +0000 (UTC) (envelope-from andrew_terekhov@yahoo.com) Received: (qmail 47147 invoked by uid 60001); 7 Sep 2007 20:59:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=mD24/VtOeFSS5T8Scb9YXLWC3Tg8G+Iic3aFgUgWjjhoy61yihSepIuT4+gdtROno7LmhE4MkPoLpWXGfLfpiykBHvb9YbPeBfC9EA4HYg0uK5n8SVwq36S6YIZW3Ijj8k+bmpxehscj0vAdP8/cBMeQjaYyF/txeQ7gU5ZpTZ4=; X-YMail-OSG: HjHTl2YVM1ndx0uy2xN9g5L0zPypHbhbhyOzd4kje0VR6APzx2WGNi7bWF0AEaJPRg-- Received: from [69.147.98.50] by web54407.mail.yahoo.com via HTTP; Fri, 07 Sep 2007 13:59:14 PDT X-Mailer: YahooMailRC/651.50 YahooMailWebService/0.7.134 Date: Fri, 7 Sep 2007 13:59:14 -0700 (PDT) From: andrew_terekhov@yahoo.com To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: <526915.46102.qm@web54407.mail.yahoo.com> Subject: 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: Fri, 07 Sep 2007 21:25:55 -0000 Current kernel/world (i386) from a few days ago on 2 different computers ex= hibits DMA read/write =0Aerrors when accessing SATA drives. IDE drives work= fine.=0A=0AErrors are similar to described here:=0A=0Ahttp://lists.freebsd= .org/pipermail/freebsd-current/2007-September/076776.html=0Ahttp://lists.fr= eebsd.org/pipermail/freebsd-current/2007-September/076699.html=0Ahttp://lis= ts.freebsd.org/pipermail/freebsd-questions/2007-August/156029.html=0A=0AAft= er a few DMA errors both systems usually hard lockup.=0A=0AI took advice fo= und here:=0A=0Ahttp://lists.freebsd.org/pipermail/freebsd-current/2007-Augu= st/076219.html=0A=0Aand rebuilt both systems with =0A=0A*date=3D2007.06.16.= 03.00.00=0A=0AThe problem was gone - running for the second day with heavy = use of SATA drives with no errors. =0ABefore it took a few minutes to bring= down computers.=0A=0A=0AHardware:=0A=0ASystem 1:=0A=0Aatapci1: port 0xe300-0xe307,0xe400-0xe403,0xe500-0xe507,0xe600-0xe= 603,0xe700-0xe70f irq 11 at device 5.0 on pci0=0Aad4: 305245MB at ata2-master SATA150=0A=0A=0ASystem 2:=0A=0Aatapci2: port 0xcc00-0xcc7f,0xc800-0xc8ff mem 0xfe= aff000-0xfeafffff,0xfeac0000-0xfeadffff irq 16 at device 3.0 on pci5=0Aad8:= 194481MB at ata4-master SATA150=0Aad10: 286168MB= at ata5-master SATA300=0A=0A=0AIt seems someth= ing was changed after 2007-06-16 that broke SATA in current.=0A=0A=0A=0A=0A= =0A =0A______________________________________________________________= ______________________=0AYahoo! oneSearch: Finally, mobile search =0Athat g= ives answers, not web links. =0Ahttp://mobile.yahoo.com/mobileweb/onesearch= ?refer=3D1ONXIC