From: Mark Lord <liml@rtr.ca>
To: Onis <onion@virasto.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_mv dropping disks
Date: Fri, 19 May 2006 17:06:26 -0400 [thread overview]
Message-ID: <446E3352.20405@rtr.ca> (raw)
In-Reply-To: <20060518213131.GA10777@virasto.com>
Onis wrote:
> Hello
>
> Got warnings while rebuilding md raid5 array. Controller is 88SX5081 with
> 8xMaxtor 300GB 7V300F0. I've ran badblock -w on all disks, smartctl doesn't
> report errors.
>
> ----
> BUG: warning at drivers/scsi/sata_mv.c:1884/mv_channel_reset()
>
> Call Trace: <IRQ> <ffffffff803a39ce>{mv_channel_reset+238}
> <ffffffff803a4277>{mv_stop_and_reset+55}
> <ffffffff803a45f7>{mv_interrupt+631}
> <ffffffff8024e9fc>{handle_IRQ_event+44}
> <ffffffff8024eae0>{__do_IRQ+176}
...
I'm not sure what the complaint is about there.
I see this on line 1884: mdelay(1);
But maybe the 2.6.17-rc4-mm1 version is different from
the 2.6.17-rc4-git2-libata1 that I have handy right now. (?)
> BUG: warning at drivers/scsi/sata_mv.c:1904/__msleep()
Similarly, on that line I see: mdelay(20);
Is there something different about mdelay() in -mm now?
..
> 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.
> 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.
..
> 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.
Cheers
next prev parent reply other threads:[~2006-05-19 21:06 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 [this message]
2006-05-19 22:25 ` Onis
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=446E3352.20405@rtr.ca \
--to=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=onion@virasto.com \
/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).