All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Rudolf Marek <r.marek@assembler.cz>
Cc: lm-sensors@lm-sensors.org, "R, Durgadoss" <durgadoss.r@intel.com>
Subject: Re: [lm-sensors] coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too
Date: Fri, 16 Sep 2011 16:07:52 +0000	[thread overview]
Message-ID: <20110916160752.GA10978@ericsson.com> (raw)
In-Reply-To: <20110915193018.GA10256@redhat.com>

On Thu, Sep 15, 2011 at 03:30:18PM -0400, Dave Jones wrote:
> just had a user report this against rc6..
> 
> # while true; do rmmod coretemp; modprobe coretemp; done
> 
> 
> [15811.924167] BUG: MAX_LOCKDEP_ENTRIES too low!
> [15811.924171] turning off the locking correctness validator.
> [15811.924175] Pid: 10598, comm: modprobe Not tainted 3.1.0-rc6+ #5
> [15811.924178] Call Trace:
> [15811.924187]  [<ffffffff81081205>] ? up+0x39/0x3e
> [15811.924193]  [<ffffffff8108e556>] add_lock_to_list.constprop.22+0x45/0xa7
> [15811.924198]  [<ffffffff81090c05>] __lock_acquire+0xb7f/0xd0c
> [15811.924204]  [<ffffffff81091594>] ? mark_held_locks+0x6d/0x95
> [15811.924210]  [<ffffffff814e27d5>] ? __slab_alloc+0x41c/0x43d
> [15811.924216]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924221]  [<ffffffff81091295>] lock_acquire+0xf3/0x13e
> [15811.924225]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924230]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924236]  [<ffffffff814e96a3>] _raw_spin_lock+0x40/0x73
> [15811.924241]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924245]  [<ffffffff8127012e>] ? kobject_get+0x18/0x1f
> [15811.924250]  [<ffffffff812701d0>] kobject_add_internal+0x9b/0x18c
> [15811.924255]  [<ffffffff812705fa>] kobject_add+0x91/0xa2
> [15811.924260]  [<ffffffff814c5afd>] ? klist_init+0x33/0x46
> [15811.924265]  [<ffffffff81337bc3>] device_add+0xd5/0x576
> [15811.924271]  [<ffffffff81336ac3>] ? dev_set_name+0x41/0x43
> [15811.924277]  [<ffffffff8133b8f1>] platform_device_add+0x111/0x15b
> [15811.924283]  [<ffffffffa0606cbd>] get_core_online+0x9b/0x143 [coretemp]
> [15811.924290]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924296]  [<ffffffffa005004b>] coretemp_init+0x4b/0x1000 [coretemp]
> [15811.924302]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924308]  [<ffffffff81002099>] do_one_initcall+0x7f/0x13a
> [15811.924313]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924319]  [<ffffffff8109cacf>] sys_init_module+0x114/0x267
> [15811.924324]  [<ffffffff814f0202>] system_call_fastpath+0x16/0x1b
> 
> 
I have tried to reproduce the problem with lockdeb debugging enabled,
but I was unable to see it. Guess I must be missing something. 

Couple of questions:

What CPU and/or system was this seen with ? Output of /proc/cpuinfo might help.
Can you send the configuration file used to build the kernel ?
How long does one have to run the loop ?
What is the output of "sensors" with coretemp loaded ?

Thanks,
Guenter

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Rudolf Marek <r.marek@assembler.cz>
Cc: lm-sensors@lm-sensors.org, "R, Durgadoss" <durgadoss.r@intel.com>
Subject: Re: coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too low!)
Date: Fri, 16 Sep 2011 09:07:52 -0700	[thread overview]
Message-ID: <20110916160752.GA10978@ericsson.com> (raw)
In-Reply-To: <20110915193018.GA10256@redhat.com>

On Thu, Sep 15, 2011 at 03:30:18PM -0400, Dave Jones wrote:
> just had a user report this against rc6..
> 
> # while true; do rmmod coretemp; modprobe coretemp; done
> 
> 
> [15811.924167] BUG: MAX_LOCKDEP_ENTRIES too low!
> [15811.924171] turning off the locking correctness validator.
> [15811.924175] Pid: 10598, comm: modprobe Not tainted 3.1.0-rc6+ #5
> [15811.924178] Call Trace:
> [15811.924187]  [<ffffffff81081205>] ? up+0x39/0x3e
> [15811.924193]  [<ffffffff8108e556>] add_lock_to_list.constprop.22+0x45/0xa7
> [15811.924198]  [<ffffffff81090c05>] __lock_acquire+0xb7f/0xd0c
> [15811.924204]  [<ffffffff81091594>] ? mark_held_locks+0x6d/0x95
> [15811.924210]  [<ffffffff814e27d5>] ? __slab_alloc+0x41c/0x43d
> [15811.924216]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924221]  [<ffffffff81091295>] lock_acquire+0xf3/0x13e
> [15811.924225]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924230]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924236]  [<ffffffff814e96a3>] _raw_spin_lock+0x40/0x73
> [15811.924241]  [<ffffffff812701d0>] ? kobject_add_internal+0x9b/0x18c
> [15811.924245]  [<ffffffff8127012e>] ? kobject_get+0x18/0x1f
> [15811.924250]  [<ffffffff812701d0>] kobject_add_internal+0x9b/0x18c
> [15811.924255]  [<ffffffff812705fa>] kobject_add+0x91/0xa2
> [15811.924260]  [<ffffffff814c5afd>] ? klist_init+0x33/0x46
> [15811.924265]  [<ffffffff81337bc3>] device_add+0xd5/0x576
> [15811.924271]  [<ffffffff81336ac3>] ? dev_set_name+0x41/0x43
> [15811.924277]  [<ffffffff8133b8f1>] platform_device_add+0x111/0x15b
> [15811.924283]  [<ffffffffa0606cbd>] get_core_online+0x9b/0x143 [coretemp]
> [15811.924290]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924296]  [<ffffffffa005004b>] coretemp_init+0x4b/0x1000 [coretemp]
> [15811.924302]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924308]  [<ffffffff81002099>] do_one_initcall+0x7f/0x13a
> [15811.924313]  [<ffffffffa0050000>] ? 0xffffffffa004ffff
> [15811.924319]  [<ffffffff8109cacf>] sys_init_module+0x114/0x267
> [15811.924324]  [<ffffffff814f0202>] system_call_fastpath+0x16/0x1b
> 
> 
I have tried to reproduce the problem with lockdeb debugging enabled,
but I was unable to see it. Guess I must be missing something. 

Couple of questions:

What CPU and/or system was this seen with ? Output of /proc/cpuinfo might help.
Can you send the configuration file used to build the kernel ?
How long does one have to run the loop ?
What is the output of "sensors" with coretemp loaded ?

Thanks,
Guenter

  reply	other threads:[~2011-09-16 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 19:30 coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too low!) Dave Jones
2011-09-16 16:07 ` Guenter Roeck [this message]
2011-09-16 16:07   ` Guenter Roeck
2011-09-16 16:29   ` [lm-sensors] coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too Dave Jones
2011-09-16 16:29     ` coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too low!) Dave Jones
2011-09-18 18:05     ` [lm-sensors] coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too Guenter Roeck
2011-09-18 18:05       ` coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too low!) Guenter Roeck
2011-09-20 10:40 ` Peter Zijlstra

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=20110916160752.GA10978@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=davej@redhat.com \
    --cc=durgadoss.r@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=r.marek@assembler.cz \
    /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.