Thanks I will give that a try. I forgot to mention that e1000e does not
appear to fail to load. In the failure case, e1000e is still listed in
lsmod as a loaded module.
On Thu, Nov 8, 2012 at 2:17 PM, Alexander Duyck <alexander.h.du...@intel.com
> wrote:
> Looking over the code it looks like there is only one spot where the
> driver could be failing without displaying some sort of error message.
> That would be at the register_netdev call.
>
> If you look in the netdev.c file you should be able to find a tag named
> "err_register:". It would greatly help with debugging if you could
> modifying it by adding an e_err in the line after the tag. With the
> change the code should look something like this:
>
> err_register:
> e_err("register_netdev returned %d\n", err);
> if (!(adapter <
> http://ladlxr.jf.intel.com/lxr/linux-2.6/ident?v=3.5;i=adapter>->flags <
> http://ladlxr.jf.intel.com/lxr/linux-2.6/ident?v=3.5;i=flags> &
> FLAG_HAS_AMT <
> http://ladlxr.jf.intel.com/lxr/linux-2.6/ident?v=3.5;i=FLAG_HAS_AMT>))
>
>
> If you could build and test that driver it will help to confirm if the
> error is actually being returned from netdev_register and this is
> resulting in everything being silently freed after being assigned.
>
> Thanks,
>
> Alex
>
> --
Mark Bidewell
http://www.linkedin.com/in/markbidewell
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
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
