Problem with eSATA Port Multiplier

10-01-2010, 12:16 AM

Hi,

I've got a no-name PMP that I want to connect to the eSata port on
my mobo.

Attached are the output from "lspci -vvv" (It's a SiL 3132 chip and
the sata_sil24 driver is loaded) and /var/log/syslog.

I'm running a stock kernel:
$ uname -r
2.6.32-5-amd64

The actual h/w is "different" in that you "push" the hdd into the
enclosure and it's held in via a leaf spring. Thus, I wonder if the
PMP isn't firmly connecting with the hdd.

(Yes, I've Googled, but to no avail.)

TIA,
Ron

--
Seek truth from facts.
lspci -vvvs 02:00.0
02:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)
Subsystem: Silicon Image, Inc. Device 7132
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 4 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fdaff000 (64-bit, non-prefetchable) [size=128]
Region 2: Memory at fdaf8000 (64-bit, non-prefetchable) [size=16K]
Region 4: I/O ports at df00 [size=128]
[virtual] Expansion ROM at fdf00000 [disabled] [size=512K]
Capabilities: [54] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [5c] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 1024 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Latency L0 unlimited, L1 unlimited
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn-
Kernel driver in use: sata_sil24

Sep 30 18:02:50 haggis kernel: [14588.429745] ata1: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen
Sep 30 18:02:50 haggis kernel: [14588.429757] ata1: irq_stat 0x00b40090, PHY RDY changed
Sep 30 18:02:50 haggis kernel: [14588.429778] ata1: hard resetting link
Sep 30 18:02:53 haggis kernel: [14590.628082] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
Sep 30 18:02:53 haggis kernel: [14590.628426] ata1.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
Sep 30 18:02:53 haggis kernel: [14590.628882] ata1.00: hard resetting link
Sep 30 18:02:53 haggis kernel: [14591.044580] ata1.00: link resume succeeded after 1 retries
Sep 30 18:02:53 haggis kernel: [14591.152866] ata1.00: SATA link down (SStatus 0 SControl 310)
Sep 30 18:02:53 haggis kernel: [14591.152931] ata1.01: hard resetting link
Sep 30 18:02:53 haggis kernel: [14591.472537] ata1.01: SATA link down (SStatus 0 SControl 320)
Sep 30 18:02:53 haggis kernel: [14591.472636] ata1.02: hard resetting link
Sep 30 18:02:54 haggis kernel: [14591.793040] ata1.02: SATA link down (SStatus 0 SControl 320)
Sep 30 18:02:54 haggis kernel: [14591.793138] ata1.03: hard resetting link
Sep 30 18:02:54 haggis kernel: [14592.112492] ata1.03: SATA link down (SStatus 0 SControl 320)
Sep 30 18:02:54 haggis kernel: [14592.112598] ata1.04: hard resetting link
Sep 30 18:02:54 haggis kernel: [14592.432514] ata1.04: SATA link down (SStatus 0 SControl 320)
Sep 30 18:02:54 haggis kernel: [14592.432612] ata1.05: hard resetting link
Sep 30 18:02:55 haggis kernel: [14592.752941] ata1.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
Sep 30 18:02:55 haggis kernel: [14592.753139] ata1: EH complete

10-01-2010, 03:13 AM

Ron Johnson put forth on 9/30/2010 7:16 PM:
> Hi,
>
> I've got a no-name PMP that I want to connect to the eSata port on my mobo.
>
> Attached are the output from "lspci -vvv" (It's a SiL 3132 chip and the
> sata_sil24 driver is loaded) and /var/log/syslog.
>
> I'm running a stock kernel:
> $ uname -r
> 2.6.32-5-amd64
>
> The actual h/w is "different" in that you "push" the hdd into the
> enclosure and it's held in via a leaf spring. Thus, I wonder if the PMP
> isn't firmly connecting with the hdd.
>
> (Yes, I've Googled, but to no avail.)

Hay Ron,

Can you post dmesg output please. Also, have you confirmed all cables
are firmly engaged? Have you tried more than one eSATA cable?

Can you please post every bit of information you can find WRT the PMP
device and the drive enclosure? Are they on in the same? If you have
pictures of the devices that would be very helpful, so I can get an idea
of what plugs into what, and where, and how.

--
Stan

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CA551CB.4000008@hardwarefreak.com">http://lists.debian.org/4CA551CB.4000008@hardwarefreak.com

10-01-2010, 10:28 PM

On 09/30/2010 10:13 PM, Stan Hoeppner wrote:

Ron Johnson put forth on 9/30/2010 7:16 PM:

Hi,

I've got a no-name PMP that I want to connect to the eSata port on my mobo.

Attached are the output from "lspci -vvv" (It's a SiL 3132 chip and the
sata_sil24 driver is loaded) and /var/log/syslog.

I'm running a stock kernel:
$ uname -r
2.6.32-5-amd64

The actual h/w is "different" in that you "push" the hdd into the
enclosure and it's held in via a leaf spring. Thus, I wonder if the PMP
isn't firmly connecting with the hdd.

(Yes, I've Googled, but to no avail.)

Hay Ron,

Can you post dmesg output please.

[78511.900050] ata1.15: SATA link down (SStatus 0 SControl 10)
[78514.900060] ata1.15: qc timeout (cmd 0xe4)
[78514.900099] ata1.15: failed to read PMP GSCR[0] (Emask=0x5)
[78514.900113] ata1.15: PMP revalidation failed (errno=-5)
[78514.900118] ata1.15: failed to recover PMP after 5 tries, giving up
[78514.900124] ata1.15: Port Multiplier detaching
[78514.900163] ata1.00: disabled
[78516.900040] ata1: hard resetting link
[78518.981510] ata1: SATA link down (SStatus 0 SControl 0)
[78518.981536] ata1: EH complete

Also, have you confirmed all cables
are firmly engaged?

Yes.

Have you tried more than one eSATA cable?

Only have one.

Can you please post every bit of information you can find WRT the PMP
device and the drive enclosure? Are they on in the same? If you have
pictures of the devices that would be very helpful, so I can get an idea
of what plugs into what, and where, and how.

http://members.cox.net/ron.l.johnson/PMP_innards.jpg
http://members.cox.net/ron.l.johnson/PMP_front.jpg
http://members.cox.net/ron.l.johnson/PMP_rear.jpg

--
Seek truth from facts.

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CA660A0.9010704@cox.net">http://lists.debian.org/4CA660A0.9010704@cox.net

10-02-2010, 07:08 AM

Ron Johnson put forth on 10/1/2010 5:28 PM:
> On 09/30/2010 10:13 PM, Stan Hoeppner wrote:

>> Have you tried more than one eSATA cable?
>
> Only have one.

Pick up a new one from a retailer that'll give refunds on returns no (or
few) questions asked. If the new cable doesn't fix the problem get your
money back.

>> Can you please post every bit of information you can find WRT the PMP
>> device and the drive enclosure? Are they on in the same? If you have
>> pictures of the devices that would be very helpful, so I can get an idea
>> of what plugs into what, and where, and how.
>>
>
> http://members.cox.net/ron.l.johnson/PMP_innards.jpg
> http://members.cox.net/ron.l.johnson/PMP_front.jpg
> http://members.cox.net/ron.l.johnson/PMP_rear.jpg

Ok, so the 4 drive SATA JBOD box has a small cheap hotswap backplane
containing the port multiplier chip. If the problem isn't the cable,
it's likely the backplane itself. I've read many horror stories on the
Linux-RAID and XFS lists about cheap backplanes. Direct connecting the
drives to the controller fixes the problem in over 90% of the cases I've
seen. And it's not just "cheap" backplanes that suffer these problems.
I've read cases of reputable whitebox backplanes (SuperMicro for
example) having problems. And it's almost always "active" backplanes
that fail--those with with a PMP or I2C chip, or both. Passive
backplanes rarely causes problems, and if they do, they're defective out
of the box. Active backplanes can die over time. Cross your fingers
and hope it's the cable.

I forgot to ask earlier: is this JBOD enclosure a recent addition, or
was it working fine for eons and all of a sudden crapped out?

--
Stan

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CA6DA6B.9070008@hardwarefreak.com">http://lists.debian.org/4CA6DA6B.9070008@hardwarefreak.com

Sat Oct 2 09:30:02 2010
Return-path: <gentoo-dev+bounces-42826-tom=linux-archive.org@lists.gentoo.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Sat, 02 Oct 2010 09:19:46 +0300
Received: from pigeon.gentoo.org ([208.92.234.80]:57553 helo=lists.gentoo.org)
by s2.java-tips.org with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <gentoo-dev+bounces-42826-tom=linux-archive.org@lists.gentoo.org>)
id 1P1vRi-0005FC-C7
for tom@linux-archive.org; Sat, 02 Oct 2010 09:19:46 +0300
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 5FA69E0832;
Sat, 2 Oct 2010 07:12:45 +0000 (UTC)
X-Original-To: gentoo-dev@lists.gentoo.org
Delivered-To: gentoo-dev@lists.gentoo.org
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id A736CE07A1
for <gentoo-dev@lists.gentoo.org>; Sat, 2 Oct 2010 07:10:58 +0000 (UTC)
Received: from [192.168.1.101] (unknown [78.110.211.180])
(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
(No client certificate requested)
by smtp.gentoo.org (Postfix) with ESMTPSA id F09FC1B407A
for <gentoo-dev@lists.gentoo.org>; Sat, 2 Oct 2010 07:10:57 +0000 (UTC)
Message-ID: <4CA6DAFE.5000205@gentoo.org>
Date: Sat, 02 Oct 2010 09:10:54 +0200
From: =?windows-1252?Q?=22Miroslav_=8Aulc_=28fordfrog=29=22?=
<fordfrog@gentoo.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100927 Lightning/1.0b3pre Thunderbird/3.1.4
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] issue with gentoo-x86 cvs repo
References: <4CA688AE.3090506@gentoo.org> <robbat2-20101002T013323-776201821Z@orbis-terrarum.net>
In-Reply-To: <robbat2-20101002T013323-776201821Z@orbis-terrarum.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Dne 2.10.2010 03:35, Robin H. Johnson napsal(a):
> On Sat, Oct 02, 2010 at 03:19:42AM +0200, "Miroslav ?ulc (fordfrog)" wrote:
>> hi,
>>
>> yesterday i was able to use the repo but now i get this error (for any
>> cvs command):
>>
>> $ cvs rm -f apgdiff-2.0.2.ebuild
>> Your account has expired; please contact your system administrator
>> Connection closed by 81.93.255.6
>> cvs [remove aborted]: end of file from server (consult above messages if
>> any)
>>
>> what does it exactly mean?
> It's fixed already.
> Some lovely lines from the old perl_ldap:
> ===
> my $expiry = convertEpoch(0,0,0,1,9,2010);
> ...
> shadowExpire => $expiry,
> ===
> Which is a date of 2010/10/02, that just rolled up a few hours ago.
> A constant value that was set >5 years ago come up :-).
>
> All LDAP and the script are fixed now.
>
Thanks :-)

10-02-2010, 10:36 AM

On 10/02/2010 02:08 AM, Stan Hoeppner wrote:

Ron Johnson put forth on 10/1/2010 5:28 PM:

On 09/30/2010 10:13 PM, Stan Hoeppner wrote:

Have you tried more than one eSATA cable?

Only have one.

Pick up a new one from a retailer that'll give refunds on returns no (or
few) questions asked. If the new cable doesn't fix the problem get your
money back.

OK.

Can you please post every bit of information you can find WRT the PMP
device and the drive enclosure? Are they on in the same? If you have
pictures of the devices that would be very helpful, so I can get an idea
of what plugs into what, and where, and how.

http://members.cox.net/ron.l.johnson/PMP_innards.jpg
http://members.cox.net/ron.l.johnson/PMP_front.jpg
http://members.cox.net/ron.l.johnson/PMP_rear.jpg

Ok, so the 4 drive SATA JBOD box has a small cheap hotswap backplane
containing the port multiplier chip. If the problem isn't the cable,
it's likely the backplane itself. I've read many horror stories on the
Linux-RAID and XFS lists about cheap backplanes. Direct connecting the
drives to the controller fixes the problem in over 90% of the cases I've
seen.

But how would I do that?

And it's not just "cheap" backplanes that suffer these problems.
I've read cases of reputable whitebox backplanes (SuperMicro for
example) having problems. And it's almost always "active" backplanes
that fail--those with with a PMP or I2C chip, or both. Passive
backplanes rarely causes problems, and if they do, they're defective out
of the box. Active backplanes can die over time. Cross your fingers
and hope it's the cable.

I forgot to ask earlier: is this JBOD enclosure a recent addition, or
was it working fine for eons and all of a sudden crapped out?

It never "worked". I'm only now stimulated to try and fix it.

--
Seek truth from facts.

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CA70B15.7060600@cox.net">http://lists.debian.org/4CA70B15.7060600@cox.net

10-03-2010, 02:04 AM

Ron Johnson put forth on 10/2/2010 5:36 AM:
> On 10/02/2010 02:08 AM, Stan Hoeppner wrote:
>> Ron Johnson put forth on 10/1/2010 5:28 PM:

>>> http://members.cox.net/ron.l.johnson/PMP_innards.jpg
>>> http://members.cox.net/ron.l.johnson/PMP_front.jpg
>>> http://members.cox.net/ron.l.johnson/PMP_rear.jpg
>>
>> Ok, so the 4 drive SATA JBOD box has a small cheap hotswap backplane
>> containing the port multiplier chip. If the problem isn't the cable,
>> it's likely the backplane itself. I've read many horror stories on the
>> Linux-RAID and XFS lists about cheap backplanes. Direct connecting the
>> drives to the controller fixes the problem in over 90% of the cases I've
>> seen.
>
> But how would I do that?

In you case you'd have to test each drive individually, as you
apparently don't have 4 free SATA ports inside your host machine. Given
the errors you receive, the drives aren't the problem. It's the cable
or the backplane.

>> And it's not just "cheap" backplanes that suffer these problems.
>> I've read cases of reputable whitebox backplanes (SuperMicro for
>> example) having problems. And it's almost always "active" backplanes
>> that fail--those with with a PMP or I2C chip, or both. Passive
>> backplanes rarely causes problems, and if they do, they're defective out
>> of the box. Active backplanes can die over time. Cross your fingers
>> and hope it's the cable.
>>
>> I forgot to ask earlier: is this JBOD enclosure a recent addition, or
>> was it working fine for eons and all of a sudden crapped out?
>>
>
> It never "worked". I'm only now stimulated to try and fix it.

If the cable doesn't fix it, the way to do so is to order a replacement
backplane from the manufacturer. I'm assuming the unit you have it out
of warranty. If not sent it back for repair.

They will probably quote you a price on a replacement backplane so high
that it would be better to buy another complete unit, which is exactly
why they'll shoot you an unrealistically high price. Then again, they
may simply say they don't sell replacement backplanes/parts of any kind.

If the cable isn't the problem but the backplane is, and if for any
reason you don't want to attempt replacing the backplane, I'd recommend
swapping the drives into a similar product:

http://www.newegg.com/Product/Product.aspx?Item=N82E16817998053

I've never used this device, but it's the least expensive eSATA box
Newegg carries. It's big brother (more expensive) doesn't look any more
capable, although swapping a drive is easier with the more expensive unit.

--
Stan

--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4CA7E4BE.7090400@hardwarefreak.com">http://lists.debian.org/4CA7E4BE.7090400@hardwarefreak.com