From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: SATA drive keeps hard resetting Date: Wed, 12 Dec 2007 17:27:59 +0900 Message-ID: <475F9B8F.1050208@gmail.com> References: <475E08FC.9010809@gmail.com> <475E5D51.8010902@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from wa-out-1112.google.com ([209.85.146.176]:64541 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754201AbXLLI2M (ORCPT ); Wed, 12 Dec 2007 03:28:12 -0500 Received: by wa-out-1112.google.com with SMTP id v27so248689wah.23 for ; Wed, 12 Dec 2007 00:28:12 -0800 (PST) In-Reply-To: <475E5D51.8010902@msgid.tls.msk.ru> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Michael Tokarev Cc: =?ISO-8859-1?Q?Mat=ED=ADas_Alejandro_Torres?= , linux-ide@vger.kernel.org Michael Tokarev wrote: > Mat=ED=ADas Alejandro Torres wrote: >> Hi all, >> >> I have a SATA drive in a motherboard with an ATI SB600 chipset that >> until now worked just fine. >> The disk seems fine but after a while it start making noises (like >> spinning up) and the computer freezes during 2 or 3 seconds. I think= my >> SATA drive is broken, or maybe the motherboard. This is what dmesg s= ays: >> >> [ 229.096000] ata4: exception Emask 0x10 SAct 0x0 SErr 0x90200 acti= on 0x6 frozen >=20 > See http://marc.info/?l=3Dlinux-ide&m=3D119707355016060&w=3D2 > ... >> I'm using Ubuntu 7.10 with kernel 2.6.22-14-generic in a dual proces= sor >> computer. Below there's some hardware information. The output of dme= sg >> is attached. Thanks! >=20 > That patch will not apply cleanly to 2.6.22 - it will show rejects > in libata-core.c. Those are OK - it's a cleanup of wrongly blacklist= ed > drives. The main part - in ahci.c - is the one that's needed. Matias's problem doesn't have anything to do with spurious completion. PHY RDY changed and HSM violation are completely different error condit= ions. I think either the harddrive or power supply is dying. smartctl -a might show something but I'm not too hopeful. The surest way is to connect the drive to a different PSU and see whether the problem goes away but if all other drives on the system is fine, I would just throw away the harddrive. Thanks. --=20 tejun