From: Jeff Garzik <jgarzik@pobox.com>
To: sander@humilis.net
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
lkml@rtr.ca
Subject: Re: Some sata_mv error messages
Date: Mon, 20 Mar 2006 20:02:06 -0500 [thread overview]
Message-ID: <441F508E.1030008@pobox.com> (raw)
In-Reply-To: <20060320133318.GB32762@favonius>
Sander wrote:
> Hi all,
>
> While sata_mv in 2.6.16-rc6-mm2 seems stable (yah!) compared to
> 2.6.16-rc6 (no crashes, no data corruption), I still get these messages:
>
> [ 3962.139906] ata5: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> [ 3962.139959] ata5: status=0xd0 { Busy }
>
> [ 6105.948045] ata6: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> [ 6105.948097] ata6: status=0xd0 { Busy }
>
> [ 7981.164936] ata5: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> [ 7981.164991] ata5: status=0xd0 { Busy }
>
> [ 8273.951019] ata7: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> [ 8273.951072] ata7: status=0xd0 { Busy }
>
> [ 9903.032350] ata8: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> [ 9903.032402] ata8: status=0xd0 { Busy }
>
>
> I'm not entirely sure this is only happens on sata_mv (Marvell
> MV88SX6081) as out of eight disks only one is connected to the onboard
> sata_nv (nVidia) and the error doesn't happen very often. But I'll keep
> an eye on it.
>
> Are these messages somehow dangerous or otherwise indicating a
> potentional serious problem? A google search came up with a few links,
> but none of them helped me understand the messages.
Without answering your specific question, just remember that sata_mv is
considerly "highly experimental" right now, and still needs some
workarounds for hardware errata.
For now, the goal is a system that doesn't crash and doesn't corrupt
data. If its occasionally slow or spits out a few errors, but otherwise
still works, that's pretty darned good :)
Jeff
next prev parent reply other threads:[~2006-03-21 1:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060318044056.350a2931.akpm@osdl.org>
2006-03-18 15:10 ` sata_mv success on 2.6.16-rc6-mm2 (was: Re: 2.6.16-rc6-mm2) Sander
2006-03-18 19:57 ` Andrew Morton
2006-03-20 13:33 ` Some sata_mv error messages " Sander
2006-03-21 1:02 ` Jeff Garzik [this message]
2006-03-21 2:25 ` Some sata_mv error messages Dave Jones
2006-03-21 2:35 ` Jeff Garzik
2006-03-21 16:06 ` Peter Jones
2006-03-21 4:48 ` Mark Lord
2006-03-21 7:28 ` Sander
2006-03-21 19:33 ` Denis Leroy
2006-03-21 19:37 ` Jeff Garzik
2006-03-21 19:42 ` Mark Lord
2006-03-21 7:26 ` Sander
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=441F508E.1030008@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=sander@humilis.net \
/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).