From: "Parag Warudkar" <parag.warudkar@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: soft lockup - CPU#1 stuck for 15s! [swapper:0]
Date: Sun, 9 Dec 2007 16:57:38 -0500 [thread overview]
Message-ID: <82e4877d0712091357u41973a24v38c4ad18ad596de5@mail.gmail.com> (raw)
In-Reply-To: <82e4877d0712081512s2b5a72aewbe396f28305ac963@mail.gmail.com>
On Dec 8, 2007 6:12 PM, Parag Warudkar <parag.warudkar@gmail.com> wrote:
> No problems after disabling CONFIG_HIGHRES_TIMERS , CONFIG_CPU_IDLE
> and CONFIG_NO_HZ.
>
> I will try enabling them one by one - HRT, NOHZ and CPU_IDLE last -
> that way we can at least tell what is required to be hit with this
> problem.
Looks like CPU_IDLE=y is necessary for the problem to show up.
With CPU_IDLE=n HRT+NO_HZ+TICK_ONESHOT does not give soft lockup problems.
(Actually with HIGH_RES_TIMERS=NO_HZ=TICK_ONESHOT=y I do see short
freezes on ssh - when I cannot type anything for may be a second even
under 100% idle. But Soft Lock up doesnt show up in dmesg with this
configuration.)
No Soft Lockup - CPU_IDLE=n 5+ Hours uptime
---------------------------------------------------------------------------
HIGH_RES_TIMERS=NO_HZ=TICK_ONESHOT=n
HIGH_RES_TIMERS=y NO_HZ=TICK_ONESHOT=n
HIGH_RES_TIMERS=NO_HZ=y TICK_ONESHOT=n
HIGH_RES_TIMERS=NO_HZ=TICK_ONESHOT=y - short freezes.
Soft Lockup - CPU_IDLE=y 2 hours uptime
--------------------------------------------------------------------------
HIGH_RES_TIMERS=NO_HZ=TICK_ONESHOT=y
dmesg -
BUG: soft lockup - CPU#1 stuck for 11s! [swapper:0]
Pid: 0, comm: swapper Not tainted (2.6.24-rc4 #13)
EIP: 0060:[<c0603eaa>] 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: 800f5958 CR3: 37284000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
[<c0438293>] tick_broadcast_oneshot_control+0x10/0xda
[<c0437ce2>] tick_notify+0x1d4/0x2eb
[<c04281bc>] get_next_timer_interrupt+0x143/0x1b4
[<c06058a1>] notifier_call_chain+0x2a/0x47
[<c04345c0>] raw_notifier_call_chain+0x17/0x1a
[<c043781e>] clockevents_notify+0x19/0x4f
[<c0533d23>] acpi_idle_enter_simple+0x183/0x1d0
[<c058cf03>] cpuidle_idle_call+0x53/0x78
[<c058ceb0>] cpuidle_idle_call+0x0/0x78
[<c0402575>] cpu_idle+0x97/0xb8
=======================
Parag
next prev parent reply other threads:[~2007-12-09 21:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 22:53 BUG: " 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 [this message]
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 ` BUG: " Andrew Morton
2007-12-08 2:35 ` Rafael J. Wysocki
2007-12-09 22:42 parag.warudkar
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=82e4877d0712091357u41973a24v38c4ad18ad596de5@mail.gmail.com \
--to=parag.warudkar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®