From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: csnook@redhat.com, netdev@vger.kernel.org
Subject: Re: atl1: WARNING at net/sched/sch_generic.c:221
Date: Wed, 17 Sep 2008 11:44:46 +0400 [thread overview]
Message-ID: <20080917074446.GB3770@x200.localdomain> (raw)
In-Reply-To: <20080915204431.45201beb@osprey.hogchain.net>
On Mon, Sep 15, 2008 at 08:44:31PM -0500, Jay Cliburn wrote:
> On Tue, 16 Sep 2008 02:45:22 +0400
> Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > On Sun, Sep 14, 2008 at 06:17:14PM -0500, Jay Cliburn wrote:
> > > On Thu, 21 Aug 2008 15:58:49 +0400
> > > adobriyan@gmail.com wrote:
> > >
> > > > This message happens more or less every reboot, sometimes cable
> > > > unplug/plug is needed to restore connectivity, otherwise card is
> > > > working fine.
> > > >
> > > >
> > > > [ 22.570010] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
> > > > [ 26.570011] NET: Registered protocol family 10
> > > > [ 37.551934] eth0: no IPv6 routers present
> > > >
> > > > [rebooted box which is directly connected to a box with
> > > > atl1]
> > > >
> > > > [ 2078.740004] atl1 0000:03:00.0: eth0 link is down
> > > > [ 2080.790004] atl1 0000:03:00.0: eth0 link is up 1000 Mbps full
> > > > duplex [ 2086.049998] NETDEV WATCHDOG: eth0 (atl1): transmit
> > > > timed out [ 2086.050004] ------------[ cut here ]------------
> > > > [ 2086.050004] WARNING: at net/sched/sch_generic.c:221
> > > [...]
> > >
> > > Alexey,
> > >
> > > Can you please try this patch?
> >
> > Seems to help (no more messages), still sometimes no networking until
> > after cable replug. Stay tuned.
>
> Does this stay tuned mean, "Jay, hold off while I (Alexey) troubleshoot
> this further." Or does it mean, "Jay, you've not completely solved the
> problem yet and you need to continue working on it."
I don't know.
Transmit timeout messages definitely dissapeared, no network until cable
replug a) happened earlier, b) much more rare than transmit timeouts.
> If it's the latter, can you please describe your setup and how you reproduce
> the problem? Is the box you have connected directly to the atl1 box used
> as a netconsole?
atl1 netconsoles to r8169, connected directly without any switches.
It usually happens after one of the boxes reboots (well, obviously)
prev parent reply other threads:[~2008-09-17 7:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 11:58 atl1: WARNING at net/sched/sch_generic.c:221 adobriyan
2008-08-21 11:59 ` David Miller
2008-08-21 12:04 ` adobriyan
2008-08-21 12:08 ` David Miller
2008-09-14 19:26 ` Jay Cliburn
2008-09-14 19:58 ` Stephen Hemminger
2008-09-14 23:56 ` David Miller
2008-09-15 0:11 ` Jay Cliburn
2008-09-15 3:14 ` Jeff Garzik
2008-08-22 2:00 ` Jay Cliburn
2008-08-22 21:50 ` Jay Cliburn
2008-09-14 23:17 ` Jay Cliburn
2008-09-15 22:45 ` Alexey Dobriyan
2008-09-16 1:44 ` Jay Cliburn
2008-09-17 7:44 ` Alexey Dobriyan [this message]
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=20080917074446.GB3770@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).