Re: spinlock lockup on CPU#0

Bernard Pidoux
2008-04-27T00:15:40Z

[-- Attachment #1: Type: text/plain, Size: 95 bytes --]

Hi,

cpu_idle bug is also present in 2.6.24.4 kernel.

I hope this helps.

Bernard Pidoux

[-- Attachment #2: lockdep-2.6.24.4.idle.cpu --]
[-- Type: text/plain, Size: 3051 bytes --]

Apr 27 01:13:36 f6bvp-7 kernel: Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
Apr 27 01:13:36 f6bvp-7 kernel: ... MAX_LOCKDEP_SUBCLASSES: 8
Apr 27 01:13:36 f6bvp-7 kernel: ... MAX_LOCK_DEPTH: 30
Apr 27 01:13:36 f6bvp-7 kernel: ... MAX_LOCKDEP_KEYS: 2048
Apr 27 01:13:36 f6bvp-7 kernel: ... CLASSHASH_SIZE: 1024
Apr 27 01:13:36 f6bvp-7 kernel: ... MAX_LOCKDEP_ENTRIES: 8192
Apr 27 01:13:36 f6bvp-7 kernel: ... MAX_LOCKDEP_CHAINS: 16384
Apr 27 01:13:36 f6bvp-7 kernel: ... CHAINHASH_SIZE: 8192
Apr 27 01:13:36 f6bvp-7 kernel: memory used by lock dependency info: 1712 kB
Apr 27 01:13:36 f6bvp-7 kernel: per task-struct memory footprint: 2160 bytes
Apr 27 01:13:36 f6bvp-7 kernel: Memory: 1018724k/1047424k available (2307k kernel code, 27920k reserved, 1174k data, 616k init)
Apr 27 01:13:36 f6bvp-7 kernel: Calibrating delay using timer specific routine.. 4396.25 BogoMIPS (lpj=8792506)
Apr 27 01:13:36 f6bvp-7 kernel: Mount-cache hash table entries: 256
Apr 27 01:13:36 f6bvp-7 kernel: lockdep: not fixing up alternatives.
Apr 27 01:13:36 f6bvp-7 kernel: lockdep: not fixing up alternatives.
Apr 27 01:13:36 f6bvp-7 kernel: Initializing CPU#1
Apr 27 01:13:36 f6bvp-7 kernel: Calibrating delay using timer specific routine.. 4388.97 BogoMIPS (lpj=8777957)
Apr 27 01:13:36 f6bvp-7 kernel: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz stepping 0d
Apr 27 01:13:36 f6bvp-7 kernel: WARNING: at kernel/lockdep.c:2662 check_flags()
Apr 27 01:13:36 f6bvp-7 kernel: Pid: 0, comm: swapper Not tainted 2.6.24.4patched #7
Apr 27 01:13:36 f6bvp-7 kernel:
Apr 27 01:13:36 f6bvp-7 kernel: Call Trace:
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8024d650>] __atomic_notifier_call_chain+0x0/0xa0
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff802537b2>] check_flags+0x1c2/0x1d0
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff80257e35>] lock_acquire+0x65/0xd0
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8024d6a1>] __atomic_notifier_call_chain+0x51/0xa0
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8020b510>] mwait_idle+0x0/0x60
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8020b390>] default_idle+0x0/0x60
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8024d701>] atomic_notifier_call_chain+0x11/0x20
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8020ac49>] __exit_idle+0x29/0x30
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8020b475>] cpu_idle+0x85/0xd0
Apr 27 01:13:36 f6bvp-7 kernel: [<ffffffff8021eea8>] start_secondary+0x2f8/0x430
Apr 27 01:13:36 f6bvp-7 kernel:
Apr 27 01:13:36 f6bvp-7 kernel: possible reason: unannotated irqs-on.
Apr 27 01:13:36 f6bvp-7 kernel: irq event stamp: 6
Apr 27 01:13:36 f6bvp-7 kernel: hardirqs last enabled at (5): [<ffffffff8043fd15>] _spin_unlock_irqrestore+0x55/0x60
Apr 27 01:13:36 f6bvp-7 kernel: hardirqs last disabled at (6): [<ffffffff8020b461>] cpu_idle+0x71/0xd0
Apr 27 01:13:36 f6bvp-7 kernel: softirqs last enabled at (0): [<ffffffff8022e8ae>] copy_process+0x2de/0x15d0
Apr 27 01:13:36 f6bvp-7 kernel: softirqs last disabled at (0): [<0000000000000000>] 0x0