From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: CaT <cat@zip.com.au>, linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: Re: libata + siI3112 + 2.6.5-rc3 hang
Date: Fri, 30 Apr 2004 02:08:32 +0200 [thread overview]
Message-ID: <200404300208.32830.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20040429234258.GA6145@zip.com.au>
Probably your drive needs mod15write quirk. please try this.
[PATCH] sata_sil.c: ST3200822AS needs MOD15WRITE quirk
linux-2.6.6-rc2-bk4-bzolnier/drivers/scsi/sata_sil.c | 1 +
1 files changed, 1 insertion(+)
diff -puN drivers/scsi/sata_sil.c~sata_sil_fix drivers/scsi/sata_sil.c
--- linux-2.6.6-rc2-bk4/drivers/scsi/sata_sil.c~sata_sil_fix 2004-04-30 02:00:37.387289528 +0200
+++ linux-2.6.6-rc2-bk4-bzolnier/drivers/scsi/sata_sil.c 2004-04-30 02:00:53.417852512 +0200
@@ -82,6 +82,7 @@ struct sil_drivelist {
{ "ST360015AS", SIL_QUIRK_MOD15WRITE },
{ "ST380023AS", SIL_QUIRK_MOD15WRITE },
{ "ST3120023AS", SIL_QUIRK_MOD15WRITE },
+ { "ST3200822AS", SIL_QUIRK_MOD15WRITE },
{ "ST340014ASL", SIL_QUIRK_MOD15WRITE },
{ "ST360014ASL", SIL_QUIRK_MOD15WRITE },
{ "ST380011ASL", SIL_QUIRK_MOD15WRITE },
_
On Friday 30 of April 2004 01:42, CaT wrote:
> Just acquired a Seagate 200GB SATA HD (yeah, baby, yeah ;) and hooked
> it up to my onboard Silicon Image iI 3112 SATA Raid controller of my
> Gigabyte nforce2 MB. Things work fine for the most part except when
> heavy IO is done on the drive. Then the system hangs totally with no
> console error msgs displayed. This also happens under Debian sarge's
> 2.4.25 aswell and has occured when I did a mke2fs -c on a partition
> and (twice) with hdparm -tT. The first time hdparm works fine and
> infact clocks the HD at 62MB/s (wowsers!), but the second time the
> system hangs.
It will go down with a quirk :( blame SiI for not providing chipset errata.
> scsi0? I thought it detected it at scsi1? This reminds me. The MB has
> the connector labeled as SATA1 but on bootup it's detected as the primary
> SATA drive.
libata has zero knowledge about legacy ordering and it's GOOD thing.
Cheers,
Bartlomiej
next prev parent reply other threads:[~2004-04-30 0:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 23:42 CaT
2004-04-30 0:08 ` Bartlomiej Zolnierkiewicz [this message]
2004-04-30 0:39 ` CaT
2004-04-30 9:39 ` CaT
2004-04-30 16:00 ` Bartlomiej Zolnierkiewicz
2004-05-01 3:08 ` CaT
2004-05-01 5:21 ` Andrew Morton
2004-05-01 11:58 ` Prakash K. Cheemplavam
2004-05-01 15:15 ` Bartlomiej Zolnierkiewicz
2004-05-01 15:58 ` CaT
2004-05-01 3:53 Marcus Hartig
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=200404300208.32830.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=cat@zip.com.au \
--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®