netdev - Re: atl1: WARNING at net/sched/sch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080914125841.1310c390@speedy>
Date:	Sun, 14 Sep 2008 12:58:41 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Jay Cliburn <jacliburn@...lsouth.net>
Cc:	David Miller <davem@...emloft.net>, adobriyan@...il.com,
	csnook@...hat.com, netdev@...r.kernel.org
Subject: Re: atl1: WARNING at net/sched/sch_generic.c:221

On Sun, 14 Sep 2008 14:26:54 -0500
Jay Cliburn <jacliburn@...lsouth.net> wrote:

> On Thu, 21 Aug 2008 05:08:57 -0700 (PDT)
> David Miller <davem@...emloft.net> wrote:
> 
> > From: adobriyan@...il.com
> > Date: Thu, 21 Aug 2008 16:04:09 +0400
> > 
> > > On Thu, Aug 21, 2008 at 04:59:10AM -0700, David Miller wrote:
> > > > From: adobriyan@...il.com
> > > > Date: Thu, 21 Aug 2008 15:58:49 +0400
> > > > 
> > > > > This message happens more or less every reboot, sometimes cable
> > > > > unplug/plug is needed to restore connectivity, otherwise card
> > > > > is working fine.
> > > > 
> > > > What kernel version.... no, I can figure it out via osmosis never
> > > > mind! :-)
> > > 
> > > WARN already prints kernel version. ;-)
> > > 
> > > [ 2086.052503] Pid: 0, comm: swapper Not tainted
> > > 2.6.27-rc4-netns-nf #4 ^^^^^^^^^^^^^^^^^^^
> > > 
> > > And before you ask, "-netns-nf" part doesn't matter, it happens with
> > > strictly mainline kernels too and started around multiqueue TX
> > > changes, IIRC.
> > 
> > It's a simple transmit timeout error.
> > 
> > Perhaps atl1 doesn't call netif_carrier_off() in all the places that
> > it should.
> 
> For reference, the original report from Alexey on this matter is here:
> 
> http://marc.info/?l=linux-netdev&m=121931988219314&w=2
> 
> To which Dave responded above, "It's a simple transmit timeout error."
> 
> Should a netdev driver be coded such that a watchdog transmit timeout
> never occurs?
> 
> [ 2086.049998] NETDEV WATCHDOG: eth0 (atl1): transmit timed out
> 
> Or is a watchdog timeout an expected occurrence if a cable is
> unplugged/plugged?

Any transmit timeout is driver or hardware bug. The driver should be
shutting down transmit correctly on cable pull.
--
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