netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200()
Date: Sun, 5 Feb 2012 14:59:13 -0800	[thread overview]
Message-ID: <20120205145913.194746473361e324bda1eb4a@gmail.com> (raw)
In-Reply-To: <20120205222141.GA26223@electric-eye.fr.zoreil.com>

On Sun, 5 Feb 2012 23:21:41 +0100
Francois Romieu <romieu@fr.zoreil.com> wrote:

> Larry Finger <Larry.Finger@lwfinger.net> :
> > On 02/05/2012 03:40 PM, Justin P. Mattock wrote:
> > >
> > >this showed up as I woke the machine up from suspend. machine is connected
> > >I just see networkmanager constantly spinning trying to connect then telling me
> > >the wired network is not connected(even though its just wireless that I have).
> 
> [ 1273.447349] r8169 0000:06:00.0: Refused to change power state, currently in D3
> [ 1273.571024] psmouse serio1: elantech: retrying ps2 command 0xf8 (2).
> [ 1273.656709] r8169 0000:06:00.0: eth0: link up
>                                          ^^^^^^^
> 
> Justin, you did not ever connect a cable, did you ?

nope! was using wireless the whole time. 

> 
> [...]
> > 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.
> 
> It could hide the problem but the D3 + link up messages are nonetheless
> a bit unexpected.
> 
> > P.S. Unless it happens with just the ath9k active, this ML is likely
> > not the correct one.
> 
> Yes, please Cc: netdev@vger.kernel.org + me instead.
> 
> Thanks.
> 
> -- 
> Ueimor

removed linux-wireless and added netdev to the cc's
will monitor this and report anything that shows up.

-- 
Justin P. Mattock <justinmattock@gmail.com>

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120205134050.7e135bb231b613806a2e0b70@gmail.com>
     [not found] ` <4F2F0065.9040909@lwfinger.net>
     [not found]   ` <20120205222141.GA26223@electric-eye.fr.zoreil.com>
2012-02-05 22:59     ` Justin P. Mattock [this message]
2012-03-19  4:01       ` WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200() Justin Mattock
2012-03-20  9:37         ` Francois Romieu
2012-03-20 14:16           ` Justin P. Mattock
2012-03-20 21:31             ` Justin P. Mattock
2012-03-20 23:27               ` Francois Romieu
2012-03-21  5:15                 ` Justin P. Mattock

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=20120205145913.194746473361e324bda1eb4a@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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).