From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
netdev@vger.kernel.org
Subject: Re: mod_timer: list_add corruption: WARNING: CPU: 1 PID: 0 at lib/list_debug.c:33 __list_add+0xbe/0xd0()
Date: Fri, 19 Jul 2013 14:38:03 +0530 [thread overview]
Message-ID: <51E901F3.8010203@linux.vnet.ibm.com> (raw)
In-Reply-To: <51E8F759.4060202@linux.vnet.ibm.com>
On 07/19/2013 01:52 PM, Srivatsa S. Bhat wrote:
> On 07/16/2013 07:55 PM, Srivatsa S. Bhat wrote:
>> Hi,
>>
>> I happened to hit these warnings on an idle system shortly after
>> boot. And the machine locked up and sent NMIs to all CPUs, some of
>> which have been captured below.
>>
>> Kernel version: v3.11-rc1 + 3 unrelated local cpufreq patches.
>> Options set in .config (which are of interest here):
>>
>> CONFIG_TICK_ONESHOT=y
>> CONFIG_NO_HZ_COMMON=y
>> # CONFIG_HZ_PERIODIC is not set
>> # CONFIG_NO_HZ_IDLE is not set
>> CONFIG_NO_HZ_FULL=y
>> CONFIG_NO_HZ_FULL_ALL=y
>> CONFIG_NO_HZ=y
>> CONFIG_HIGH_RES_TIMERS=y
>>
>> CONFIG_TREE_RCU=y
>> # CONFIG_PREEMPT_RCU is not set
>> CONFIG_RCU_STALL_COMMON=y
>> CONFIG_CONTEXT_TRACKING=y
>> CONFIG_RCU_USER_QS=y
>> CONFIG_CONTEXT_TRACKING_FORCE=y
>> CONFIG_RCU_FANOUT=64
>> CONFIG_RCU_FANOUT_LEAF=16
>> # CONFIG_RCU_FANOUT_EXACT is not set
>> CONFIG_RCU_FAST_NO_HZ=y
>> # CONFIG_TREE_RCU_TRACE is not set
>> CONFIG_RCU_NOCB_CPU=y
>> CONFIG_RCU_NOCB_CPU_ALL=y
>>
>>
>
> Today I hit the same warnings, even without NO_HZ_FULL enabled.
> I've attached my .config with this mail.
>
Adding netdev mailing list to CC.
I had posted the warnings here:
http://marc.info/?l=linux-kernel&m=137398492701587&w=2
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2013-07-19 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 14:25 mod_timer: list_add corruption: WARNING: CPU: 1 PID: 0 at lib/list_debug.c:33 __list_add+0xbe/0xd0() Srivatsa S. Bhat
2013-07-19 8:22 ` Srivatsa S. Bhat
2013-07-19 9:08 ` Srivatsa S. Bhat [this message]
2013-07-19 11:25 ` Thomas Gleixner
2013-07-19 11:47 ` Srivatsa S. Bhat
2013-07-19 13:40 ` Thomas Gleixner
2013-07-19 13:51 ` Eric Dumazet
2013-07-19 16:38 ` Thomas Gleixner
2013-07-19 17:26 ` Eric Dumazet
2013-07-19 18:46 ` Srivatsa S. Bhat
2013-07-20 3:07 ` [PATCH] bridge: do not call setup_timer() multiple times Eric Dumazet
2013-07-20 5:13 ` David Miller
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=51E901F3.8010203@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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).