Skip to contentSkip to conversation

dma errors with sata_sil and Seagate disk

DISCUSSION John Lash 4 participants 9 messages Dec 1, 2004 – Dec 3, 2004

lore
Share & tools
lore

John Lash

author
#0 lore raw

I'm using the sata_sil driver on a Tyan 2885. It has onboard Silicon Image 3114 SATA interfaces. There's one disk connected now, a Seagate ST380013AS. I've been seeing persistent problems with errors (DriveStatusError) on the device. It seems to happen pretty quickly under a load (trying to copy a couple of GB of files to the disk).

I noticed that the sil_blacklist had quite a few Seagate entries and on searching the web, found that these were dma problems that looked pretty similar to mine. Since then I've added this model number to the sil_blacklist table, rebuilt and rebooted. Now it's stable (just copied 20 GB of data to it). Is this another problematic drive? Or am I masking the original problem?

I see the problem consistently on 2.6.8.1, 2.6.9, and 2.6.10-rc2-bk13. Also saw the problems when I tried this on an older AMD MP system with a SI 3112 PCI controller card.

I don't see any indication that Seagate has released any public firmware upgrades for this drive. Anybody have a suggestion?

--john

#1 lore raw
Quoted 2 lines · John Lash

I don't see any indication that Seagate has released any public firmware upgrades for this drive. Anybody have a suggestion?

Don't mix seagate drives and SI311x hardware is the best suggestion. Even if you activate the workaround for the problem you take a performance hit.

Please send Jeff Garzik a patch for the the change you made of course.

author
#2 lore raw
Quoted 11 lines · On Wed, 01 Dec 2004 23:41:22 +0000 Alan Cox <[email protected]> wrote:
Quoted 2 lines · John Lash

I don't see any indication that Seagate has released any public firmware upgrades for this drive. Anybody have a suggestion?

Don't mix seagate drives and SI311x hardware is the best suggestion. Even if you activate the workaround for the problem you take a performance hit.

Please send Jeff Garzik a patch for the the change you made of course.

Thanks Alan, that's pretty clear ;-) Yes, performance hit, big time, 9-10 MB/sec, load average through the roof on a big copy. Pretty much what I was expecting though. I'll look around work and see if there is anybody I can trade with. Odd that those two devices are so wildly incompatible.

I'll roll up a patch for the change in the morning.

--john

#3 lore raw
In reply to Alan Cox
Quoted 5 lines · Alan Cox
Quoted 2 lines · John Lash

I don't see any indication that Seagate has released any public firmware upgrades for this drive. Anybody have a suggestion?

Don't mix seagate drives and SI311x hardware is the best suggestion.

Is there some problem with Seagate drives in general? I'm using two ST3160827AS drives on an SI3114 controller, and haven't seen any glitches yet. That model is not in the blacklist, and performance is what I'd usually expect. Is it pure luck that has kept me away from problems?

Signature · 2 lines
Måns Rullgård
[email protected]
#4 lore raw
Quoted 5 lines · Måns Rullgård

Is there some problem with Seagate drives in general? I'm using two ST3160827AS drives on an SI3114 controller, and haven't seen any glitches yet. That model is not in the blacklist, and performance is what I'd usually expect. Is it pure luck that has kept me away from problems?

I've never been able to get a non NDA list of the affected drives. Got to love vendors some days

#5 lore raw
Quoted 9 lines · Alan Cox
Quoted 5 lines · Måns Rullgård

Is there some problem with Seagate drives in general? I'm using two ST3160827AS drives on an SI3114 controller, and haven't seen any glitches yet. That model is not in the blacklist, and performance is what I'd usually expect. Is it pure luck that has kept me away from problems?

I've never been able to get a non NDA list of the affected drives. Got to love vendors some days

Does this mean it is the drives which are faulty, not the controller? These drives are both new, so I suppose known problems might have been fixed. FWIW, they are reported by the kernel thusly:

  Vendor: ATA       Model: ST3160827AS       Rev: 3.03
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: ST3160827AS       Rev: 3.00
  Type:   Direct-Access                      ANSI SCSI revision: 05
Signature · 2 lines
Måns Rullgård
[email protected]
#6 lore raw
Quoted 3 lines · Måns Rullgård

Does this mean it is the drives which are faulty, not the controller? These drives are both new, so I suppose known problems might have been fixed. FWIW, they are reported by the kernel thusly:

The issue is that the SiI 311x controllers send out packets (called "FIS's" in SATA-land) that are not multiples of 512 bytes.

This is perfectly legal according to SATA spec, but early drive firmwares (notoriously Seagate in this case) were written with the assumption that the FIS's would be multiples of 512 bytes.

Jeff

author
#7 lore raw
In reply to Måns Rullgård
Quoted 4 lines · On Fri, 03 Dec 2004 02:14:27 +0100 Måns Rullgård <[email protected]> wrote:
Quoted 1 line · Alan Cox

On Iau, 2004-12-02 at 10:01, Måns Rullgård wrote:

Quoted 9 lines

Does this mean it is the drives which are faulty, not the controller? These drives are both new, so I suppose known problems might have been fixed. FWIW, they are reported by the kernel thusly:

  Vendor: ATA       Model: ST3160827AS       Rev: 3.03
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: ST3160827AS       Rev: 3.00
  Type:   Direct-Access                      ANSI SCSI revision: 05

I know that the disk that I'm using has been sitting on a shelf since about last June. It still seems to be a shipping model though. It's showing itself as model: ST380013AS, rev: 3.18.

It would be nice if the problem gets fixed someday. Be even nicer if there was a firmware update that could be applied to the older drives.....

--john

#8 lore raw
In reply to Alan Cox
Quoted 11 lines · Alan Cox
Quoted 5 lines · Måns Rullgård

Is there some problem with Seagate drives in general? I'm using two ST3160827AS drives on an SI3114 controller, and haven't seen any glitches yet. That model is not in the blacklist, and performance is what I'd usually expect. Is it pure luck that has kept me away from problems?

I've never been able to get a non NDA list of the affected drives. Got to love vendors some days

I seriously doubt a complete list exists, NDA or no. You'd have to poll each vendor.

I also suspect that a few of the more recent Seagate additions are simply masking a problem in the BIOS.

SiI 311x problems have a history of resolving themselves through BIOS updates and tweaks. Most recently a lockup was solved by tweaking a 'byte enable' setting in an nForce mobo BIOS.

Jeff