From owner-freebsd-stable@FreeBSD.ORG Tue Mar 27 21:17:39 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0DE816A405 for ; Tue, 27 Mar 2007 21:17:39 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 51E4313C465 for ; Tue, 27 Mar 2007 21:17:38 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l2RLHWA9043078; Tue, 27 Mar 2007 15:17:37 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <460989EB.7070108@samsco.org> Date: Tue, 27 Mar 2007 15:17:31 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: JoaoBR References: <200703271805.50708.joao@matik.com.br> In-Reply-To: <200703271805.50708.joao@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 27 Mar 2007 14:17:37 -0700 (MST) X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: scsi error with latest sources X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2007 21:17:39 -0000 JoaoBR wrote: > hi, somebody knows to interprete this scsi error I get after upgrading amd64 > with sources from 26/03/ or is this a hardware problem? > You either have a failing disk or a power supply that is underpowered and/or failing. In short, check your hardware =-) Scott