public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-kernel@vger.kernel.org
Subject: Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200()
Date: Sun, 5 Feb 2012 17:35:27 -0500	[thread overview]
Message-ID: <20120205223527.GA19001@redhat.com> (raw)
In-Reply-To: <20120205142946.953cf9ed55b0adce3974a759@gmail.com>

On Sun, Feb 05, 2012 at 02:29:46PM -0800, Justin P. Mattock wrote:
 
 > > > [ 2270.546572] WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200()
 > > > [ 2270.546576] Hardware name: 0914
 > > > [ 2270.546580] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
 > > 
 > > The error clearly comes from r8169, not from ath9k. If you unload r8169 before 
 > > suspending, does this still happen? My suspicion is that NM is getting confused.
 > > 
 > as a quick test I unloaded r8169 and did not see this message, but I also added it in and suspended
 > and no warning message as well.

FWIW, we've been seeing reports of this in Fedora since last summer.
https://bugzilla.redhat.com/show_bug.cgi?id=715137

(We have reports on other chips too, but this bug is just the r8169 reports)

	Dave


      reply	other threads:[~2012-02-05 22:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 21:40 WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200() Justin P. Mattock
2012-02-05 22:19 ` Larry Finger
2012-02-05 22:21   ` Francois Romieu
2012-02-05 22:59     ` Justin P. Mattock
2012-03-19  4:01       ` Justin Mattock
2012-03-20  9:37         ` Francois Romieu
2012-02-05 22:29   ` Justin P. Mattock
2012-02-05 22:35     ` Dave Jones [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=20120205223527.GA19001@redhat.com \
    --to=davej@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=justinmattock@gmail.com \
    --cc=linux-kernel@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