From: Jeff Garzik <jeff@garzik.org>
To: Nicolas Jungers <nicolas@jungers.net>
Cc: linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: possible esata regression in 2.6.35
Date: Sun, 22 Aug 2010 15:54:51 -0400 [thread overview]
Message-ID: <4C71808B.7070704@garzik.org> (raw)
In-Reply-To: <4C702070.5020809@jungers.net>
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.
Jeff
next prev parent reply other threads:[~2010-08-22 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 18:52 possible esata regression in 2.6.35 Nicolas Jungers
2010-08-21 19:13 ` Mark Lord
2010-08-21 19:59 ` Nicolas Jungers
2010-08-22 19:54 ` Jeff Garzik [this message]
2010-08-22 19:57 ` Jeff Garzik
2010-08-27 8:19 ` Gwendal Grignou
[not found] ` <AANLkTi=deJbndavPJmFzEoy6kZQX8LdoAdE+QQN5if0=@mail.gmail.com>
2010-08-27 22:56 ` Gwendal Grignou
2010-08-29 0:40 ` Gwendal Grignou
2010-08-25 19:00 ` Maciej Rutecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C71808B.7070704@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas@jungers.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox