On Tue, Apr 29, 2014 at 10:59 AM, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: >>> [ 82.642468] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready >>> [ 86.741124] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: >>> RX >>> [ 86.763938] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >>> [ 96.748110] ------------[ cut here ]------------ >>> [ 96.756653] WARNING: at >>> /home/shiv/kernel_builds/linux/kernel/net/sched/sch_generic.c:255 >>> dev_watchdog+0x264/0 >>> x284() >>> [ 96.775062] NETDEV WATCHDOG: eth0 (igb): transmit queue 0 timed out > ... >>> [ 259.740507] igb 0000:01:00.0 eth0: Reset adapter >>> [ 263.738512] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: >>> RX >>> [ 278.749107] igb 0000:01:00.0 eth0: Reset adapter >>> [ 282.739504] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: >>> RX >>> ------------------------CONTINUES for >>> EVER--------------------------------------------------- > > Hmmm. This is a completely different problem than the first one or two > in this thread, which were about an external abort while enabling the > device's bus-master access... I assume there's no longer a problem with > enabling bus-master? I thought he meant that he just left Bus Master disabled completely. I wouldn't expect the driver to work at all in that case, so this just looked like a red herring. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
