From: Ethan Chen <thanatoz@ucla.edu>
To: linux-kernel@vger.kernel.org
Cc: thanatoz@ucla.edu
Subject: SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14
Date: Mon, 28 Nov 2005 20:04:33 -0800 [thread overview]
Message-ID: <438BD351.60902@ucla.edu> (raw)
I've got a dual Opteron 242 machine here with 2x Seagate ST3200822AS
SATA drives attached to a Silicon Image SI3114 controller, and after
upgrading to 2.6.14 from 2.6.13, it seems the SIL_QUIRK_MOD15WRITE
workaround for the sata_sil driver isn't being applied anymore. This
caused me trouble in the past before my drive was added to the
blacklist, and this message that comes up when writing (~4GBfiles to
test) files, right before the computer locks up, is the same as before:
kernel: ata1: command 0x35 timeout, stat 0xd8 host_stat 0x61
In the dmesg, the 'Applying Seagate errata fix' message doesn't appear
anymore as well.
Finally, without the fix, write speeds are much higher as well, before
it locks up.
dmesg snippet from 2.6.13.4
kernel: SCSI subsystem initialized
kernel: ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 17 (level, low) -> IRQ 16
kernel: ata1: SATA max UDMA/100 cmd 0xFFFFC20000004C80 ctl
0xFFFFC20000004C8A bmdma 0xFFFFC20000004C00 irq 16
kernel: ata2: SATA max UDMA/100 cmd 0xFFFFC20000004CC0 ctl
0xFFFFC20000004CCA bmdma 0xFFFFC20000004C08 irq 16
kernel: ata3: SATA max UDMA/100 cmd 0xFFFFC20000004E80 ctl
0xFFFFC20000004E8A bmdma 0xFFFFC20000004E00 irq 16
kernel: ata4: SATA max UDMA/100 cmd 0xFFFFC20000004EC0 ctl
0xFFFFC20000004ECA bmdma 0xFFFFC20000004E08 irq 16
kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
kernel: ata1: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
kernel: ata1(0): applying Seagate errata fix
kernel: ata1: dev 0 configured for UDMA/100
kernel: scsi0 : sata_sil
kernel: ata2: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
kernel: ata2(0): applying Seagate errata fix
kernel: ata2: dev 0 configured for UDMA/100
kernel: scsi1 : sata_sil
kernel: ata3: dev 0 ATA, max UDMA/133, 586114704 sectors: lba48
kernel: ata3: dev 0 configured for UDMA/100
kernel: scsi2 : sata_sil
kernel: ata4: no device found (phy stat 00000000)
kernel: scsi3 : sata_sil
dmesg snippet from 2.6.14.2
kernel: SCSI subsystem initialized
kernel: ACPI: PCI Interrupt 0000:03:05.0[A] -> GSI 17 (level, low) -> IRQ 16
kernel: ata1: SATA max UDMA/100 cmd 0xFFFFC20000004C80 ctl
0xFFFFC20000004C8A bmdma 0xFFFFC20000004C00 irq 16
kernel: ata2: SATA max UDMA/100 cmd 0xFFFFC20000004CC0 ctl
0xFFFFC20000004CCA bmdma 0xFFFFC20000004C08 irq 16
kernel: ata3: SATA max UDMA/100 cmd 0xFFFFC20000004E80 ctl
0xFFFFC20000004E8A bmdma 0xFFFFC20000004E00 irq 16
kernel: ata4: SATA max UDMA/100 cmd 0xFFFFC20000004EC0 ctl
0xFFFFC20000004ECA bmdma 0xFFFFC20000004E08 irq 16
kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
kernel: ata1: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
kernel: ata1: dev 0 configured for UDMA/100
kernel: scsi0 : sata_sil
kernel: ata2: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
kernel: ata2: dev 0 configured for UDMA/100
kernel: scsi1 : sata_sil
kernel: ata3: dev 0 ATA, max UDMA/133, 586114704 sectors: lba48
kernel: ata3: dev 0 configured for UDMA/100
kernel: scsi2 : sata_sil
kernel: ata4: no device found (phy stat 00000000)
kernel: scsi3 : sata_sil
Thanks,
Ethan Chen
next reply other threads:[~2005-11-29 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:04 Ethan Chen [this message]
2005-11-30 4:16 ` SIL_QUIRK_MOD15WRITE workaround problem on 2.6.14 Tejun Heo
2005-11-30 4:42 ` Jeff Garzik
2005-11-30 5:37 ` Tejun Heo
2005-12-02 2:01 ` Jeff Garzik
2005-12-04 16:44 ` Tejun Heo
2005-12-05 18:41 ` Jeff Garzik
2005-11-30 4:48 ` Ethan Chen
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=438BD351.60902@ucla.edu \
--to=thanatoz@ucla.edu \
--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