From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: possible esata regression in 2.6.35 Date: Sun, 22 Aug 2010 15:57:09 -0400 Message-ID: <4C718115.8070103@garzik.org> References: <4C702070.5020809@jungers.net> <4C71808B.7070704@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-vw0-f46.google.com ([209.85.212.46]:45762 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752062Ab0HVT5O (ORCPT ); Sun, 22 Aug 2010 15:57:14 -0400 In-Reply-To: <4C71808B.7070704@garzik.org> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Nicolas Jungers Cc: linux-kernel@vger.kernel.org, Linux IDE mailing list On 08/22/2010 03:54 PM, Jeff Garzik wrote: > On 08/21/2010 02:52 PM, Nicolas Jungers wrote: >> My arm box doesn't succeed to use my esata port multiplier (addonics >> sil3726 based). It was working well with 2.6.34.1 and 2.6.34.4 but not >> with both 2.6.35.2 and 2.6.35.3. I haven't test other kernels. >> >> The kernels are from http://sheeva.with-linux.com/sheeva/ with for >> example the following config >> http://sheeva.with-linux.com/sheeva/2.6.35.3/sheeva-2.6.35.3.config >> >> The symptoms are in the console a loop on the esata links. Here is the >> start of it: >> >> ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen >> ata2: edma_err_cause=00000010 pp_flags=00000000, dev connect >> ata2: SError: { PHYRdyChg DevExch } >> ata2: hard resetting link >> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) >> ata2.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 > > Can you post or link to the entire dmesg? > > Notably, we need to see the probe messages to determine what SATA chip > you are using... From the edma_err_cause config I'd guess sata_mv, but > more info would be useful. Nevermind, I see the reply (it got auto-sorted into the wrong folder locally).