From owner-freebsd-current@FreeBSD.ORG Wed Sep 15 16:42:53 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 21AF616A4CE for ; Wed, 15 Sep 2004 16:42:53 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7797243D41 for ; Wed, 15 Sep 2004 16:42:52 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i8FGgphF010257; Wed, 15 Sep 2004 18:42:51 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <4148710A.5070706@DeepCore.dk> Date: Wed, 15 Sep 2004 18:42:50 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik 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> In-Reply-To: <1120.66.11.183.178.1095266341.squirrel@66.11.183.178> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable 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 16:42:53 -0000 Mike Jakubik wrote: > S=F8ren Schmidt said: >=20 >=20 >>You are having massive ICRC problems which are different and most likel= y >>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=20 somthing else is blocking interrupt delivery but its just a hunch... -S=F8ren