2.6.17-1.2630.fc6 - INFO: hard-safe -> hard-unsafe lock order detected

Aryanto Rachmad aryanto at chello.at
Fri Sep 8 21:26:49 UTC 2006


Hi guys,

I am not sure if this worth to report. Otherwise I am sorry to fill up
your mailbox.

I am using asterisk PBX with TDM400P PCI card on my IBM xSeries 330 SMP.
I can make calls and got no errors, so everything seems to be working.

Cheers,

Anto
----

kernel: ======================================================
kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
kernel: 2.6.17-1.2630.fc6 #1
kernel: ------------------------------------------------------
kernel: fxotune/1167 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
kernel:  (zone_lock){--..}, at: [<f8944693>] set_tone_zone+0x43/0x90
[zaptel]
kernel:
kernel: and this task is already holding:
kernel:  (&chan->lock){++..}, at: [<f8947327>]
initialize_channel+0x37/0x540 [zaptel]
kernel: which would create a new lock dependency:
kernel:  (&chan->lock){++..} -> (zone_lock){--..}
kernel:
kernel: but this new dependency connects a hard-irq-safe lock:
kernel:  (&chan->lock){++..}
kernel: ... which became hard-irq-safe at:
kernel:   [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:   [<c0614487>] _spin_lock_irqsave+0x22/0x32
kernel:   [<f8944eb7>] zt_ec_chunk+0x17/0x10a0 [zaptel]
kernel:   [<f8a4c3ab>] wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:   [<c0450f94>] handle_IRQ_event+0x20/0x4d
kernel:   [<c0451055>] __do_IRQ+0x94/0xef
kernel:   [<c040678d>] do_IRQ+0x9e/0xbd
kernel:
kernel: to a hard-irq-unsafe lock:
kernel:  (zone_lock){--..}
kernel: ... which became hard-irq-unsafe at:
kernel: ...  [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:   [<c06141b0>] _write_lock+0x19/0x28
kernel:   [<f894dd07>] zt_ioctl+0x157/0x15b0 [zaptel]
kernel:   [<c048333e>] do_ioctl+0x4e/0x67
kernel:   [<c04835af>] vfs_ioctl+0x258/0x26b
kernel:   [<c0483609>] sys_ioctl+0x47/0x62
kernel:   [<c0403faf>] syscall_call+0x7/0xb
kernel:
kernel: other info that might help us debug this:
kernel:
kernel: 1 lock held by fxotune/1167:
kernel:  #0:  (&chan->lock){++..}, at: [<f8947327>]
initialize_channel+0x37/0x540 [zaptel]
kernel:
kernel: the hard-irq-safe lock's dependencies:
kernel: -> (&chan->lock){++..} ops: 0 {
kernel:    initial-use  at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c0614487>]
_spin_lock_irqsave+0x22/0x32
kernel:                         [<f89444a2>] zt_reallocbufs+0x32/0x1e0
[zaptel]
kernel:                         [<f8947be4>] close_channel+0x14/0x390
[zaptel]
kernel:                         [<f894801a>] zt_chan_reg+0xba/0x160
[zaptel]
kernel:                         [<f89481a8>] zt_register+0xe8/0x2b0
[zaptel]
kernel:                         [<f8a4d17c>] wctdm_init_one+0x38c/0x1150
[wctdm]
kernel:                         [<c04f4009>] pci_device_probe+0x39/0x5b
kernel:                         [<c055509e>]
driver_probe_device+0x45/0x92
kernel:                         [<c05551cb>] __driver_attach+0x68/0x93
kernel:                         [<c0554b17>] bus_for_each_dev+0x3a/0x5f
kernel:                         [<c0554ff9>] driver_attach+0x14/0x17
kernel:                         [<c05547ee>] bus_add_driver+0x68/0x106
kernel:                         [<c0555474>] driver_register+0x78/0x7d
kernel:                         [<c04f415a>]
__pci_register_driver+0x4f/0x69
kernel:                         [<f8846071>] 0xf8846071
kernel:                         [<c0442662>]
sys_init_module+0x16ad/0x1856
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    in-hardirq-W at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c0614487>]
_spin_lock_irqsave+0x22/0x32
kernel:                         [<f8944eb7>] zt_ec_chunk+0x17/0x10a0
[zaptel]
kernel:                         [<f8a4c3ab>]
wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:                         [<c0450f94>] handle_IRQ_event+0x20/0x4d
kernel:                         [<c0451055>] __do_IRQ+0x94/0xef
kernel:                         [<c040678d>] do_IRQ+0x9e/0xbd
kernel:    in-softirq-W at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c0614487>]
_spin_lock_irqsave+0x22/0x32
kernel:                         [<f8944eb7>] zt_ec_chunk+0x17/0x10a0
[zaptel]
kernel:                         [<f8a4c3ab>]
wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:                         [<c0450f94>] handle_IRQ_event+0x20/0x4d
kernel:                         [<c0451055>] __do_IRQ+0x94/0xef
kernel:                         [<c040678d>] do_IRQ+0x9e/0xbd
kernel:  }
kernel:  ... key      at: [<f8960f1c>] __key.18214+0x0/0xffff207b
[zaptel]
kernel:
kernel: the hard-irq-unsafe lock's dependencies:
kernel: -> (zone_lock){--..} ops: 0 {
kernel:    initial-use  at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c06141b0>] _write_lock+0x19/0x28
kernel:                         [<f894dd07>] zt_ioctl+0x157/0x15b0
[zaptel]
kernel:                         [<c048333e>] do_ioctl+0x4e/0x67
kernel:                         [<c04835af>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483609>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    softirq-on-W at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c06141b0>] _write_lock+0x19/0x28
kernel:                         [<f894dd07>] zt_ioctl+0x157/0x15b0
[zaptel]
kernel:                         [<c048333e>] do_ioctl+0x4e/0x67
kernel:                         [<c04835af>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483609>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    hardirq-on-W at:
kernel:                         [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:                         [<c06141b0>] _write_lock+0x19/0x28
kernel:                         [<f894dd07>] zt_ioctl+0x157/0x15b0
[zaptel]
kernel:                         [<c048333e>] do_ioctl+0x4e/0x67
kernel:                         [<c04835af>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483609>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:  }
kernel:  ... key      at: [<f89573b8>] zone_lock+0x10/0xffffbbef
[zaptel]
kernel:
kernel: stack backtrace:
kernel:  [<c04051ee>] show_trace_log_lvl+0x58/0x171
kernel:  [<c0405802>] show_trace+0xd/0x10
kernel:  [<c040591b>] dump_stack+0x19/0x1b
kernel:  [<c043ae58>] check_usage+0x1ee/0x1fb
kernel:  [<c043b9c5>] __lock_acquire+0x828/0x99c
kernel:  [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:  [<c0614292>] _read_lock+0x19/0x28
kernel:  [<f8944693>] set_tone_zone+0x43/0x90 [zaptel]
kernel:  [<f894764d>] initialize_channel+0x35d/0x540 [zaptel]
kernel:  [<f8948afe>] zt_open+0x20e/0x2a0 [zaptel]
kernel:  [<c047ae2f>] chrdev_open+0x105/0x13a
kernel:  [<c0471a4a>] __dentry_open+0xc8/0x1ab
kernel:  [<c0471b9b>] nameidata_to_filp+0x1c/0x2e
kernel:  [<c0471bdb>] do_filp_open+0x2e/0x35
kernel:  [<c0471c22>] do_sys_open+0x40/0xb5
kernel:  [<c0471cc3>] sys_open+0x16/0x18
kernel:  [<c0403faf>] syscall_call+0x7/0xb
kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
kernel: Leftover inexact backtrace:
kernel:  [<c0405802>] show_trace+0xd/0x10
kernel:  [<c040591b>] dump_stack+0x19/0x1b
kernel:  [<c043ae58>] check_usage+0x1ee/0x1fb
kernel:  [<c043b9c5>] __lock_acquire+0x828/0x99c
kernel:  [<c043c0aa>] lock_acquire+0x4b/0x6d
kernel:  [<c0614292>] _read_lock+0x19/0x28
kernel:  [<f8944693>] set_tone_zone+0x43/0x90 [zaptel]
kernel:  [<f894764d>] initialize_channel+0x35d/0x540 [zaptel]
kernel:  [<f8948afe>] zt_open+0x20e/0x2a0 [zaptel]
kernel:  [<c047ae2f>] chrdev_open+0x105/0x13a
kernel:  [<c0471a4a>] __dentry_open+0xc8/0x1ab
kernel:  [<c0471b9b>] nameidata_to_filp+0x1c/0x2e
kernel:  [<c0471bdb>] do_filp_open+0x2e/0x35
kernel:  [<c0471c22>] do_sys_open+0x40/0xb5
kernel:  [<c0471cc3>] sys_open+0x16/0x18
kernel:  [<c0403faf>] syscall_call+0x7/0xb






More information about the fedora-test-list mailing list