From: Jon K Hellan <hellan@acm.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: Re: sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE
Date: Thu, 23 Feb 2006 07:59:47 +0100 [thread overview]
Message-ID: <1140677987.11943.16.camel@localhost> (raw)
In-Reply-To: <43FD18F5.20002@gmail.com>
On Thu, 2006-02-23 at 11:07 +0900, Tejun Heo wrote:
> According to the errata information from Silicon Image, SiI3512 does not
> have m15w bug, neither does ST3200822AS. So, this must be something else
> and you're not an isolated case.
Glad to hear it.
In that case, you'd probably like to hear about the other disk as well.
Originally, I suspected the disk was about to fail, and bought another
one - a Samsung SP2504C. I never succeeded in copying the data off the
Seagate onto the Samsung. The farthest I got was about 2 gigs. The error
messages would be from sdb (the Samsung):
Feb 21 20:08:31 parus kernel: ata2: command 0x35 timeout, stat 0xd1 host_stat 0x61
Feb 21 20:08:31 parus kernel: ata2: translated ATA stat/err 0xd1/00 to
SCSI SK/ASC/ASCQ 0xb/47/00
Feb 21 20:08:31 parus kernel: ata2: status=0xd1 { Busy }
Feb 21 20:08:31 parus kernel: sd 1:0:0:0: SCSI error: return code =
0x8000002
Feb 21 20:08:31 parus kernel: sdb: Current: sense key: Aborted Command
Feb 21 20:08:31 parus kernel: Additional sense: Scsi parity error
Feb 21 20:08:31 parus kernel: end_request: I/O error, dev sdb, sector
15657695
Feb 21 20:08:31 parus kernel: Buffer I/O error on device sdb1, logical
block 1957204
Feb 21 20:08:31 parus kernel: lost page write due to I/O error on sdb1
Feb 21 20:08:31 parus kernel: ATA: abnormal status 0xD1 on port
0xF88020C7
I didn't bring this up originally, since it looked like the Seagate
problem was a known bug, while Google didn't turn up anything on
Samsung. After reading linux-ide through gmane, I've seen similar issues
about Samsung. You guys should get an archive which Google knows
about :-)
> So, it would be very nice if you can test fixes we'll be able to come up with.
Certainly.
Regards
Jon
next prev parent reply other threads:[~2006-02-23 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 18:03 sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE Jon Kåre Hellan
2006-02-23 2:07 ` Tejun Heo
2006-02-23 3:35 ` Jeff Garzik
2006-02-23 3:52 ` Tejun Heo
2006-02-23 3:58 ` Jeff Garzik
2006-02-23 6:59 ` Jon K Hellan [this message]
2006-02-23 7:19 ` Tejun Heo
2006-02-24 7:08 ` Jon K Hellan
2006-02-24 7:21 ` Tejun Heo
2006-02-24 7:26 ` Tejun Heo
2006-02-24 8:33 ` Jon Kåre Hellan
2006-02-24 18:07 ` Jon K Hellan
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=1140677987.11943.16.camel@localhost \
--to=hellan@acm.org \
--cc=Carlos.Pardo@siliconimage.com \
--cc=htejun@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).