All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexander.h.duyck@intel.com (Alexander Duyck)
To: linux-arm-kernel@lists.infradead.org
Subject: [E1000-devel] ARM support for igb driver
Date: Mon, 05 May 2014 14:20:40 -0700	[thread overview]
Message-ID: <536800A8.7090801@intel.com> (raw)
In-Reply-To: <20140505223839.45778902@skate>

On 05/05/2014 01:38 PM, Thomas Petazzoni wrote:
> Dear Alexander Duyck,
> 
> On Mon, 05 May 2014 08:28:02 -0700, Alexander Duyck wrote:
> 
>>> 1. So overall issue is any memory/config space access hangs(logs above)
>>> if bus master enable bit is set on IGB NIC card,this is not observed
>>> with E1000E NIC cards on same platform.
>>>
>>> 2. Above issue is repro'able on my ARM platform, not x86 ubuntu. Not
>>> sure how much its related to ARM though.
>>>
>>> 3. I saw below differences in lspci -vvv output b/w e1000e and igb, I am
>>> not sure if this has anything to do with above issue.
>>> RC config is same for both cases.
>>>
>>> IGB / E1000E
>>>
>>> Command Status: INTx+/INTx-
>>> PM Status:           NoSoftRst+/NoSoftRst-
>>> DevCap:                FLReset-/FLReset+
>>> No Dev/Link2 Cap/Sta Registers for E1000E
>>> Some differences in AER Registers
>>>
>>> 4. Any idea, if this card is verified on ARM by anybody?
>>>
>>
>> It seems like you are glossing over the obvious issue.  You said it
>> yourself, this works fine on x86.  Therefore this is likely VERY related
>> to ARM, or at least your specific ARM platform configuration.
> 
> Since I haven't seen the beginning of the thread, I might be completely
> off topic. However, I wanted to mention that I have successfully used
> and tested an IGB PCIe NIC on an ARM Armada XP platform. If that is
> useful, I'd be happy to provide you with additional details upon
> request.
> 
> Best regards,
> 
> Thomas
> 


Thomas,

Glad to hear that this is working on your ARM platform as expected.

I believe the issue Shiv is having is due to a problem with the specific
platform as the IGB device is reporting a Data Link Protocol error via
AER and I believe this is what is causing his platform issues.  On
enabling BME the device is likely signalling a Fatal Error message in
response to the DLP error.  The original error he was seeing was:

Unhandled fault: imprecise external abort (0x1406) at 0x00000000

Thanks,

Alex

  reply	other threads:[~2014-05-05 21:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHH3p5KAwyMOY=ai_h0eM+JwYLtTO8d4jVaVOWVtOakhqPRTew@mail.gmail.com>
     [not found] ` <CF7EA37A.4676A%matthew.vick@intel.com>
     [not found]   ` <CAHH3p5JFc3jgeK7OFd1rtgDS3gjRdjiPr3LwwqfyKMPGSTwMWA@mail.gmail.com>
     [not found]     ` <CF7FD060.46A87%matthew.vick@intel.com>
     [not found]       ` <CAHH3p5J8V6uWEzbCoT+x-6_2x1q=nc=_oMn0qnnj113FmeuW6A@mail.gmail.com>
     [not found]         ` <9B4A1B1917080E46B64F07F2989DADD6533627A5@ORSMSX114.amr.corp.intel.com>
     [not found]           ` <CAHH3p5KEPXw5mxP-13evd774nyO5C13ky0=fCaZPCNVx1gh3Ow@mail.gmail.com>
     [not found]             ` <CAHH3p5LaRwgdECxsO4OZSdWEhGt232yj-3347kYEStP6NLg2xg@mail.gmail.com>
     [not found]               ` <5360041A.7030005@intel.com>
     [not found]                 ` <CAHH3p5L6WM3FaZ19Tw9vUcsk+kERfBKnGC2BRtnftJR1pbSF7g@mail.gmail.com>
2014-05-05 15:28                   ` [E1000-devel] ARM support for igb driver Alexander Duyck
     [not found]                     ` <CAHH3p5KEbvziVxg-9o45-chp=6U2JnW=ffk1p85GKFyWXiX8CQ@mail.gmail.com>
2014-05-05 20:00                       ` Alexander Duyck
2014-05-05 20:38                     ` Thomas Petazzoni
2014-05-05 21:20                       ` Alexander Duyck [this message]
     [not found]                         ` <CAHH3p5L4DaORYJ8_6zMEY3ikEnABU1L0B2C6Fezb_g6dCjtr5Q@mail.gmail.com>
2014-05-06 14:58                           ` Alexander Duyck
2014-06-03 14:57                             ` Ben Dooks
2014-05-06 15:18                         ` Arnd Bergmann
2014-05-06 15:24                           ` Lucas Stach
2014-05-06 15:33                             ` Arnd Bergmann
2014-05-30 11:50                               ` shiv prakash Agarwal
2014-05-30 17:21                                 ` Alexander Duyck
2014-05-30 18:02                                   ` shiv prakash Agarwal
2014-05-30 19:18                                     ` Jason Gunthorpe
2014-05-30 19:35                                       ` shiv prakash Agarwal
2014-05-30 19:56                                         ` Arnd Bergmann
2014-05-30 20:14                                           ` shiv prakash Agarwal
2014-05-30 21:11                                             ` Fujinaka, Todd
2014-05-31 18:34                                             ` Arnd Bergmann
2014-06-01  5:56                                               ` shiv prakash Agarwal
2014-06-01 11:46                                                 ` Arnd Bergmann
2014-06-02  4:53                                                   ` shiv prakash Agarwal
2014-06-02 16:05                                                     ` Fujinaka, Todd
2014-06-03 12:33                                                       ` shiv prakash Agarwal
2014-06-03 14:49                         ` Ben Dooks
2014-06-03 15:05                           ` Arnd Bergmann
2014-06-03 15:13                             ` Ben Dooks
2014-06-03 15:23                               ` Arnd Bergmann
2014-06-03 15:31                                 ` Ben Dooks

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=536800A8.7090801@intel.com \
    --to=alexander.h.duyck@intel.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.