From: Borislav Petkov <bp@alien8.de>
To: Josh Boyer <jwboyer@gmail.com>
Cc: netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: atl1c: WARNING: at net/sched/sch_generic.c:255 dev_watchdog
Date: Wed, 7 Dec 2011 17:32:08 +0100 [thread overview]
Message-ID: <20111207163208.GA1840@x1.osrc.amd.com> (raw)
In-Reply-To: <CA+5PVA7bM8ZGaCiyZdHcMVccJYh2=bk-gsHLo9ZmBP_SYT208w@mail.gmail.com>
On Tue, Dec 06, 2011 at 07:12:21PM -0500, Josh Boyer wrote:
> On Tue, Dec 6, 2011 at 6:27 PM, Borislav Petkov <bp@alien8.de> wrote:
> > Hi,
> >
> > this seems like a pretty old issue judging by a quick net search. It
> > still triggers on latest -rc4 here, below the whole trace. I'm willing
> > to test patches :).
> >
> > [14622.820555] atl1c 0000:02:00.0: atl1c: eth0 NIC Link is Up<100 Mbps Full Duplex>
> > [14632.816280] ------------[ cut here ]------------
> > [14632.816314] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x237/0x240()
> > [14632.816323] Hardware name: 30515QG
> > [14632.816332] NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
>
> Matthew Garrett has a patch to the atl1c driver that changed it's ASPM
> behavior that seemed to help. Dave Miller applied it, but I don't see
> it in linux-next for some reason.
Yeah, he reverted them due to build issues. I'm not sure they'll be
coming back though, judging by the thread.
Thanks.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2011-12-07 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 23:27 atl1c: WARNING: at net/sched/sch_generic.c:255 dev_watchdog Borislav Petkov
2011-12-07 0:12 ` Josh Boyer
2011-12-07 10:25 ` Timur Irmatov
2011-12-07 16:32 ` Borislav Petkov [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=20111207163208.GA1840@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).