Thanks, I will try the the battery trick. I have tried editing BIOS
settings and they seem to be preserved. The PSU in the box did go bad and
maybe that damaged something. I assume you mean the NIC NVM, is there
anything specific I should look for in the NVM?
On Thu, Nov 8, 2012 at 2:38 PM, Brandeburg, Jesse <
jesse.brandeb...@intel.com> wrote:
> I had a look over the ubuntu bug discussion at
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072722?comments=all
>
> There is an NVM utility called flashrom that might be able to see your NVM
> data. You will likely have to boot with iomem=relaxed boot parameter.
>
> Your hardware is acting flaky however, which to me indicates there is
> likely not a driver issue, but more some weird hardware issue.
>
> Maybe the charging circuit for your battery is no longer working? It does
> seem like if you boot and set the CMOS settings to enable the nic it works,
> but after a reboot the CMOS settings are lost (like if you didn’t have a
> battery for cmos at all) In fact can you try that case (no battery) and
> see if things act the same?
>
>
>
>
> -----Original Message-----
> From: Mark Bidewell [mailto:mbide...@gmail.com]
> Sent: Thursday, November 08, 2012 11:25 AM
> To: Duyck, Alexander H
> Cc: e1000-devel@lists.sourceforge.net; Ronciak, John
> Subject: Re: [E1000-devel] Possible Bug in e1000e driver
>
> 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
>
--
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
