From: Eran Liberty <liberty@extricom.com>
To: "tiejun.chen" <tiejun.chen@windriver.com>
Cc: linuxppc-dev@ozlabs.org, linux-pci@vger.kernel.org
Subject: Re: Freescale P2020 CPU Freeze over PCIe abort signal
Date: Mon, 18 Oct 2010 13:44:42 +0200 [thread overview]
Message-ID: <4CBC332A.9090905@extricom.com> (raw)
In-Reply-To: <4CBC18D8.5060804@windriver.com>
tiejun.chen wrote:
> AFAIK we can set one bit on PEX_ERR_DISR to detect PCI Express completion
> time-out. If so one interrupt should be issued. But I'm not sure if this can fix
> your issue.
>
> Tiejun
>
As I understand the problem, this will not help me as the CPU itself is
on hold waiting for the assembly line to complete. It may give me enough
to spot the faulty situation and crash the system... but I am aiming for
an Enterprise grade product. Crash/oops is not something I want to put
into the system if I do not absolutely have to and I do have a hardware
watch-dog that will pull me out if I do.
So just for the fun of it I am going to follow up on this PEX_ERR_DISR,
but I do not see how it will help.
-- Liberty
next prev parent reply other threads:[~2010-10-18 11:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 12:30 Freescale P2020 / 85xx PCIe and Advance Error Reporting (AER) service problem Eran Liberty
2010-10-07 14:42 ` Kumar Gala
2010-10-10 10:02 ` Eran Liberty
2010-10-11 0:19 ` Benjamin Herrenschmidt
2010-10-11 10:21 ` Eran Liberty
2010-10-11 11:32 ` Benjamin Herrenschmidt
2010-10-17 19:24 ` Freescale P2020 CPU Freeze over PCIe abort signal Eran Liberty
2010-10-18 5:26 ` Bin Meng
2010-10-18 9:52 ` tiejun.chen
2010-10-18 11:44 ` Eran Liberty [this message]
2010-10-18 18:00 ` Eran Liberty
2010-10-19 16:53 ` Eran Liberty
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 17:41 siva kumar
2013-01-23 21:40 ` Scott Wood
2013-01-24 11:53 ` siva kumar
2013-01-25 1:03 ` Scott Wood
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=4CBC332A.9090905@extricom.com \
--to=liberty@extricom.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tiejun.chen@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).