linux-kernel - Re: port multiplier problem

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4B6A3D24.8020802@kernel.org>
Date:	Thu, 04 Feb 2010 12:21:08 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Grant Grundler <grundler@...gle.com>
CC:	Chandra Shekhar Sah <edu4madh@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: port multiplier problem

Hello,

On 02/03/2010 01:44 AM, Grant Grundler wrote:
> On Tue, Feb 2, 2010 at 6:59 AM, Chandra Shekhar Sah <edu4madh@...il.com> wrote:
>> Hi Tejun,
>>
>> I have attached full dmesg output, while 9 disks are connected to PMP, and
>> no disk to "direct sata".
> 
> Linux version 2.6.31.12-174.2.3.fc12.i686.PAE
> (mockbuild@...-04.phx2.fedoraproject.org)
> ...
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> ata3.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
> ata3.00: hard resetting link
> ata3.00: SATA link down (SStatus 0 SControl 10)
> ata3.01: hard resetting link
> ata3.01: SATA link down (SStatus 0 SControl 320)
> ata3.02: hard resetting link
> ata3.02: SATA link down (SStatus 0 SControl 320)
> ata3.03: hard resetting link
> ata3.03: SATA link down (SStatus 0 SControl 320)
> ata3.04: hard resetting link
> ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.05: hard resetting link
> ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
> 
> Sil3726 has only 5 ports. 6th port is an enclosure management port.
> Wasn't there a patch submitted to ignore the enclosure mgt port?

Eh... I don't think it got included.

> I doubt this is the problem Chandra is seeing but it could be related.

Doesn't seem to be.  IDENTIFY failures are coming from normal ports.

Thanks.

-- 
tejun
--
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/