From: Dave Jones Date: Fri, 16 Sep 2011 16:29:29 +0000 Subject: Re: [lm-sensors] coretemp breaks lockdep. (MAX_LOCKDEP_ENTRIES too Message-Id: <20110916162929.GB2714@redhat.com> List-Id: References: <20110915193018.GA10256@redhat.com> <20110916160752.GA10978@ericsson.com> In-Reply-To: <20110916160752.GA10978@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Guenter Roeck Cc: Linux Kernel , Rudolf Marek , lm-sensors@lm-sensors.org, "R, Durgadoss" On Fri, Sep 16, 2011 at 09:07:52AM -0700, Guenter Roeck wrote: > On Thu, Sep 15, 2011 at 03:30:18PM -0400, Dave Jones wrote: > > just had a user report this against rc6.. > >=20 > > # while true; do rmmod coretemp; modprobe coretemp; done > >=20 > >=20 > > [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] [] ? up+0x39/0x3e > > [15811.924193] [] add_lock_to_list.constprop.22+0x4= 5/0xa7 > > [15811.924198] [] __lock_acquire+0xb7f/0xd0c > > [15811.924204] [] ? mark_held_locks+0x6d/0x95 > > [15811.924210] [] ? __slab_alloc+0x41c/0x43d > > [15811.924216] [] ? kobject_add_internal+0x9b/0x18c > > [15811.924221] [] lock_acquire+0xf3/0x13e > > [15811.924225] [] ? kobject_add_internal+0x9b/0x18c > > [15811.924230] [] ? kobject_add_internal+0x9b/0x18c > > [15811.924236] [] _raw_spin_lock+0x40/0x73 > > [15811.924241] [] ? kobject_add_internal+0x9b/0x18c > > [15811.924245] [] ? kobject_get+0x18/0x1f > > [15811.924250] [] kobject_add_internal+0x9b/0x18c > > [15811.924255] [] kobject_add+0x91/0xa2 > > [15811.924260] [] ? klist_init+0x33/0x46 > > [15811.924265] [] device_add+0xd5/0x576 > > [15811.924271] [] ? dev_set_name+0x41/0x43 > > [15811.924277] [] platform_device_add+0x111/0x15b > > [15811.924283] [] get_core_online+0x9b/0x143 [coret= emp] > > [15811.924290] [] ? 0xffffffffa004ffff > > [15811.924296] [] coretemp_init+0x4b/0x1000 [corete= mp] > > [15811.924302] [] ? 0xffffffffa004ffff > > [15811.924308] [] do_one_initcall+0x7f/0x13a > > [15811.924313] [] ? 0xffffffffa004ffff > > [15811.924319] [] sys_init_module+0x114/0x267 > > [15811.924324] [] system_call_fastpath+0x16/0x1b > >=20 > >=20 > I have tried to reproduce the problem with lockdeb debugging enabled, > but I was unable to see it. Guess I must be missing something.=20 >=20 > Couple of questions: >=20 > What CPU and/or system was this seen with ? Output of /proc/cpuinfo migh= t help. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU L9600 @ 2.13GHz stepping : 10 cpu MHz : 800.000 cache size : 6144 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat = pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constan= t_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_= cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_s= hadow vnmi flexpriority bogomips : 4266.41 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU L9600 @ 2.13GHz stepping : 10 cpu MHz : 2134.000 cache size : 6144 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat = pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constan= t_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_= cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_s= hadow vnmi flexpriority bogomips : 4266.79 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: > Can you send the configuration file used to build the kernel ? User reported it using a fedora config. I reproduced it using a similar one= .. http://codemonkey.org.uk/junk/coretempbug-config > How long does one have to run the loop ? happened within a few seconds for me > What is the output of "sensors" with coretemp loaded ? $ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +81.0=B0C (crit =3D +100.0=B0C) temp2: +62.0=B0C (crit =3D +100.0=B0C) temp3: +61.0=B0C (crit =3D +100.0=B0C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +78.0=B0C (high =3D +105.0=B0C, hyst =3D +0.0=B0C) (crit =3D +105.0=B0C) Core 1: +81.0=B0C (high =3D +105.0=B0C, hyst =3D +0.0=B0C) (crit =3D +105.0=B0C) _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors