From owner-freebsd-current@FreeBSD.ORG Fri Jan 14 07:38:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2931E16A4CF for ; Fri, 14 Jan 2005 07:38:11 +0000 (GMT) Received: from grerelbul01.net.external.hp.com (grerelbul01.net.external.hp.com [155.208.255.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45AD643D53 for ; Fri, 14 Jan 2005 07:38:10 +0000 (GMT) (envelope-from michaelc@tmbbobmc.bbn.hp.com) Received: from ebsc01.bbn.hp.com (ebsc01.bbn.hp.com [15.136.121.146]) by grerelbul01.net.external.hp.com (Postfix) with ESMTP id 20AD337F6D; Fri, 14 Jan 2005 08:38:35 +0100 (CET) Received: from tmbbobmc.bbn.hp.com (tmbbobmc.bbn.hp.com [15.136.123.54]) ESMTP id IAA10679; Fri, 14 Jan 2005 08:41:55 +0100 (MET) Received: from tmbbobmc.bbn.hp.com (localhost.localdomain [127.0.0.1]) by tmbbobmc.bbn.hp.com (8.12.11/8.12.11) with ESMTP id j0E7cvhl005217; Fri, 14 Jan 2005 08:38:57 +0100 Received: from localhost (michaelc@localhost)j0E7cvbS005214; Fri, 14 Jan 2005 08:38:57 +0100 Date: Fri, 14 Jan 2005 08:38:56 +0100 (CET) From: Michael Class To: "Daniel O'Connor" In-Reply-To: <200501141112.00237.doconnor@gsoft.com.au> Message-ID: References: <41E568CE.9030905@gmx.de> <200501141112.00237.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Fri, 14 Jan 2005 13:02:12 +0000 cc: current@freebsd.org Subject: Re: SIL3112 and Maxtor 6Y160M0 SATA Disk: DMA Failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: michael.class@gmx.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 07:38:11 -0000 On Fri, 14 Jan 2005, Daniel O'Connor wrote: > On Thu, 13 Jan 2005 04:43, Michael Class wrote: >> Unfortunately when I do attach my Maxtor SATA disk to this controller >> I do only get DMA errors. This is all on a recent 6.0-CURRENT system >> and can be reproduced with a GENERIC kernel. >> Anything I could do to track this further down? > > I good start would be to post the stack trace of the crash.. Thank you for your answer! Sorry for not making myself clear enough. The system does not crash! So there are obviously no stack traces of crashes ... The attached disk (ad4) simply does not work, generating DMA errors that can be seen in the verbose bootlog that was attached to my first mail. The disk by itself seems to be o.k. as it is working on an other system running FBSD 6.0-current attached to a Promise SATA controller. The lines that are relevant to this in the bootlog seem to be: (but I attached the whole log to the original mail, so that someone who might be interessted can read more about the exact specification of the system used) ... atapci1: port 0xac00-0xac0f,0xb000-0xb003,0xb400-0xb407,0xb800-0xb803,0xbc00-0xbc07 mem 0xdffffc00-0xdffffdff irq 17 at device 13.0 on pci0 ... ad4: ATA-7 disk at ata2-master ad4: 156334MB (320173056 sectors), 317632 C, 16 H, 63 S, 512 B ad4: 16 secs/int, 1 depth queue, SATA150 ... GEOM: new disk ad4 ad4: TIMEOUT - READ_DMA retrying (2 retries left) LBA=0 ata2: reiniting channel .. .... ata2: reset tp1 mask=01 ostat0=50 ostat1=00 ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: resetting done .. ad4: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ata2: device config done .. ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ata2: reiniting channel .. ata2: reset tp1 mask=01 ostat0=50 ostat1=00 ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: resetting done .. ad4: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ata2: device config done .. ata2: reiniting channel .. ata2: reset tp1 mask=01 ostat0=50 ostat1=00 ad4: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=00 devices=0x1 ata2: resetting done .. ad4: pio=0x0c wdma=0x22 udma=0x46 cable=40pin ata2: device config done .. ad4: FAILURE - READ_DMA timed out ad4: FAILURE - READ_DMA status=51 error=4 LBA=0 Thank you Michael