On 04/29/2014 10:21 AM, Bjorn Helgaas wrote: > [+cc igb, tegra folks] > > On Tue, Apr 29, 2014 at 9:25 AM, shiv prakash Agarwal > <chhotu.shiv@xxxxxxxxx> wrote: >> Also if I disable enabling bus master from igb driver, then ethernet >> functionality does not work due to below issue: > > This looks like an igb or (more likely) a tegra host bridge driver > issue, so hopefully somebody there can help you. > >> root@tegra-ubuntu:~# dhclient eth0 Are you running mainline Linux, or NVIDIA's "Linux4Tegra"? IIRC, that shell prompt is the L4T default, and I think kernel version 3.10 (mentioned in some of your logs) is the current L4T kernel version. If you're running L4T, you should contact the NVIDIA L4T team for support (linux-tegra-bugs@xxxxxxxxxx). If you can reproduce this issue on a recent mainline Linux (say 3.14, 3.15-rc* or or linux-next), we can continue this conversation here. In this case, I'd like to see: * Details re: which HW/board you're running on, how you're plugging in the PCIe device, etc. * U-Boot version/commit ID, so we can check any setup it's doing. * Link to source tree, so we can double-check the driver code you're running. It would be best to try a more recent source tree. Then perhaps we'll be able to try and repro this problem, although I don't have that NIC so that might be hard... >> [ 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? -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
