From: Anthony Foiani <tkil@scrye•com>
To: Xie Shaohui-B21989 <B21989@freescale•com>
Cc: Wood Scott-B07421 <B07421@freescale•com>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: SATA hang on 8315E triggered by heavy flash write?
Date: Thu, 23 May 2013 09:10:57 -0600 [thread overview]
Message-ID: <g4ndt3f5q.fsf@dworkin.scrye.com> (raw)
In-Reply-To: <ED492CCEAF882048BC2237DE806547C90B1E0FFA@039-SN2MPN1-013.039d.mgd.msft.net> (Xie Shaohui-B's message of "Thu\, 23 May 2013 06\:04\:15 +0000")
Shaohui --
Xie Shaohui-B21989 <B21989@freescale•com> writes:
> Thanks for the confirmation.
You're very welcome.
> So it seems the NOR write break the signal Integrity of SATA.
> I don't have schematic and board right now, could you please measure
> signals related to NOR write to see if anything abnormal? Is the board
> use FPGA or CPLD to control signal?
I'll have to pass these questions on to my hardware vendor; I'm not
equipped to do this level of hardware debugging (neither hardware nor
knowledge!).
> If stop NOR write, could the SATA recover and work?
Earlier in my development, I was seeing this error and it would
recover:
ata2: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen
ata2: PHY RDY changed
ata2: hard resetting link
ata2: Signature Update detected @ 0 msecs
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/133
ata2: EH complete
At the current time, however, it seems that it does not recover.
I don't know whether this is due to the speed limiting code, or if
it's because we are doing more disk accesses (when the actual product
is up and running).
I can re-do the tests with the speed limit disabled, but I won't be
able to get to that for a few hours yet. You can read about the speed
limit issues in this thread:
http://article.gmane.org/gmane.linux.ports.ppc.embedded/50652
And my final patch (yes, a year later):
http://article.gmane.org/gmane.linux.ports.ppc.embedded/58969
Please don't laugh too hard when you read it. :)
Thanks again for your help. I'll try to get the results of testing
w/o speed limit to you within a day or two.
Best regards,
Anthony Foiani
next prev parent reply other threads:[~2013-05-23 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 8:12 SATA hang on 8315E triggered by heavy flash write? Anthony Foiani
2013-05-21 21:44 ` Scott Wood
2013-05-22 4:16 ` Anthony Foiani
2013-05-22 6:15 ` Xie Shaohui-B21989
2013-05-23 5:52 ` Anthony Foiani
2013-05-23 6:04 ` Xie Shaohui-B21989
2013-05-23 15:10 ` Anthony Foiani [this message]
2013-05-23 15:49 ` Anthony Foiani
2013-05-27 7:50 ` Xie Shaohui-B21989
2013-05-28 0:29 ` Anthony Foiani
2013-05-30 7:32 ` Xie Shaohui-B21989
2013-06-01 4:24 ` Anthony Foiani
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=g4ndt3f5q.fsf@dworkin.scrye.com \
--to=tkil@scrye$(echo .)com \
--cc=B07421@freescale$(echo .)com \
--cc=B21989@freescale$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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