On Thu, Jun 6, 2013 at 1:10 PM, Ronciak, John <[email protected]> wrote: > OK so a couple of thing kind of stand out. What interface is the e1000 on? > eth0? That's not being called out or you filtered it out from the dmesg. > Early on eth2 is the e1000 interface but later it's one of the Gianfar > interfaces. Can you clear this up for us?
The interfaces do get renamed early in the boot process. We use ifrename to force the e1000 interface to eth2. The gianfar are on eth0 and eth1. > Also, it looks like you have a bonding configuration. What interfaces are > being bonded? You also have a Gianfar NIC with 2 interfaces. Is this still > happening when no bonding is configured? Does the problem occur when the > Gianfar interfaces are down/inactive? I'm just trying to narrow things down > a bit. I'd like this to be tried with just the e1000 driver being active to > see if it's happening then. Currently, there is no bonding configured at all. While we do allow bonding, there is currently no bonded interfaces. I tried the up/down loop with the gianfar devices, and I do not get the failure. They are connected to the same network, and no problem. I shutdown the gianfar adapters (eth0 and eth1) and re-ran the up/down loop. Still get the same panic. > Can you send the entire dmesg? Is it too big to email? That was the entire dmesg output. Thanks, Pete ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
