All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Duc Dang <dhdang@apm.com>
Cc: Tanmay Inamdar <tinamdar@apm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32
Date: Mon, 10 Aug 2015 11:18:23 -0500	[thread overview]
Message-ID: <CAErSpo4VFh7rv81sCAG-eCXVyZh4ub8Trh-ntZhyfy7BzqTr5g@mail.gmail.com> (raw)
In-Reply-To: <CADaLNDk=+J_yOer1ferSCNb_xAC42ULtP2FyCLmYMwa+Gj=vfA@mail.gmail.com>

On Fri, Jul 31, 2015 at 12:00 PM, Duc Dang <dhdang@apm.com> wrote:
> On Wed, Jul 29, 2015 at 8:55 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>> On Tue, Jul 28, 2015 at 08:22:55PM -0500, Bjorn Helgaas wrote:
>>> On Tue, Jul 28, 2015 at 02:50:39PM -0700, Duc Dang wrote:
>>
>>> > Do you have another PCIe card to try on the same reboot test on this board?
>>>
>>> I've seen this on at least two Mellanox cards.  I'm running similar tests
>>> on a different type of card now.
>>
>> FWIW, reboot tests on two machines with Mellanox cards failed, while the
>> same test on a machine with a different proprietary card succeeded.
>
> Thanks, Bjorn.
>
> I don't have the same Mellanox card as yours, but I will also run
> similar reboot test to see if I hit the same issue with my card.

Any more hints on this?  Nothing has changed on my end, so of course
I'm still seeing this, always on machines with Mellanox, and never on
other machines.  Could this be a hardware issue like a signal
integrity or margin issue?  I don't know where to go from here because
I'm not a hardware person, and I don't know anything to do in
software.

Bjorn

WARNING: multiple messages have this Message-ID (diff)
From: bhelgaas@google.com (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32
Date: Mon, 10 Aug 2015 11:18:23 -0500	[thread overview]
Message-ID: <CAErSpo4VFh7rv81sCAG-eCXVyZh4ub8Trh-ntZhyfy7BzqTr5g@mail.gmail.com> (raw)
In-Reply-To: <CADaLNDk=+J_yOer1ferSCNb_xAC42ULtP2FyCLmYMwa+Gj=vfA@mail.gmail.com>

On Fri, Jul 31, 2015 at 12:00 PM, Duc Dang <dhdang@apm.com> wrote:
> On Wed, Jul 29, 2015 at 8:55 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>> On Tue, Jul 28, 2015 at 08:22:55PM -0500, Bjorn Helgaas wrote:
>>> On Tue, Jul 28, 2015 at 02:50:39PM -0700, Duc Dang wrote:
>>
>>> > Do you have another PCIe card to try on the same reboot test on this board?
>>>
>>> I've seen this on at least two Mellanox cards.  I'm running similar tests
>>> on a different type of card now.
>>
>> FWIW, reboot tests on two machines with Mellanox cards failed, while the
>> same test on a machine with a different proprietary card succeeded.
>
> Thanks, Bjorn.
>
> I don't have the same Mellanox card as yours, but I will also run
> similar reboot test to see if I hit the same issue with my card.

Any more hints on this?  Nothing has changed on my end, so of course
I'm still seeing this, always on machines with Mellanox, and never on
other machines.  Could this be a hardware issue like a signal
integrity or margin issue?  I don't know where to go from here because
I'm not a hardware person, and I don't know anything to do in
software.

Bjorn

  reply	other threads:[~2015-08-10 16:18 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 22:42 X-Gene: Unhandled fault: synchronous external abort in pci_generic_config_read32 Bjorn Helgaas
2015-07-24 22:42 ` Bjorn Helgaas
2015-07-25  0:05 ` Duc Dang
2015-07-25  0:05   ` Duc Dang
2015-07-27 11:36   ` Catalin Marinas
2015-07-27 11:36     ` Catalin Marinas
2015-07-28 17:39     ` Duc Dang
2015-07-28 17:39       ` Duc Dang
2015-07-28 18:36       ` Bjorn Helgaas
2015-07-28 18:36         ` Bjorn Helgaas
2015-07-28 16:43   ` Bjorn Helgaas
2015-07-28 16:43     ` Bjorn Helgaas
2015-07-28 17:45     ` Duc Dang
2015-07-28 17:45       ` Duc Dang
2015-07-28 21:29       ` Bjorn Helgaas
2015-07-28 21:29         ` Bjorn Helgaas
2015-07-28 21:50         ` Duc Dang
2015-07-28 21:50           ` Duc Dang
2015-07-29  1:22           ` Bjorn Helgaas
2015-07-29  1:22             ` Bjorn Helgaas
2015-07-29 15:55             ` Bjorn Helgaas
2015-07-29 15:55               ` Bjorn Helgaas
2015-07-31 17:00               ` Duc Dang
2015-07-31 17:00                 ` Duc Dang
2015-08-10 16:18                 ` Bjorn Helgaas [this message]
2015-08-10 16:18                   ` Bjorn Helgaas
2015-08-10 17:38                   ` Catalin Marinas
2015-08-10 17:38                     ` Catalin Marinas
     [not found]                   ` <CADaLNDkUQHzGACfFmYDeJWnaNrKmJUDx4Rby60OWr4FzOjx3rA@mail.gmail.com>
2015-08-10 17:42                     ` Bjorn Helgaas
2015-08-10 17:42                       ` Bjorn Helgaas
2015-08-10 19:07                       ` Duc Dang
2015-08-10 19:07                         ` Duc Dang
2015-08-11 19:28                         ` Bjorn Helgaas
2015-08-11 19:28                           ` Bjorn Helgaas
2015-09-05 20:13                           ` Jon Masters
2015-09-05 20:13                             ` Jon Masters
2015-09-05 20:22                             ` Jon Masters
2015-09-05 20:22                               ` Jon Masters
2016-04-13  9:58         ` Sudeep Holla
2016-04-13  9:58           ` Sudeep Holla
2016-04-13 13:21           ` Bjorn Helgaas
2016-04-13 13:21             ` Bjorn Helgaas
2016-04-13 13:29             ` Sudeep Holla
2016-04-13 13:29               ` Sudeep Holla
2016-04-13 22:17               ` Jon Masters
2016-04-13 22:17                 ` Jon Masters
2015-07-28 14:37 ` Dall, Elizabeth J
2015-07-28 14:37   ` Dall, Elizabeth J
2015-07-28 14:37   ` Dall, Elizabeth J

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=CAErSpo4VFh7rv81sCAG-eCXVyZh4ub8Trh-ntZhyfy7BzqTr5g@mail.gmail.com \
    --to=bhelgaas@google.com \
    --cc=dhdang@apm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tinamdar@apm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.