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!
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
