From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x1f2/0x200()
Date: Tue, 20 Mar 2012 14:31:19 -0700 [thread overview]
Message-ID: <4F68F727.9030405@gmail.com> (raw)
In-Reply-To: <4F689131.2030607@gmail.com>
On 03/20/2012 07:16 AM, Justin P. Mattock wrote:
> On 03/20/2012 02:37 AM, Francois Romieu wrote:
>> (Larry removed)
>>
>> Justin Mattock<justinmattock@gmail.com> :
>> [...]
>>> seems I see this with the latest linux-next:
>>
>> Thanks for testing.
>>
>> [...]
>>> [21740.318685] r8169 0000:06:00.0: eth0: link up
>>> [21752.292679] r8169 0000:06:00.0: eth0: link up
>>> [21764.268569] r8169 0000:06:00.0: eth0: link up
>>> [21776.254393] r8169 0000:06:00.0: eth0: link up
>>> [21788.235797] r8169 0000:06:00.0: eth0: link up
>>> [21800.196524] r8169 0000:06:00.0: eth0: link up
>>> [21812.172497] r8169 0000:06:00.0: eth0: link up
>>
>> This is completely broken. I could understand a few up/down link changes
>> until things settles but the driver should not claim periodically that
>> the link is up when there is no cable, at least not with a supported
>> chipset.
>>
>> Can you apply the debug helper below and report a complete dmesg from
>> boot with the same test (please remove l-k, netdev is good enough) ?
>
> I removed linux-kernel from the Cc's and applied your patch.. system
> built fine, and suspend wakes up fine without the ethernet trying to
> connect like it was doing. will run this patch for a few Thanks for this!
>
> dmesg is here: http://fpaste.org/jHSX/
> (I have another patch added in, but it should not affect anything).
>
>
well i dont know what happened.. I suspend throughout the day without
any issues, but then on one wakeup everything went to crap ethernet
started to try and connect without any wires in.. only thing I can think
of is I was dongling with my phone(but the phone was disconnected before
suspend),which uses a different module..
dmesg here:
http://fpaste.org/mcNC/
Justin P. Mattock
next prev parent reply other threads:[~2012-03-20 21:31 UTC|newest]
Thread overview: 12+ 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-03-20 14:16 ` Justin P. Mattock
2012-03-20 21:31 ` Justin P. Mattock [this message]
2012-03-20 23:27 ` Francois Romieu
2012-03-21 5:15 ` Justin P. Mattock
2012-02-05 22:29 ` Justin P. Mattock
2012-02-05 22:35 ` Dave Jones
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=4F68F727.9030405@gmail.com \
--to=justinmattock@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.