From owner-freebsd-current@FreeBSD.ORG Wed Sep 15 21:08:56 2004 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 8966E16A4CE for ; Wed, 15 Sep 2004 21:08:56 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E519743D31 for ; Wed, 15 Sep 2004 21:08:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8FL87K6004312; Wed, 15 Sep 2004 15:08:07 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4148AE9E.5050905@samsco.org> Date: Wed, 15 Sep 2004 15:05:34 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <20040915.021427.74736836.fujita@soum.co.jp> <259306135.20040915091315@wilbury.sk> <41482A17.8020903@DeepCore.dk> <1120.66.11.183.178.1095266341.squirrel@66.11.183.178> <4148710A.5070706@DeepCore.dk> In-Reply-To: <4148710A.5070706@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.2 required=3.8 tests=SUBJ_HAS_UNIQ_ID autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Mike Jakubik cc: DanGer cc: current@freebsd.org Subject: Re: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=207594611 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 15 Sep 2004 21:08:56 -0000 Søren Schmidt wrote: > Mike Jakubik wrote: > >> Søren Schmidt said: >> >> >>> You are having massive ICRC problems which are different and most likely >>> due to bad cables/connectors or cables that are turned around (blue >>> connector at controller, black/grey at devices), or it can be a >>> weak/overloaded PSU. >>> >> This is a different error message from what everyone else, including >> me is >> reporting. What about the errors we are getting? > > > I have no idea, I can't reproduce the problem at all. However I suspect > somthing else is blocking interrupt delivery but its just a hunch... > > -Søren > I'm finding it hard to imagine a scenario where a timeout could fire but not a hardware interrupt. Nothing usually shares the interrupt vectors with ATA, so it's pretty unlikely that the ata ithread is being blocked by anything but itself. Scott