linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: "Eric D. Mudama" <edmudama@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: HPA and failed opcode was: 0x37 ?
Date: Wed, 31 Jan 2007 09:29:35 +0100	[thread overview]
Message-ID: <45C0536F.5020005@imc-berlin.de> (raw)
In-Reply-To: <311601c90701301156nb135de6g996eaff8b2f95a6c@mail.gmail.com>

Eric,

> Maybe the FPGA is discarding the taskfile writes once the HOB bit is
> set?  It wouldn't affect the READ NATIVE MAX ADDRESS EXT command being
> issued since the only the command register matters for that, but it
> would affect SET MAX ADDRESS EXT working properly.
> 
> Without a device > 137GB to test with, and without errors on the
> device, you might not see any odd behavior in normal usage.
> 
> It's *really* unlikely the drive doesn't have a working taskfile.

I am sorry. But I don't understand what a "working taskfile" means.
I don't have CONFIG_IDE_TASK_IOCTL enabled if that means anything.

The FPGA does nothing except decoding adresseses from the ARM cpu,
controlling the A[2..0], CS[1..0], IOR, IOW lines of the HDD.

In linux all I do is setting up some hw_regs_t struct (with hw.io_ports[])
according to my memory map and call ide_register_hw() ...

So looks like I need to find out more about that taskfile stuff.

The reason I started the this thread is that after working with Hitatchi and
Toshiba HDDs in the same mannor we suddenly have problems with new Seagate
drives.

After the kernel reported problems when writing to the disk I used
smartctl to look at the attributes:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   253   006         0
  3 Spin_Up_Time            0x0003   096   096   000         0
  4 Start_Stop_Count        0x0032   100   100   020        21
  5 Reallocated_Sector_Ct   0x0033   100   100   036         0
  7 Seek_Error_Rate         0x000f   061   060   030   1368871
  9 Power_On_Hours          0x0032   100   100   000        76
 10 Spin_Retry_Count        0x0013   100   100   034         0
 12 Power_Cycle_Count       0x0032   100   100   020        27
187 Unknown_Attribute       0x0032   100   100   000         0
189 Unknown_Attribute       0x003a   100   100   000         0
190 Temperature_Celsius     0x0022   069   025   045 538705951
192 Power-Off_Retract_Count 0x0032   100   100   000        25
193 Load_Cycle_Count        0x0032   100   100   000       363
194 Temperature_Celsius     0x0022   031   075   000        31
195 Hardware_ECC_Recovered  0x001a   078   066   000  23105720
197 Current_Pending_Sector  0x0012   100   100   000         0
198 Offline_Uncorrectable   0x0010   100   100   000         0
199 UDMA_CRC_Error_Count    0x003e   200   200   000         0
200 Multi_Zone_Error_Rate   0x0000   100   253   000         0
202 TA_Increase_Count       0x0032   100   253   000         0

And I am kind of concerned about Seek_Error_Rate, Temperature_Celsius and
Hardware_ECC_Recovered ...

So now I wonder if all the Seagate drives we have are broken or if this
might be a problem with our hardware ...

Thanks a million!

Steven


  parent reply	other threads:[~2007-01-31  8:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 14:02 HPA and failed opcode was: 0x37 ? Steven Scholz
2007-01-30 14:07 ` Steven Scholz
2007-01-30 15:44   ` Eric D. Mudama
2007-01-30 15:50     ` Eric D. Mudama
2007-01-30 15:54       ` Steven Scholz
2007-01-30 15:53     ` Steven Scholz
2007-01-30 16:44 ` Alan
2007-01-30 16:46   ` Steven Scholz
2007-01-30 17:26     ` Alan
2007-01-30 17:19       ` Steven Scholz
2007-01-30 18:07         ` Alan
2007-01-30 18:04           ` Steven Scholz
2007-01-30 18:23             ` Eric D. Mudama
2007-01-30 18:32             ` Sergei Shtylyov
2007-01-30 19:56               ` Eric D. Mudama
2007-01-30 20:01                 ` Eric D. Mudama
2007-01-31  8:29                 ` Steven Scholz [this message]
2007-01-31 12:54                   ` Sergei Shtylyov
2007-01-31 13:08                     ` Steven Scholz
2007-01-31 13:12                       ` Sergei Shtylyov
2007-01-31 13:38                         ` Steven Scholz
2007-01-31  9:51               ` Steven Scholz
2007-01-31 12:50                 ` Sergei Shtylyov
2007-01-31 13:04                   ` Steven Scholz
2007-01-31 13:33                     ` Alan
2007-01-31 13:26                       ` Steven Scholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45C0536F.5020005@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=edmudama@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).