linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [E1000-devel] ARM support for igb driver
Date: Tue, 03 Jun 2014 16:31:15 +0100	[thread overview]
Message-ID: <538DEA43.9020109@codethink.co.uk> (raw)
In-Reply-To: <20276415.m3UVtkWF1S@wuerfel>

On 03/06/14 16:23, Arnd Bergmann wrote:
> On Tuesday 03 June 2014 16:13:07 Ben Dooks wrote:
>> On 03/06/14 16:05, Arnd Bergmann wrote:
>>> On Tuesday 03 June 2014 15:49:13 Ben Dooks wrote:
>>>> On 05/05/14 22:20, Alexander Duyck wrote:
>>>>> On 05/05/2014 01:38 PM, Thomas Petazzoni wrote:
>>>>>
>>>>> 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
>>>>
>>>> I should sort out making these errors non-fatal to the system, there's
>>>> not really much point in killing a process that may not have been the
>>>> initiator of the problem.
>>>
>>> We really shouldn't catch those errors system-wide, it belongs into
>>> the specific host bridge driver, but Shiv refuses to say which one that
>>> is, so we can't fix it.
>>
>> I am not sure what else we can do, either we either have to have a
>> default null handler, or log that they have happened.
>>
>> The whole issue with the "imprecise external" part is that you have
>> no idea what instruction (or core) caused the issue and IIRC there is
>> very little information about what actually sent the abort.
>>
>> I believe these are useful to report as they tend to show that some
>> part of the system has gone wrong. For example, we get them on the
>> rcar-h2 if the system tries to access a unit that has not been
>> properly clocked.
> 
> In my experience, any unit that can send such an abort also has
> a diagnotic register that you can look into to find out at least the
> unit that triggered it so you can disable it.

Not on the rcar-h2.

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

      reply	other threads:[~2014-06-03 15:31 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
     [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 [this message]

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=538DEA43.9020109@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --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 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).