From: Justin Cormack <justin@street-vision.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, benh@kernel.crashing.org
Subject: Re: Serial ATA (SATA) status report
Date: Sat, 28 Feb 2004 14:49:39 +0000 [thread overview]
Message-ID: <1077979779.12949.1414.camel@lotte.street-vision.com> (raw)
In-Reply-To: <403D5B3D.6060804@pobox.com>
On Thu, 2004-02-26 at 02:34, Jeff Garzik wrote:
> Silicon Image 3112/3114
> -----------------------
> Summary: No TCQ. Looks like a PATA controller, but with full SATA
> control including hotplug and PM.
>
> libata driver status: Alpha.
>
> drivers/ide driver status: Production, but see issue #4.
>
> Issue #4: Need to have the most recent fixes posted to lkml, for stable
> operation and full performance (where possible).
Having had problems with SiI 3112A under the standard IDE drivers
http://marc.theaimsgroup.com/?l=linux-kernel&m=107539618032329&w=2
I thought I would test my set of disks with some bad sectors that oops
or hang the standard driver. I also tested them under high load (which
also causes problems with the legacy drivers which can drop to PIO mode
or just hang).
libata (2.4.25-libata3) is much more stable, managing 22 hours without
problems, however has just hung with
ata3: DMA timeout, stat 0x1
as the last log message (nothing before), box completely unresponsive.
Will recompile with magic sysrq and with DPRINTK and VPRINTK defined. It
wasnt actually accessing a part of the disk with bad sectors at the
point, just under high load and accessing 3 disks. What is the best way
of debugging this?
SCSI subsystem driver Revision: 1.00
libata version 1.01 loaded.
sata_sil version 0.53
ata1: SATA max UDMA/133 cmd 0xF8816080 ctl 0xF881608A bmdma 0xF8816000
irq 26
ata2: SATA max UDMA/133 cmd 0xF88160C0 ctl 0xF88160CA bmdma 0xF8816008
irq 26
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c49 86:3a01 87:4003
88:207f
ata1: dev 0 ATA, max UDMA/133, 240121728 sectors
ata1: dev 0 configured for UDMA/133
ata2: no device found (phy stat 00000000)
ata2: thread exiting
ata3: SATA max UDMA/133 cmd 0xF8818480 ctl 0xF881848A bmdma 0xF8818400
irq 27
ata4: SATA max UDMA/133 cmd 0xF88184C0 ctl 0xF88184CA bmdma 0xF8818408
irq 27
ata3: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003
88:203f
ata3: dev 0 ATA, max UDMA/100, 488397168 sectors (lba48)
ata3: dev 0 configured for UDMA/100
ata4: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003
88:203f
ata4: dev 0 ATA, max UDMA/100, 488397168 sectors (lba48)
ata4: dev 0 configured for UDMA/100
scsi0 : sata_sil
scsi1 : sata_sil
scsi2 : sata_sil
scsi3 : sata_sil
Vendor: ATA Model: Maxtor 6Y120M0 Rev: 1.01
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2500JD-00F Rev: 1.01
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2500JD-00F Rev: 1.01
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
sda: unknown partition table
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: unknown partition table
SCSI device sdc: 488397168 512-byte hdwr sectors (250059 MB)
sdc: unknown partition table
next prev parent reply other threads:[~2004-02-28 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 2:34 Jeff Garzik
2004-02-26 2:54 ` Mike Fedyk
2004-02-26 3:09 ` Jeff Garzik
2004-02-26 9:13 ` Mark Watts
2004-02-26 13:19 ` Andre Tomt
2004-02-26 14:23 ` Mark Watts
2004-02-26 15:33 ` Terje Kvernes
2004-02-26 15:55 ` Mark Watts
2004-02-26 20:11 ` Terje Kvernes
2004-02-27 18:56 ` Mark
2004-02-26 16:00 ` Jeff Garzik
2004-02-28 14:49 ` Justin Cormack [this message]
2004-03-01 8:05 ` Michael Knigge
2004-02-26 6:28 Kyle Wong
2004-02-26 19:08 Adam Radford
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=1077979779.12949.1414.camel@lotte.street-vision.com \
--to=justin@street-vision.com \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®