linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ravich <lravich@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: PCIE device errors after linux kernel upgrade
Date: Sun, 18 Aug 2013 04:30:56 -0700 (PDT)	[thread overview]
Message-ID: <1376825456181-75193.post@n7.nabble.com> (raw)
In-Reply-To: <CAErSpo6zGZkL7hWmBOVzd2=MWvY18v5xLO1qg7jVfSgqa8wHzw@mail.gmail.com>

Hi

>>Is this still a problem, or have you found a solution in the meantime? 
I did not found any solution yet
>>Where are the "PCIE ERR_CAP_STAT" and similar messages from? 
PCIE ERR_CAP_STAT is coming from:
drivers/edac/mpc85xx_edac.c

>>Can you post the complete logs somewhere, maybe in a bugzilla or similar? 
cant I post here??

Thanks for your time 



--
View this message in context: http://linuxppc.10917.n7.nabble.com/Re-PCIE-device-errors-after-linux-kernel-upgrade-tp74563p75193.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2013-08-18 11:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPWoNkJ3NKM-_g93LdRpjvdNFtLt-Pjpg4d4oEKC9CvkpzZ-Wg@mail.gmail.com>
     [not found] ` <CAPWoNkLQUbFG2vZ7wqoqqVNj4uxKz3Fa_vsSH=1_TDD=XC1f2A@mail.gmail.com>
2013-08-05 15:38   ` PCIE device errors after linux kernel upgrade Bjorn Helgaas
2013-08-06  6:32     ` Leon Ravich
2013-08-07  5:41       ` Leon Ravich
2013-08-16 22:05         ` Bjorn Helgaas
2013-08-18 11:30           ` ravich [this message]
2013-10-11 22:01           ` Bjorn Helgaas
2013-10-29 15:07             ` ravich
2014-01-08  8:24               ` ravich
2014-01-08 21:07                 ` Scott Wood
2013-11-20  7:53             ` ravich
2013-08-06  7:07     ` Johannes Thumshirn
2013-08-06  7:26       ` Leon Ravich
2013-08-06  7:36         ` Johannes Thumshirn
2013-08-06  8:34           ` Leon Ravich
2013-08-07  3:35         ` Zang Roy-R61911

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=1376825456181-75193.post@n7.nabble.com \
    --to=lravich@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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).