From owner-freebsd-questions@FreeBSD.ORG Tue Dec 6 19:42:39 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A44CA1065670 for ; Tue, 6 Dec 2011 19:42:39 +0000 (UTC) (envelope-from linnemannr@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7C45D8FC08 for ; Tue, 6 Dec 2011 19:42:39 +0000 (UTC) Received: by dakp5 with SMTP id p5so3372529dak.13 for ; Tue, 06 Dec 2011 11:42:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=D1xgRnbaftj80zjCqGb4pEaSCNr40O0m07mu18JisQc=; b=Gddsk55Wtj8w5g4i1bEt2q30lMvsLTWZ7Ovi01FuBUKOXwYUIZkeJPybjQcGlBgOw8 yOX0poDOVdHbyJJukg0L5R3oVxEbCwYRo/s2eP5FXvkhl7uZhhBV/p92tYTCo0YUchcF wtxhrGhpkId7/p/GOMsFwGfuE97BUGnvZOHhY= MIME-Version: 1.0 Received: by 10.68.59.4 with SMTP id v4mr34931013pbq.114.1323200558938; Tue, 06 Dec 2011 11:42:38 -0800 (PST) Sender: linnemannr@gmail.com Received: by 10.142.196.12 with HTTP; Tue, 6 Dec 2011 11:42:38 -0800 (PST) In-Reply-To: References: <4EDE37A1.5030306@ulb.ac.be> Date: Tue, 6 Dec 2011 13:42:38 -0600 X-Google-Sender-Auth: V4VVkvkw4MBL1q-uJrgzszLN1sQ Message-ID: From: Reid Linnemann To: "C. P. Ghost" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Julien Cigar , FreeBSD Mailing List Subject: Re: AHCI timeout X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2011 19:42:39 -0000 On Tue, Dec 6, 2011 at 12:25 PM, C. P. Ghost wrote: > On Tue, Dec 6, 2011 at 4:41 PM, Julien Cigar wrote: >> Hello, >> >> I'm running 9.0-RC3 on a HP Proliant Microserver (N40L). A disk died in = my >> graid3 array and I replaced it with a new one, and now have tons of: >> >> ahcich3: Timeout on slot 5 port 0 >> ahcich3: is 00000000 cs 00000000 ss 00003f60 rs 00003f60 tfd 40 serr >> 00000000 cmd 0000ed17 > > Check the connectors, both on disk and on the controller. They're > usually the culprit. Sometimes it is also a firmware problem, but > I'll try to replace the cables first. > >> (...) >> >> Those are Seagate disks: >> >> jcigar@backup conf % sudo camcontrol devlist >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 at scbus0 target 0 lu= n 0 (pass0,ada0) >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0at scbus1 target 0 lu= n 0 (pass1,ada1) >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0at scbus2 target 0 lu= n 0 (pass2,ada2) >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0at scbus3 target 0 lu= n 0 (pass3,ada3) >> >> The controller is: >> >> ahci0@pci0:0:17:0: =A0 =A0 =A0class=3D0x010601 card=3D0x1609103c chip=3D= 0x43911002 >> rev=3D0x40 hdr=3D0x00 >> =A0 =A0vendor =A0 =A0 =3D 'ATI Technologies Inc' >> =A0 =A0device =A0 =A0 =3D 'SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]= ' >> =A0 =A0class =A0 =A0 =A0=3D mass storage >> =A0 =A0subclass =A0 =3D SATA >> >> jcigar@backup conf % vmstat -i >> interrupt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0total =A0 = =A0 =A0 rate >> irq17: ehci0 ehci1+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02 =A0 =A0 =A0= =A0 =A00 >> irq18: ohci0 ohci1+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 30 =A0 =A0 =A0 = =A0 =A00 >> irq256: bge0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 31354 =A0 =A0 = =A0 =A0 =A04 >> irq257: ahci0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 19012658 =A0 =A0 =A0 2= 477 >> irq258: hpet0:t0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4926229 =A0 =A0 =A0 =A0= 641 >> irq259: hpet0:t1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4635261 =A0 =A0 =A0 =A0= 603 >> Total =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 28605534 =A0 = =A0 =A0 3727 >> >> >> Any idea what could be the cause of this ... ? >> >> >> Thanks, >> Julien > > -cpghost. > > -- > Cordula's Web. http://www.cordula.ws/ > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" I've had similar problems with a failing power supply when I used to run a gmirror on 7-STABLE. I was not running with AHCI, so I did not get the same messages; but I did get repeated WRITE_DMA timeouts on my da disks that eventually resulted in one disk being detached from the mirror. Cold booting was an arduous process because 9 boots of 10 the system would start sputtering out on DMA timeouts almost immediately after mounting the filesystems, and take well over 30 minutes just to get through rc. I changed cables, swapped the disks around, checked smartctl over and over to no avail. Eventually I bought a new rig and hooked it up to the original power supply - the problems persisted. I swapped in the new power supply and hey presto! the problems went away. You mentioned hardware failure in the original disk, so it might not be too far of a stretch to consider the power supply might also have suffered a failure.