Package: smartmontools
Version: 5.36-8
Severity: normal

I'm seeing this error repeatedly:

Oct  9 12:22:07 chianti kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 
action 0x2 frozen
Oct  9 12:22:07 chianti kernel: ata4.00: tag 0 cmd 0xb0 Emask 0x2 stat 0x50 err 
0x0 (HSM violation)
Oct  9 12:22:07 chianti kernel: ata4: soft resetting port
Oct  9 12:22:07 chianti kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)
Oct  9 12:22:07 chianti kernel: ata4.00: configured for UDMA/133
Oct  9 12:22:07 chianti kernel: ata4: EH complete

Tejun Heo has posted a patch as follows.

David


From: Tejun Heo <htejun <at> gmail.com>
Subject: Re: smartctl causing HSM violation on sata_nv, 2.6.18
Newsgroups: gmane.linux.ide, gmane.linux.utilities.smartmontools
Date: 2006-09-28 06:54:09 GMT (1 week, 4 days, 12 hours and 32 minutes ago)

Hello, Jim Paris, Bruce Allen.

On Wed, Sep 27, 2006 at 02:33:39PM -0400, Jim Paris wrote:
> Hi Tejun,
> 
> My NVIDIA SATA controller is having some problems with smartctl on
> 2.6.18 (+ the previously mentioned sata_nv patch).  If I try to enable
> Attribute Autosafe (smartctl -S on) or Automatic Offline (smartctl -o
> on), the controller craps out (but recovers).  Executing the same
> command on an identical disk connected to a SiI3132 works fine.  Other
> SMART stuff (reading attributes, running self-tests) seems to be
> behaving just fine.  

This is because smartctl issues AUTOSAVE and AUTO_OFFLINE w/
HDIO_DRIVE_CMD.  Both SMART subcommands are non-data but still use
non-zero NSECT field.  HDIO_DRIVE_CMD assumes data-in protocol when
NSECT is non-zero.  libata HSM implementation is stricter than ide's
and declares HSM violation when device reports command complete when
it's expecting DRQ.

> ### sata_nv controller (CK804):
> 
> # smartctl -data -S on /dev/disk/by-path/pci-0000:00:07.0-scsi-0:0:0:0
> smartctl version 5.36 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce 
> Allen
> Home page is http://smartmontools.sourceforge.net/
> 
> === START OF ENABLE/DISABLE COMMANDS SECTION ===
> Error SMART Enable Auto-save failed: Input/output error
> Smartctl: SMART Enable Attribute Autosave Failed.
> 
> A mandatory SMART command failed: exiting. To continue, add one or more '-T 
> permissive' options.
> 
> 
> ### sata_sil24 controller (SiI3132):
> 
> # smartctl -data -S on /dev/disk/by-path/pci-0000:04:00.0-scsi-0:0:0:0
> smartctl version 5.36 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce 
> Allen
> Home page is http://smartmontools.sourceforge.net/
> 
> === START OF ENABLE/DISABLE COMMANDS SECTION ===
> SMART Attribute Autosave Enabled.

sata_sil24 works because the controller hardware snoops the command
and determines protocol by itself.  So, regardless of what the ioctl
says, it executes the command with non-data protocol.

The following patch against smartmontools-5.36 converts it to use
HDIO_DRIVE_TASK ioctl for AUTOSAVE and AUTO_OFFLINE which don't have
the above issue.

Thanks.

diff -uNr smartmontools-5.36/os_linux.c smartmontools-5.36-fixed/os_linux.c
--- smartmontools-5.36/os_linux.c       2006-04-13 02:02:19.000000000 +0900
+++ smartmontools-5.36-fixed/os_linux.c 2006-09-28 15:41:06.000000000 +0900
 <at>  <at>  -383,14 +383,10  <at>  <at> 
 //   1 if the command succeeded and disk SMART status is "FAILING"

 
-// huge value of buffer size needed because HDIO_DRIVE_CMD assumes
-// that buff[3] is the data size.  Since the ATA_SMART_AUTOSAVE and
-// ATA_SMART_AUTO_OFFLINE use values of 0xf1 and 0xf8 we need the space.
-// Otherwise a 4+512 byte buffer would be enough.
-#define STRANGE_BUFFER_LENGTH (4+512*0xf8)
+#define BUFFER_LEN (4+512)

 int ata_command_interface(int device, smart_command_set command, int select, 
char *data){
-  unsigned char buff[STRANGE_BUFFER_LENGTH];
+  unsigned char buff[BUFFER_LEN];
   // positive: bytes to write to caller.  negative: bytes to READ from
   // caller. zero: non-data command
   int copydata=0;
 <at>  <at>  -407,7 +403,7  <at>  <at> 
   // buff[2] contains the ATA SECTOR COUNT REGISTER

   // clear out buff.  Large enough for HDIO_DRIVE_CMD (4+512 bytes)
-  memset(buff, 0, STRANGE_BUFFER_LENGTH);
+  memset(buff, 0, BUFFER_LEN);

   buff[0]=ATA_SMART_CMD;
   switch (command){
 <at>  <at>  -457,12 +453,14  <at>  <at> 
     buff[2]=ATA_SMART_STATUS;
     break;
   case AUTO_OFFLINE:
-    buff[2]=ATA_SMART_AUTO_OFFLINE;
-    buff[3]=select;   // YET NOTE - THIS IS A NON-DATA COMMAND!!
+    // NSECT is 241 for enable but no data transfer.  Use TASK ioctl.
+    buff[1]=ATA_SMART_AUTO_OFFLINE;
+    buff[2]=select;
     break;
   case AUTOSAVE:
-    buff[2]=ATA_SMART_AUTOSAVE;
-    buff[3]=select;   // YET NOTE - THIS IS A NON-DATA COMMAND!!
+    // NSECT is 248 for enable but no data transfer.  Use TASK ioctl.
+    buff[1]=ATA_SMART_AUTOSAVE;
+    buff[2]=select;
     break;
   case IMMEDIATE_OFFLINE:
     buff[2]=ATA_SMART_IMMEDIATE_OFFLINE;
 <at>  <at>  -517,7 +515,7  <at>  <at> 

   // There are two different types of ioctls().  The HDIO_DRIVE_TASK
   // one is this:
-  if (command==STATUS_CHECK){
+  if (command==AUTO_OFFLINE || command==AUTOSAVE || command==STATUS_CHECK){
     int retval;

     // NOT DOCUMENTED in /usr/src/linux/include/linux/hdreg.h. You




-- Package-specific info:
Ouput of /usr/share/bug/smartmontools:
# CONFIG_IDE_TASK_IOCTL is not set

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages smartmontools depends on:
ii  debianutils                  2.17.3      Miscellaneous utilities specific t
ii  libc6                        2.3.6.ds1-5 GNU C Library: Shared libraries
ii  lsb-base                     3.1-17      Linux Standard Base 3.1 init scrip

Versions of packages smartmontools recommends:
ii  mailx            1:8.1.2-0.20050715cvs-1 A simple mail user agent

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to