[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130614055346.GB6547@sig21.net>
Date: Fri, 14 Jun 2013 07:53:46 +0200
From: Johannes Stezenbach <js@...21.net>
To: Johannes Berg <johannes@...solutions.net>
Cc: netdev@...r.kernel.org, mcgrof@...not-panic.com, kvalo@...rom.com,
adrian.chadd@...il.com, romieu@...zoreil.com
Subject: Re: [PATCH] alx: add a simple AR816x/AR817x device driver
On Fri, Jun 14, 2013 at 12:29:13AM +0200, Johannes Berg wrote:
> On Fri, 2013-06-14 at 00:24 +0200, Johannes Stezenbach wrote:
>
> > and after "ifconfig eth0 up":
> >
> > [ 539.482153] alx 0000:03:00.0: irq 45 for MSI/MSI-X
> > [ 539.482249] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 539.483169] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full
> > [ 539.483354] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> > [ 544.801438] ------------[ cut here ]------------
> > [ 544.801458] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x19b/0x201()
> > [ 544.801462] Hardware name: System Product Name
> > [ 544.801464] NETDEV WATCHDOG: eth0 (alx): transmit queue 0 timed out
>
> Hmm, this is odd. I might just be forgetting to set something.
>
> > 03:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 08)
>
> OTOH, I have a 8171, so maybe I messed up with my simplifications or it
> simply doesn't work.
>
> > Any idea what to try?
>
> Does it still pass traffic after that? Or is it actually dead?
It is dead. Not interrupts, I tried ping from both ends
of the link (link LED flashes on RX).
Johannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists