From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965058AbbD0Tqd (ORCPT ); Mon, 27 Apr 2015 15:46:33 -0400 Received: from static.rcn.com ([207.172.69.99]:28102 "EHLO newtao.randomstring.org" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753135AbbD0Tqc convert rfc822-to-8bit (ORCPT ); Mon, 27 Apr 2015 15:46:32 -0400 X-Greylist: delayed 316 seconds by postgrey-1.27 at vger.kernel.org; Mon, 27 Apr 2015 15:46:32 EDT Date: Mon, 27 Apr 2015 15:41:14 -0400 From: Dan Ritter To: Nicolas George Cc: debian-user@lists.debian.org, linux-kernel@vger.kernel.org Subject: Re: ATA resets with Intel 8/C220 and HGST drive Message-ID: <20150427194114.GW19736@randomstring.org> References: <20150427130358.GA522233@phare.normalesup.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20150427130358.GA522233@phare.normalesup.org> X-Message-Flag: Cannot contact reaper.nsa.gov. Trying bucket.cia.gov.. Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 27, 2015 at 03:03:58PM +0200, Nicolas George wrote: > [ 409.772773] ata2.00: failed command: WRITE FPDMA QUEUED > [ 409.772776] ata2.00: cmd 61/28:88:e0:a3:04/00:00:02:00:00/40 tag 17 ncq 20480 out > [ 409.772776] res 50/00:28:e0:a3:04/00:00:02:00:00/40 Emask 0x10 (ATA bus error) > [ 409.772777] ata2.00: status: { DRDY } > [ 409.772779] ata2: hard resetting link > [ 410.092732] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) > [ 410.097670] ata2.00: configured for UDMA/133 > > Last week, hinted by the penultimate line, I tried to lower the speed of the > SATA link permanently, and it worked. I did this by adding > "libata.force=2:3.0Gbps" to the kernel command line (configured using > /etc/default/grub). > > Since then, no reset happened; I am confident that seven days without them > are not a coincidence. Two options occur to me: 1. There may be a firmware update for your disk. 2. You may have a bad SATA cable. -dsr-