From mboxrd@z Thu Jan 1 00:00:00 1970 From: ben.dooks@codethink.co.uk (Ben Dooks) Date: Tue, 03 Jun 2014 15:49:13 +0100 Subject: [E1000-devel] ARM support for igb driver In-Reply-To: <536800A8.7090801@intel.com> References: <9B4A1B1917080E46B64F07F2989DADD6533627A5@ORSMSX114.amr.corp.intel.com> <5360041A.7030005@intel.com> <5367AE02.8030802@intel.com> <20140505223839.45778902@skate> <536800A8.7090801@intel.com> Message-ID: <538DE069.5030804@codethink.co.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 05/05/14 22:20, Alexander Duyck wrote: > 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 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. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius