From: Ingo Molnar <mingo@elte.hu>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: 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: Sat, 8 Dec 2007 16:47:55 +0100 [thread overview]
Message-ID: <20071208154755.GA5255@elte.hu> (raw)
In-Reply-To: <82e4877d0712080736v12c1e31at9149655ae000fe50@mail.gmail.com>
* Parag Warudkar <parag.warudkar@gmail.com> wrote:
> [<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
> =======================
> BUG: soft lockup - CPU#1 stuck for 11s! [vim:3736]
does the patch below help? But the root cause is likely some timer
problems - do you get consistent results from:
while :; do time usleep 1111111; done
or do these sleeps fluctuate?
Ingo
Index: linux/kernel/sched.c
===================================================================
--- linux.orig/kernel/sched.c
+++ linux/kernel/sched.c
@@ -774,6 +774,7 @@ void sched_clock_idle_wakeup_event(u64 d
struct rq *rq = cpu_rq(smp_processor_id());
u64 now = sched_clock();
+ touch_softlockup_watchdog();
rq->idle_clock += delta_ns;
/*
* Override the previous timestamp and ignore all
next prev parent reply other threads:[~2007-12-08 15:48 UTC|newest]
Thread overview: 36+ 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 [this message]
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 ` BUG: " Andrew Morton
2007-12-08 2:35 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
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=20071208154755.GA5255@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.