public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	shiv prakash Agarwal
	<chhotu.shiv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux NICS <linux.nics-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"e1000-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<e1000-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Intel NIC testing on ARM
Date: Tue, 29 Apr 2014 10:59:45 -0600	[thread overview]
Message-ID: <535FDA81.3020508@wwwdotorg.org> (raw)
In-Reply-To: <CAErSpo7gtOoh_swzOtSyzkjRXUuZvLWwWpBeqHgy-9J4oB6b7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org).

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?

  parent reply	other threads:[~2014-04-29 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHH3p5+9VCYwS6JdB8aFJ0i4JLcFTMgSgiKOaE2GMnhfWM1bWA@mail.gmail.com>
     [not found] ` <CAErSpo7cDPa0vujMmppWV2RM3vn6=WJ7MCcP8CvwhT4Zn==MwA@mail.gmail.com>
     [not found]   ` <CAHH3p5+qEeYaNKm-L4_RmnkmXeA2030u4t3D+J2wUwBEWiPBPQ@mail.gmail.com>
     [not found]     ` <CAErSpo6+_Tnh9+r50_qK-v0ubpv_pqTcnS7DhMiNi8GbWmsgJA@mail.gmail.com>
     [not found]       ` <CAHH3p5+xTwMaDW-k-0UUZ+21EhCCt2voWXP2jZf_PbRqOdukiA@mail.gmail.com>
     [not found]         ` <CAErSpo7jd2smdoju31r7SWVp4KjNmN+qDAxSUxmVCnUSUOfKTw@mail.gmail.com>
     [not found]           ` <CAHH3p5LKay-1gcgCn1fatM0hOL1Tc+a81Za+ePVjJ6oPo8+6rg@mail.gmail.com>
     [not found]             ` <CAErSpo5VWnAG3xnhn0zgpyC22Eum=ZVR=BM8j2Rvt+=i7LZgjA@mail.gmail.com>
     [not found]               ` <CAHH3p5+aRDq3j_au2Kou6Ef9L+iLaCUVV7hwZPhmD_HU6TxzqQ@mail.gmail.com>
     [not found]                 ` <CAHH3p5KYoPdRO-SEBGMwEPC5dhRd0j_nq_jDz+Z2WMuzOPKREA@mail.gmail.com>
2014-04-29 16:21                   ` Intel NIC testing on ARM Bjorn Helgaas
     [not found]                     ` <CAErSpo7gtOoh_swzOtSyzkjRXUuZvLWwWpBeqHgy-9J4oB6b7g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-29 16:59                       ` Stephen Warren [this message]
2014-04-29 17:23                         ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=535FDA81.3020508@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=chhotu.shiv-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=e1000-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux.nics-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox