From: Onis <onion@virasto.com>
To: Mark Lord <liml@rtr.ca>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_mv dropping disks
Date: Sat, 20 May 2006 01:25:40 +0300 [thread overview]
Message-ID: <20060519222540.GA15276@virasto.com> (raw)
In-Reply-To: <446E3352.20405@rtr.ca>
Mark Lord wrote:
> >BUG: warning at drivers/scsi/sata_mv.c:1884/mv_channel_reset()
> ...
> >What does "PCI IRQ cause=0x28000020" mean?
>
> "MWrPerr: SErr# asserted upon a PErr# response to write data by the PCI
> master"
>
> In other words, a PCI bus parity error was detected.
> Noisy bus, or buggy hardware.
Yes, that was fixed by relaxing bus speed to 133->66MHz, ignore it. My bad.
> > ata4: translated ATA stat/err 0x50/01 to SCSI SK/ASC/ASCQ 0x3/13/00
> > ata4: status=0x50 { DriveReady SeekComplete }
> > ata4: error=0x01 { AddrMarkNotFound }
>
> That is wrong (bug). I *think* this may be fixed by the sata_mv
> patch series I just posted today. The response should be to reset
> the bus (well, at least that's what it does now) and then retry
> the operation, not fail it immediately.
I think this was related to bus speed also. Haven't seen this error before.
> >Also I'm getting a lots of these on all ports on boot. smartctl also
> >triggers
> >these:
> >----
> >ata3: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> >ata3: status=0xd0 { Busy }
> >ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> >ata1: status=0xd0 { Busy }
> >...
>
> That's due to a Marvell chip bug. A workaround for that got posted in
> my patch series today.
Thanks a lot for the patch Mark! I grabbed immediately and patched against
2.6.17-rc4. Is it okay?
Now I'm now running rebuild with 6081 controller. Everything seems great. No
ata busy warnings or anything.
> Cheers
Cheers!
prev parent reply other threads:[~2006-05-19 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 21:31 sata_mv dropping disks Onis
2006-05-19 21:06 ` Mark Lord
2006-05-19 22:25 ` Onis [this message]
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=20060519222540.GA15276@virasto.com \
--to=onion@virasto.com \
--cc=liml@rtr.ca \
--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).