Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)

On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell [off-list ref] wrote:

Hi all,

Changes since 20120716:

Not sure what the root cause of this issue is.

I see the following call-trace in linux-next (next-20120717).

[   23.431889] ------------[ cut here ]------------
[   23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0()
[   23.431897] Hardware name: <HIDDEN>
[   23.431901] ODEBUG: free active (active state 0) object type:
timer_list hint: delayed_work_timer_fn+0x0/0x40
[   23.431901] Modules linked in: joydev snd_hda_intel(+)
snd_hda_codec snd_hwdep snd_pcm snd_page_alloc arc4 iwldvm i915(+)
snd_seq_midi snd_seq_midi_event coretemp snd_rawmidi mac80211
kvm_intel snd_seq drm_kms_helper snd_seq_device kvm drm snd_timer
uvcvideo iwlwifi snd videobuf2_vmalloc i2c_algo_bit videobuf2_memops
psmouse ghash_clmulni_intel samsung_laptop soundcore videobuf2_core
aesni_intel videodev aes_x86_64 btusb lp mei serio_raw ablk_helper
video lpc_ich hid_generic mac_hid cryptd cfg80211 bluetooth parport
microcode usbhid hid r8169
[   23.431935] Pid: 35, comm: khubd Not tainted
3.5.0-rc7-next-20120717-3-iniza-generic #1
[   23.431935] Call Trace:
[   23.431937]  [<ffffffff81053fff>] warn_slowpath_common+0x7f/0xc0
[   23.431944]  [<ffffffff810540f6>] warn_slowpath_fmt+0x46/0x50
[   23.431947]  [<ffffffff81041b89>] ? default_spin_lock_flags+0x9/0x10
[   23.431951]  [<ffffffff813320ee>] debug_print_object+0x8e/0xb0
[   23.431954]  [<ffffffff81071360>] ? __queue_work+0x3a0/0x3a0
[   23.431956]  [<ffffffff81332f05>] debug_check_no_obj_freed+0x125/0x230
[   23.431959]  [<ffffffff8108af15>] ? wake_up_process+0x15/0x20
[   23.431965]  [<ffffffffa008efc5>] ? bt_host_release+0x15/0x30 [bluetooth]
[   23.431975]  [<ffffffff811742aa>] kfree+0x8a/0x160
[   23.431980]  [<ffffffffa008efc5>] bt_host_release+0x15/0x30 [bluetooth]
[   23.431988]  [<ffffffff81411937>] device_release+0x27/0xa0
[   23.431992]  [<ffffffff8131f49c>] kobject_release+0x4c/0xa0
[   23.431997]  [<ffffffff8131f35c>] kobject_put+0x2c/0x60
[   23.432000]  [<ffffffff81411777>] put_device+0x17/0x20
[   23.432003]  [<ffffffffa0079819>] hci_free_dev+0x29/0x30 [bluetooth]
[   23.432010]  [<ffffffffa0064a1d>] btusb_disconnect+0x7d/0xb0 [btusb]
[   23.432015]  [<ffffffff814b173d>] usb_unbind_interface+0x5d/0x1b0
[   23.432019]  [<ffffffff8141576c>] __device_release_driver+0x7c/0xe0
[   23.432022]  [<ffffffff814157fc>] device_release_driver+0x2c/0x40
[   23.432025]  [<ffffffff81415201>] bus_remove_device+0xe1/0x120
[   23.432028]  [<ffffffff814127b0>] device_del+0x120/0x1b0
[   23.432031]  [<ffffffff814af2cf>] usb_disable_device+0xaf/0x1f0
[   23.432034]  [<ffffffff814a6eb0>] usb_disconnect+0x90/0x120
[   23.432038]  [<ffffffff814a9275>] hub_thread+0x9f5/0x13e0
[   23.432041]  [<ffffffff8108e6a0>] ? can_migrate_task+0x210/0x210
[   23.432045]  [<ffffffff81079570>] ? add_wait_queue+0x60/0x60
[   23.432049]  [<ffffffff814a8880>] ? usb_remote_wakeup+0x40/0x40
[   23.432052]  [<ffffffff81078ad3>] kthread+0x93/0xa0
[   23.432055]  [<ffffffff816821a4>] kernel_thread_helper+0x4/0x10
[   23.432059]  [<ffffffff81078a40>] ? kthread_freezable_should_stop+0x70/0x70
[   23.432062]  [<ffffffff816821a0>] ? gs_change+0x13/0x13
[   23.432064] ---[ end trace f5ee68b81851f20a ]---

My debugobjects kernel-config options:

CONFIG_DEBUG_OBJECTS=y
# CONFIG_DEBUG_OBJECTS_SELFTEST is not set
CONFIG_DEBUG_OBJECTS_FREE=y
CONFIG_DEBUG_OBJECTS_TIMERS=y
# CONFIG_DEBUG_OBJECTS_WORK is not set
# CONFIG_DEBUG_OBJECTS_RCU_HEAD is not set
# CONFIG_DEBUG_OBJECTS_PERCPU_COUNTER is not set
CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1

I have attached dmesg + kernel-config.

- Sedat -

On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote:

On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell [off-list ref] wrote:

quoted

Hi all,

Changes since 20120716:

Not sure what the root cause of this issue is.

I see the following call-trace in linux-next (next-20120717).

[   23.431889] ------------[ cut here ]------------
[   23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0()
[   23.431897] Hardware name: <HIDDEN>
[   23.431901] ODEBUG: free active (active state 0) object type:
timer_list hint: delayed_work_timer_fn+0x0/0x40

There are few delayed works on hci_dev structure, it's hard to say which
one is not stopped before kfree.

# CONFIG_DEBUG_OBJECTS_WORK is not set

If you enable that option, it should show which delayed work is causing trouble.

Stanislaw
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Fri, Jul 20, 2012 at 11:47 AM, Stanislaw Gruszka [off-list ref] wrote:

On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote:

quoted

On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell [off-list ref] wrote:

quoted

Hi all,

Changes since 20120716:

Not sure what the root cause of this issue is.

I see the following call-trace in linux-next (next-20120717).

[   23.431889] ------------[ cut here ]------------
[   23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0()
[   23.431897] Hardware name: <HIDDEN>
[   23.431901] ODEBUG: free active (active state 0) object type:
timer_list hint: delayed_work_timer_fn+0x0/0x40

There are few delayed works on hci_dev structure, it's hard to say which
one is not stopped before kfree.

quoted

# CONFIG_DEBUG_OBJECTS_WORK is not set

If you enable that option, it should show which delayed work is causing trouble.

OK, thanks for the explanations & hints!
I will activate that kconfig-option.

FYI: With yesterday's linux-next (next-20120719) I didn't trap into
this regression (same kernel-config + several bootups).

- Sedat -

Stanislaw

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html