From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [BUG] 2.6.29.1 debugobjects warning
Date: Thu, 23 Apr 2009 10:00:02 -0400 [thread overview]
Message-ID: <20090423140002.GA12852@Krystal> (raw)
Hi,
I got the following warning on my Thinkpad T43p laptop (single-core
32-bits x86). I run the 2.6.29.1 tree, plus LTTng patchset applied. It
seems to come from cpufreq. Any idea what is going on here ?
------------[ cut here ]------------
WARNING: at lib/debugobjects.c:217 debug_print_object+0x5a/0x70()
Hardware name: 2687D5U
ODEBUG: init active object type: timer_list
Modules linked in: irda parport nsc_ircc irtty_sir parport_pc psmouse snd_seq sn
d_seq_midi_event hid_logitech ac unix floppy output battery sir_dev nvram snd_ra
wmidi pcmcia x_tables ip_tables joydev snd_seq_midi evdev video snd_page_alloc s
oundcore led_class i2c_i801 cryptoloop snd snd_seq_dummy rfkill thinkpad_acpi sn
d_seq_oss snd_mixer_oss loop ipw2200 blowfish aes_i586 snd_pcm_oss ac97_bus snd_
seq_device agpgart snd_pcm ide_cd_mod snd_timer intel_agp snd_ac97_codec ide_gen
eric button snd_intel8x0 edd acpi_cpufreq ltt_statedump ipc_trace usbhid thermal
mm_trace snd_intel8x0m fs_trace pcmcia_core rcu_trace lib80211 syscall_trace rs
rc_nonstatic libphy serio_raw kernel_trace tg3 trap_trace libipw crc_ccitt net_t
race dm_mod dm_log dm_region_hash dm_mirror yenta_socket dm_snapshot fat vfat nl
s_cp437 nls_iso8859_1 lp ppdev af_packet drm ntfs ipv6 auth_rpcgss binfmt_misc r
adeon lockd sunrpc nfs
Pid: 3628, comm: cpufreqd Not tainted 2.6.29.1-trace #28
Call Trace:
[<c1044123>] warn_slowpath+0x73/0xd0
[<c1069c28>] ? mark_held_locks+0x48/0x90
[<c13313f5>] ? __mutex_unlock_slowpath+0xd5/0x150
[<c1069f39>] ? trace_hardirqs_on_caller+0x199/0x1f0
[<c1331478>] ? mutex_unlock+0x8/0x10
[<c1331478>] ? mutex_unlock+0x8/0x10
[<c1107b76>] ? sysfs_addrm_finish+0x16/0x230
[<c1107671>] ? sysfs_find_dirent+0x21/0x30
[<c116d71a>] debug_print_object+0x5a/0x70
[<c116e054>] __debug_object_init+0x254/0x340
[<c126533f>] ? cpufreq_governor_dbs+0x10f/0x210
[<c116e187>] debug_object_init+0x17/0x20
[<c104de70>] init_timer+0x10/0x30
[<c104de9b>] init_timer_deferrable+0xb/0x20
[<c12653fd>] cpufreq_governor_dbs+0x1cd/0x210
[<c126205b>] __cpufreq_governor+0xab/0x120
[<c12621cb>] __cpufreq_set_policy+0xfb/0x140
[<c1262c24>] store_scaling_governor+0xa4/0x220
[<c1263550>] ? handle_update+0x0/0x10
[<c1262b80>] ? store_scaling_governor+0x0/0x220
[<c126343e>] store+0x4e/0x70
[<c1106b9c>] sysfs_write_file+0x9c/0x100
[<c10b825c>] vfs_write+0x9c/0x140
[<c1106b00>] ? sysfs_write_file+0x0/0x100
[<c10b8447>] sys_write+0x47/0xe0
[<c1021dde>] syscall_call+0x7/0xb
[<c1020000>] ? sys_vfork+0x20/0x30
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2009-04-23 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 14:00 Mathieu Desnoyers [this message]
2009-04-23 23:46 ` [BUG] 2.6.29.1 debugobjects warning Andrew Morton
2009-04-24 4:34 ` [PATCH -stable] cpufreq fix timer teardown in conservative governor (2.6.28.x, 2.6.29.1) Mathieu Desnoyers
2009-04-28 12:57 ` Mathieu Desnoyers
2009-04-24 4:35 ` [PATCH] cpufreq fix timer teardown in conservative governor (2.6.30-rc2) Mathieu Desnoyers
2009-04-24 6:18 ` Len Brown
2009-04-24 16:12 ` Mathieu Desnoyers
2009-04-26 14:47 ` Henrique de Moraes Holschuh
2009-04-26 16:31 ` Mathieu Desnoyers
2009-04-24 4:38 ` [PATCH] cpufreq fix timer teardown in ondemand governor (2.6.28.x, 2.6.29.1, 2.6.30-rc2) Mathieu Desnoyers
2009-04-28 13:00 ` Mathieu Desnoyers
2009-04-24 6:49 ` [BUG] 2.6.29.1 debugobjects warning Ingo Molnar
2009-04-24 15:07 ` Mathieu Desnoyers
2009-04-27 11:30 ` Thomas Gleixner
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=20090423140002.GA12852@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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