On 05/04/2014 11:55 PM, shiv prakash Agarwal wrote: > + linux-arm-kernel mailing list. > > Thanks Alex, > > 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. You also mention "some differences in the AER Registers", how about you tell us what was different there since as I pointed out that could tell us if there is some error the device detected that is triggering the problem, or better yet could you just send us the lspci -vvv output from the problem system. That would give us much more to work with and help us to understand what the issue is. Thanks, Alex ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
