From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Stark Subject: Re: SMART support for libata Date: 08 Jun 2005 23:08:59 -0400 Message-ID: <873brs5ir8.fsf@stark.xeocode.com> References: <87y8g8r4y6.fsf@stark.xeocode.com> <41B7EFA3.8000007@pobox.com> <87br6g6ayr.fsf@stark.xeocode.com> <42A73E6E.80808@rtr.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from stark.xeocode.com ([216.58.44.227]:7363 "EHLO stark.xeocode.com") by vger.kernel.org with ESMTP id S262247AbVFIDJJ (ORCPT ); Wed, 8 Jun 2005 23:09:09 -0400 In-Reply-To: <42A73E6E.80808@rtr.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mark Lord Cc: Greg Stark , Jeff Garzik , linux-kernel@vger.kernel.org, "linux-ide@vger.kernel.org" Mark Lord writes: > Greg Stark wrote: > > > > getting really hot so I put it to sleep with "hdparm -Y". > > Now whenever smartd probes that drive my system freezes for a few seconds and > > I get this in my syslog: > > Jun 8 12:49:36 stark kernel: hda: status timeout: status=0xd0 { Busy } > > Jun 8 12:49:36 stark kernel: Jun 8 12:49:36 stark kernel: ide: failed > > opcode was: 0xe5 > > That is normal and expected behaviour. > A "sleeping" drive never responds to commands > until woken with a reset. I'm fine with errors and SMART failing to get any data. It's the part about my entire computer freezing for 5-10s that doesn't seem kosher to me. > You should be using "-y" (standby) instead of "-Y" (sleep). I'll try that. But that's not going to make it spin up when it gets a SMART query is it? -- greg