From: Andrew Morton <akpm@linux-foundation.org>
To: "Parag Warudkar" <parag.warudkar@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com,
torvalds@linux-foundation.org, linux-acpi@vger.kernel.org
Subject: Re: BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0]
Date: Fri, 7 Dec 2007 15:17:14 -0800 [thread overview]
Message-ID: <20071207151714.51b80234.akpm@linux-foundation.org> (raw)
In-Reply-To: <82e4877d0712071453h38795e36of26324a4b123fa6c@mail.gmail.com>
On Fri, 7 Dec 2007 17:53:47 -0500
"Parag Warudkar" <parag.warudkar@gmail.com> wrote:
> Got this on today's git (2.6.24-rc4) while compiling stuff - Looks
> like it is related to CpuIdle stuff.
> I chose CONFIG_CPU_IDLE for the first time so I don't know when this
> was introduced.
>
> This is on x86_32, SMP.
>
> BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0]
>
> Pid: 0, comm: swapper Not tainted (2.6.24-rc4 #3)
> EIP: 0060:[<c0603e22>] EFLAGS: 00000202 CPU: 1
> EIP is at _spin_lock_irqsave+0x16/0x27
> EAX: c06b4110 EBX: 00000001 ECX: f7873808 EDX: 00000293
> ESI: 00000005 EDI: f7873808 EBP: 00000000 ESP: f7829f10
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> CR0: 8005003b CR2: 004f5960 CR3: 372c5000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400
> [<c0438233>] tick_broadcast_oneshot_control+0x10/0xda
> [<c0437c82>] tick_notify+0x1d4/0x2eb
> [<c04281b4>] get_next_timer_interrupt+0x143/0x1b4
> [<c0605819>] notifier_call_chain+0x2a/0x47
> [<c04345a0>] raw_notifier_call_chain+0x17/0x1a
> [<c04378b7>] clockevents_notify+0x19/0x4f
> [<c0533cc3>] acpi_idle_enter_simple+0x183/0x1d0
> [<c058cea3>] cpuidle_idle_call+0x53/0x78
> [<c058ce50>] cpuidle_idle_call+0x0/0x78
> [<c0402575>] cpu_idle+0x97/0xb8
OK, thanks. Another one for the regression list, please.
next prev parent reply other threads:[~2007-12-07 23:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 22:53 BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] Parag Warudkar
2007-12-07 23:12 ` Pallipadi, Venkatesh
2007-12-07 23:31 ` Parag Warudkar
2007-12-08 2:56 ` Thomas Gleixner
2007-12-08 15:10 ` Parag Warudkar
2007-12-08 15:36 ` Parag Warudkar
2007-12-08 15:47 ` Ingo Molnar
2007-12-08 16:00 ` Parag Warudkar
2007-12-08 19:13 ` Ingo Molnar
2007-12-08 19:33 ` Parag Warudkar
2007-12-08 19:42 ` Ingo Molnar
2007-12-08 20:08 ` Parag Warudkar
2007-12-08 20:11 ` Ingo Molnar
2007-12-08 20:46 ` Parag Warudkar
2007-12-08 20:51 ` Arjan van de Ven
2007-12-08 21:04 ` Parag Warudkar
2007-12-08 23:12 ` Parag Warudkar
2007-12-09 21:57 ` Parag Warudkar
2007-12-09 22:30 ` Arjan van de Ven
2007-12-10 5:49 ` Thomas Gleixner
2007-12-11 4:49 ` Parag Warudkar
2007-12-14 23:17 ` Len Brown
2007-12-15 0:51 ` Parag Warudkar
2007-12-15 8:10 ` Thomas Gleixner
2007-12-15 18:48 ` Parag Warudkar
2007-12-16 5:15 ` Parag Warudkar
2007-12-16 13:43 ` Parag Warudkar
2007-12-17 8:05 ` Thomas Gleixner
2007-12-17 13:08 ` Parag Warudkar
2007-12-17 22:05 ` Thomas Gleixner
2008-01-09 11:56 ` Thomas Gleixner
2008-01-11 0:31 ` Parag Warudkar
2008-01-11 9:50 ` Thomas Gleixner
2007-12-07 23:17 ` Andrew Morton [this message]
2007-12-08 2:35 ` BUG: " Rafael J. Wysocki
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=20071207151714.51b80234.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).