From: poma <pomidorabelisima-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Stanislaw Gruszka
<sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Mailing-List fedora-kernel
<kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A@public.gmane.org>,
Josh Boyer <jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jamal Hadi Salim <jhs-jkUAjuhPggJWk0Htik3J/w@public.gmane.org>,
"Justin M. Forbes"
<jforbes-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Alexey Kuznetsov <kuznet-v/Mj1YrvjDBInbfyfbPRSQ@public.gmane.org>,
Intel Corporation
<linux.nics-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()
Date: Tue, 18 Feb 2014 11:15:19 +0100 [thread overview]
Message-ID: <530332B7.10909@gmail.com> (raw)
Ahoy!
Debugging S3 aka suspend produces 'WARNINGS':
Steps to Reproduce:
# echo core > /sys/power/pm_test
# cat /sys/power/pm_test
none [core] processors platform devices freezer
# echo mem > /sys/power/state
Results:
- dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-core.diff
https://bugzilla.redhat.com/attachment.cgi?id=864436
Steps to Reproduce:
# echo processors > /sys/power/pm_test
# cat /sys/power/pm_test
none core [processors] platform devices freezer
# echo mem > /sys/power/state
Results:
- dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-processors.diff
https://bugzilla.redhat.com/attachment.cgi?id=864438
Steps to Reproduce:
# echo platform > /sys/power/pm_test
# cat /sys/power/pm_test
none core processors [platform] devices freezer
# echo mem > /sys/power/state
Results:
- dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-platform.diff
https://bugzilla.redhat.com/attachment.cgi?id=864439
RHBZ 1010764:
"[abrt] NETDEV WATCHDOG: em1 (e1000e): transmit queue 0 timed out"
https://bugzilla.redhat.com/show_bug.cgi?id=1010764
Tested with Rawhide 'kernel-debug-3.14.0-0.rc3.git0.1.fc21.x86_64'
http://koji.fedoraproject.org/koji/buildinfo?buildID=498711
poma
_______________________________________________
kernel mailing list
kernel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kernel
next reply other threads:[~2014-02-18 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:15 poma [this message]
[not found] ` <530332B7.10909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-19 4:37 ` WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() poma
[not found] ` <53043521.4060206-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-06 23:32 ` poma
[not found] ` <5319059E.1010205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-07 16:30 ` poma
[not found] ` <5319F40F.4040304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-08 1:33 ` poma
2014-03-08 12:35 ` Francois Romieu
[not found] ` <20140308123528.GA2052-lmTtMILVy1jWQcoT9B9Ug5SCg42XY1Uw0E9HWUfgJXw@public.gmane.org>
2014-03-08 23:30 ` poma
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=530332B7.10909@gmail.com \
--to=pomidorabelisima-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jforbes-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jhs-jkUAjuhPggJWk0Htik3J/w@public.gmane.org \
--cc=jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A@public.gmane.org \
--cc=kuznet-v/Mj1YrvjDBInbfyfbPRSQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux.nics-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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).