lockdep spew

[Dave Jones]

I don't think I've seen this one reported yet.
This kernel was a 2.6.18rc3-gitSomething, but I don't think
anything has changed recently that would explain this?

		Dave

-- 
http://www.codemonkey.org.uk
> --- Begin Message ---
> Please do not reply directly to this email. All additional
> comments should be made in the comments box of this bug report.
>
>
>
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201726
>
>            Summary: massive kernel spewage with DWARF2 unwinder errors
>            Product: Fedora Core
>            Version: fc6test2
>           Platform: x86_64
>         OS/Version: Linux
>             Status: NEW
>           Severity: high
>           Priority: normal
>          Component: kernel
>         AssignedTo: kernel-maint@xxxxxxxxxx
>         ReportedBy: netllama@xxxxxxxxx
>          QAContact: bbrock@xxxxxxxxxx
>                 CC: wtogami@xxxxxxxxxx
>
>
> Description of problem:
>
>
> Version-Release number of selected component (if applicable):
> 2.6.17-1.2517.fc6 and 2.6.17-1.2530.fc6
>
> How reproducible:
>
>
> Steps to Reproduce:
> 1. Boot, and the fireworks begin early on at "checking if image is initramfs..."
> 2. Even after booting, there's a ton more spewage, seemingly at random when
> doing things as simple as ssh/scp, and also when running the attached sysreport.
>
>   
> Actual results:
>
> #######
> checking if image is initramfs...
> =============================================
> [ INFO: possible recursive locking detected ]
> ---------------------------------------------
> swapper/1 is trying to acquire lock:
>  (&nc->lock){....}, at: [<ffffffff8020782c>] kmem_cache_free+0x1a1/0x26c
>
> but task is already holding lock:
>  (&nc->lock){....}, at: [<ffffffff8020b47e>] kfree+0x1b3/0x27e
>
> other info that might help us debug this:
> 2 locks held by swapper/1:
>  #0:  (&nc->lock){....}, at: [<ffffffff8020b47e>] kfree+0x1b3/0x27e
>  #1:  (&parent->list_lock){....}, at: [<ffffffff802dae22>]
> __drain_alien_cache+0x37/0
> x77
>
> stack backtrace:
>
> Call Trace:
>  [<ffffffff8026e77d>] show_trace+0xae/0x30e
>  [<ffffffff8026e9f2>] dump_stack+0x15/0x17
>  [<ffffffff802a7f23>] __lock_acquire+0x135/0xa54
>  [<ffffffff802a8de3>] lock_acquire+0x4b/0x69
>  [<ffffffff8026774b>] _spin_lock+0x25/0x31
>  [<ffffffff8020782c>] kmem_cache_free+0x1a1/0x26c
>  [<ffffffff802da9a8>] slab_destroy+0x12b/0x138
>  [<ffffffff802dab5f>] free_block+0x1aa/0x1ee
>  [<ffffffff802dae48>] __drain_alien_cache+0x5d/0x77
>  [<ffffffff8020b49b>] kfree+0x1d0/0x27e
>  [<ffffffff80968444>] free+0x9/0xb
>  [<ffffffff80968461>] huft_free+0x1b/0x27
>  [<ffffffff8096961c>] inflate_dynamic+0x4f0/0x525
>  [<ffffffff80969b18>] unpack_to_rootfs+0x4c7/0x930
>  [<ffffffff80969fe6>] populate_rootfs+0x65/0xe7
>  [<ffffffff8026d710>] init+0x190/0x3cd
>  [<ffffffff8026135e>] child_rip+0x8/0x12
> DWARF2 unwinder stuck at child_rip+0x8/0x12
> Leftover inexact backtrace:
>  [<ffffffff80267a32>] _spin_unlock_irq+0x2b/0x31
>  [<ffffffff8026099c>] restore_args+0x0/0x30
>  [<ffffffff8036c696>] acpi_os_acquire_lock+0x9/0xb
>  [<ffffffff8026d580>] init+0x0/0x3cd
>  [<ffffffff80261356>] child_rip+0x0/0x12
>
>  it is
> ##############
>
> ############
>                                                        sibling
>   task                 PC          pid father child younger older
> init          S ffff8101442eda08     0     1      0     2               (NOTLB)
>  ffff8101442eda08 ffff8101442ed988 ffffffff806c0d80 0000000000000008
>  ffff81013fc6a040 ffffffff80567e80 000000a047ea2983 0000000000015fe9
>  ffff81013fc6a228 ffff810100000000 ffffffff806c0d80 ffff8101442eda08
> Call Trace:
>  [<ffffffff80265886>] schedule_timeout+0x8c/0xb3
>  [<ffffffff8021204c>] do_select+0x470/0x4de
>  [<ffffffff802e705b>] core_sys_select+0x1b7/0x266
>  [<ffffffff80217106>] sys_select+0x147/0x172
>  [<ffffffff8026040e>] system_call+0x7e/0x83
> DWARF2 unwinder stuck at system_call+0x7e/0x83
> Leftover inexact backtrace:
>
> migration/0   S ffff81013fc77e98     0     2      1             3       (L-TLB)
>  ffff81013fc77e98 0000000100000296 0000000000000002 0000000000000001
>  ffff8101442ea040 ffffffff80567e80 000000a0598b50f5 000000000000119a
>  ffff8101442ea228 ffff810100000000 0000000000000046 ffff81013fc77e78
> Call Trace:
>  [<ffffffff80246a22>] migration_thread+0x1a2/0x23f
>  [<ffffffff802353fe>] kthread+0x100/0x136
>  [<ffffffff8026135e>] child_rip+0x8/0x12
> DWARF2 unwinder stuck at child_rip+0x8/0x12
> Leftover inexact backtrace:
>  [<ffffffff80267a32>] _spin_unlock_irq+0x2b/0x31
>  [<ffffffff8026099c>] restore_args+0x0/0x30
>  [<ffffffff802352fe>] kthread+0x0/0x136
>  [<ffffffff80261356>] child_rip+0x0/0x12
> #########
>
> Expected results:
> No spewage
>
> Additional info:
> I'm seeing all of this behavior on an HP xw9300 workstation
>
> ------- Additional Comments From netllama@xxxxxxxxx  2006-08-08 11:27 EST -------
> Created an attachment (id=133794)
>  --> (https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=133794&action=view)
> dmesg which includes the copious backtraces
>
>
> -- 
> Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> --- End Message ---