From: Bernard Pidoux <bpidoux@free.fr>
To: linux-kernel@vger.kernel.org
Cc: Bernard Pidoux <bpidoux@free.fr>
Subject: Re: spinlock lockup on CPU#0
Date: Sun, 27 Apr 2008 02:15:23 +0200 [thread overview]
Message-ID: <200804270215.23739.bpidoux@free.fr> (raw)
In-Reply-To: <200804262333.39383.bpidoux@free.fr>
[-- 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
next prev parent reply other threads:[~2008-04-27 0:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 21:33 spinlock lockup on CPU#0 Bernard Pidoux
2008-04-27 0:15 ` Bernard Pidoux [this message]
2008-04-27 2:00 ` Justin Mattock
2008-04-27 2:13 ` Bob Copeland
2008-04-27 2:20 ` Justin Mattock
2008-04-27 2:41 ` Bob Copeland
2008-04-27 6:11 ` Justin Mattock
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 1:41 Justin Mattock
2008-04-26 18:29 ` Andrew Morton
2008-04-26 18:39 ` Justin Mattock
2008-04-26 19:14 ` Ingo Molnar
2008-04-26 19:32 ` Justin Mattock
2008-04-26 21:06 ` Bob Copeland
2008-04-26 21:48 ` Justin Mattock
2008-04-28 20:38 ` Venki Pallipadi
2008-04-28 22:02 ` Justin Mattock
2008-04-26 23:04 ` Hugh Dickins
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=200804270215.23739.bpidoux@free.fr \
--to=bpidoux@free.fr \
--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