linux-kernel - Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ACC076F.7020000@rtr.ca>
Date:	Tue, 06 Oct 2009 23:13:51 -0400
From:	Mark Lord <liml@....ca>
To:	Bernie Innocenti <bernie@...ewiz.org>
Cc:	Harri Olin <harri.olin@...il.com>, linux-ide@...r.kernel.org,
	lkml <linux-kernel@...r.kernel.org>, sysadmin <sysadmin@....org>
Subject: Re: sata_mv 0000:03:06.0: PCI ERROR; PCI IRQ cause=0x30000040

Bernie Innocenti wrote:
> El Tue, 06-10-2009 a las 20:06 -0400, Bernie Innocenti escribió:
>>> The early revs of these chips did have a number of errata specific to PCI-X.
>> I checked the revision (09) against the sata_mv source and I couldn't
>> spot anything relevant to us.
> 
> NEWSFLASH: today we replaced the 4x500GB Seagate drives with 4x1.5TB
> drives and reconstruction of the array has been running for 2h without a
> glitch.
> 
> One interesting difference is that the 500GB drives were being
> configured in 1.5Gbps SATA mode.  Another notable difference is the
> sequential read speed: ~70MB/s vs ~130MB/s with the 1.5TB model.
> 
> Could the PCI bus errors be a red herring?
..

Dunno.  Rev.9 == "C0" in Marvell terminology,
and that's the latest/final rev for the 6081 chip,
with most of the PCI-X bugs fixed or worked around.
So not much to go on there.

The Bus error report was real, though.
But with 3.0gb/sec sata connections, the chip will be
using some different internal clocks and timings,
which could be enough to avoid triggering the PCI errors.

I guess.  Let's hope so, anyway.

Cheers


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/